[buddypress-trac] [BuddyPress] #5016: Usage of <H*> selectors in theme compatibility templates

buddypress-trac noreply at wordpress.org
Tue May 28 00:58:51 UTC 2013

#5016: Usage of <H*> selectors in theme compatibility templates
 Reporter:  ericlewis    |       Owner:
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Theme        |     Version:  1.7
 Severity:  normal       |  Resolution:  wontfix
 Keywords:               |
Changes (by boonebgorges):

 * keywords:  close 2nd-opinion =>
 * resolution:   => wontfix
 * status:  new => closed
 * component:  Template Pack => Theme
 * milestone:  Awaiting Review =>


 I'm going to agree with r-a-y here. The problem is not us: We are using
 the semantically correct elements - at least, the semantically correct
 _HTML4_ elements, as our templates are minimally HTML5-ified. If themes do
 funny things do funny things with the way `<h*>` elements are styled (and
 I have actually seen themes that, eg, make `<h3>` bigger than `<h2>`, make
 `<h4>` smaller than the body text, etc), it's really a bug in that theme.
 The only ways we could work around it are (a) supply our own overriding
 styles, like `#buddypress h3 { font-size: 1.2em; }`, or (b) stop using
 header elements altogether. In the case of (a), we'd invariably clash with
 the native header styles of many themes, which defeats much of the purpose
 of theme compatibility. In case (b), we would still have to supply our own
 styles, *and* we'd be abandoning semantic web protocol.

 Going to close as wontfix. Let's be evangelists to themers about this kind
 of stuff. Thanks for the report, ericlewis.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5016#comment:2>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list