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

[WordPress Trac]

#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):

 Missed your update to the selector earlier to

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

 That would mostly work and is certainly useful if you have elements all
 over the place. Otherwise if your plugin uses a container as me and cello
 expressions are using the following also mostly works (as mentioned in an
 earlier post).

  .plugin-container, .plugin-container * {
 box-sizing: content-box;
 -moz-box-sizing: content-box;
 -webkit-box-sizing: content-box;
 }

 However both methods are problematic when applied to the top level widget
 box as it appends the widget class for which twelve thirteen has defined
 both width and padding.

 Note that twelve thirteen by adding padding and width to the widget class
 is breaking tradition as well leading to unfortunate styling consequences
 as most current plugins assume they have access to the full width of the
 widget container. Instead to achieve the plugin surround I suggest we
 provide a parent container to do this. This is the easy way to solve this
 problem and the problem above and provide consistent behavior between
 plugins and themes. Note the surround is really only useful for sidebar
 widgets. For footer widgets masonry can be used to provide the desired
 separation.

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