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

WordPress Trac noreply at wordpress.org
Wed Jun 5 10:08:10 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 Jayjdk):

 Replying to [comment:24 professor99]:
 > No theme I have come across uses the universal selector to set box-
 sizing to border-box (and I'm always cross checking problems with themes
 and WPUF). Can you name one?

 By only looking at the themes on [http://wordpress.org/themes/ this page]
 I found:

 * http://wordpress.org/themes/montezuma
 * http://wordpress.org/themes/quark
 * http://wordpress.org/themes/aspen
 * http://wordpress.org/themes/_second-foundation

 I also found some on ThemeForest.

 I also have two themes using it. I've never heard any complaints about it.
 And I haven't yet seen an example of a plugin breaking. Do you have one?

 > Unfortunately the [class*="your-plugin-prefix-"] selector has a big
 problem in that box-sizing isn't inherited so any child of that selector
 will revert to the universal box-sizing.

 `[class*="your-plugin-prefix-"] *`?

 It might be because I don't have a plugin that adds any frontend styling
 but I don't see why you would have to use Javascript. Plugins like
 WooCommerce are using `box-sizing: border-box` in their CSS.

 >
 > Seriously though wouldn't the solution be to define content-box sizing
 for the widget and entry-content classes using the selectors I gave two
 posts back? That would mean that plugins both past and future would be
 compatible with this theme.

 If Twenty Thirteen were to do this I agree your solution seems to be the
 best. But in my opinion this problem should be fixed on the plugin side.

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


More information about the wp-trac mailing list