Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#21353 closed enhancement (wontfix)

Twenty Eleven: In-content headers are largely unstyled, small, and don't have hierarchy

Reported by: nacin's profile nacin Owned by: lancewillett's profile lancewillett
Milestone: Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords: has-patch
Focuses: Cc:


The h1 and h2 styling is simply bold text. h4, h5, h6 are simply plain text. h3 is cool, but the text is very small and it gets lost easily.

Attachments (2)

heading-sizes-before.png (48.7 KB) - added by lancewillett 11 years ago.
21353.patch (1.3 KB) - added by lancewillett 11 years ago.

Download all attachments as: .zip

Change History (11)

#1 @lancewillett
11 years ago

URL for testing and before/after comparison:

#2 @obenland
11 years ago

  • Cc konstantin@… added

11 years ago

#3 @lancewillett
11 years ago

  • Keywords has-patch added

#4 @lancewillett
11 years ago

Added patch for testing.

Should we be concerned about breaking existing styling? Child themes and many people using Twenty Eleven now will see a big difference in post and page heading styles with this change.

#5 @lancewillett
11 years ago

I'm going to vote to leave this one not fixed because it will break back compat visually -- child themes can use the patch to fix things up if they want to.

Twenty Twelve works correctly, of course. :)

#6 @MikeHansenMe
11 years ago

I do like the Twenty Twelve styling better for h1-h5, but I would agree that we should just leave Twenty Eleven as it is since it is already being used.

#7 @iandstewart
11 years ago

-1 — Another vote not to fix this in Twenty Eleven for the reasons stated above.

#8 @lancewillett
11 years ago

  • Milestone 3.5 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

In summary: though this update would make things look much nicer, it would break too many things to be a good change.

#9 @nacin
11 years ago

Originally, I just wanted to make sure this got logged — I agree with the wontfix.

Note: See TracTickets for help on using tickets.