WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #10734, comment 28


Ignore:
Timestamp:
05/03/11 19:55:28 (3 years ago)
Author:
chipbennett
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10734, comment 28

    initial v1  
    1010And now we're arguing in circles. 
    1111 
    12 No, it's not hard. But it's the polar opposite of what ''should'' be done. Theme Developers shouldn't have to ''undo'' something that should never have been done in the first place. Theme developers ''shouldn't have to'' fix core's invalid markup. Theme developers ''shouldn't have to'' implement workarounds to undo arbitrary styling. 
     12No, it's not hard. But it's the polar opposite of what ''should'' be done. Theme Developers ''shouldn't have to'' undo something that should never have been done in the first place. Theme developers ''shouldn't have to'' fix core's invalid markup. Theme developers ''shouldn't have to'' implement workarounds to undo arbitrary styling. 
    1313 
    14 Core does not define styling for any other markup. Why does gallery markup get this special dispensation - and to the degree that it is deemed so vitally important that it causes core to output invalid markup in order to implement? 
     14Core does not define styling for any other markup. Why does gallery markup get this special dispensation - and to the degree that it is deemed so vitally important that it is allowed to cause core to output invalid markup in order to implement? 
    1515 
    1616Further: the argument that it's easy to fix rather invalidates the hyperbolic assertion that fixing it would cause breakage for millions of users.