[wp-trac] [WordPress Trac] #24306: Twenty Thirteen: border-box box sizing will break many plugins

WordPress Trac noreply at wordpress.org
Thu Jun 6 09:51:15 UTC 2013


#24306: Twenty Thirteen: border-box box sizing will break many plugins
---------------------------+--------------------
 Reporter:  professor99    |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  3.6
Component:  Bundled Theme  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |
---------------------------+--------------------

Comment (by professor99):

 These are just 4 themes of the 1795 themes available on the WordPress
 themes page. Though there may be more themes that use the universal
 selector its a very small minority and certainly not a good enough reason
 for this change.

 Of the themes you have given Montezuma is definitely worth a look as it
 has 170,000 downloads since first appearing last November (it presents
 images nicely). I looked on the forums including the author's own forum
 and a few problems with plugins are mentioned that may be caused by this
 or otherwise but there are always clashes between themes and plugins so I
 wouldn't past judgement either way.

 In any case problems with plugin layout always get reported to the plugin
 author (as I can attest) and rarely to the theme developer so such
 problems will not be immediately apparent on the theme's support forum.

 As to clashes with themes most plugin author's tend to ignore them unless
 the theme is popular and the issue regularly gets reported.

 It's obvious that changing the box-sizing universally from the standard
 default content-box would change the layout of elements affected in the
 content or the plugin widget. Whether or not this causes a problem or not
 is another matter but if the plugin is relying on the standard model
 defaults it could be a big deal or even catastrophic as my example a few
 posts back shows.

 Suggesting that all plugin authors have to upgrade their plugins to
 support a non default box model is silly. We have standards so everybody
 can get along famously and reduce the workload of handling infinite
 possibilities. I remember the bad days of the internet where we had to
 cope with both IE's non-standard model and W3C's model which multiplied my
 workload enormously (the pain yet lingers). Let's not add needlessly to
 plugin authors workload in requiring them to support two box models and
 let them get on with their work in designing plugins without having to
 deal with this mess. If the plugin author wants to use border-box let them
 define it themselves but don't ENFORCE it.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24306#comment:28>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list