Opened 12 years ago
Closed 12 years ago
#22179 closed defect (bug) (fixed)
Twenty Twelve: style MultiSite messages and forms
Reported by: | pavelevap | Owned by: | lancewillett |
---|---|---|---|
Milestone: | 3.5 | Priority: | normal |
Severity: | normal | Version: | 3.5 |
Component: | Bundled Theme | Keywords: | has-patch |
Focuses: | Cc: |
Description
I tested Twenty Twelve with Multisite and it does not look very good (see attached screenshot). Maybe bundled themes could also support basic Multisite forms and activation messages?
Attachments (7)
Change History (20)
#1
@
12 years ago
- Summary changed from Bundled themes should support for Multisite? to Bundled themes should support for Multisite? (Twenty Twelve)
#3
follow-up:
↓ 6
@
12 years ago
Looks to me like the biggest problem here is that all standard styles are currently targeted, meaning we don't have standalone p, ul, li, h2 in the stylesheet. I propose we add the untargeted styles but I'm working two patches, so @lancewillet or whomever can choose.
#4
@
12 years ago
- Keywords 2nd-opinion added
22179-standalone.diff adds standalone ul, li, p and h2 styles. I've also attached three resulting screenshots:
I'm scrapping my effort on the override/targeted patch, mostly because we'd essentially be printing the original styles followed by the overriding styles in the page (which is lame).
On a side note, wp-signup.php looks like a primo candidate for some love at WCDenver Hack Day this weekend.
I'm reasonably confident the standalone styles will suffice here, but I'd love to hear others' feedback.
#5
@
12 years ago
- Keywords has-patch added; needs-patch removed
- Summary changed from Bundled themes should support for Multisite? (Twenty Twelve) to Twenty Twelve: style MultiSite messages and forms
#6
in reply to:
↑ 3
;
follow-up:
↓ 7
@
12 years ago
- Priority changed from normal to low
Replying to DrewAPicture:
Looks to me like the biggest problem here is that all standard styles are currently targeted, meaning we don't have standalone p, ul, li, h2 in the stylesheet. I propose we add the untargeted styles but I'm working two patches, so @lancewillet or whomever can choose.
I don't think we should add any standalone styles. Much better to target with a specific class, please.
Shouldn't system messages like this be styled by WP core itself?
#7
in reply to:
↑ 6
@
12 years ago
Replying to lancewillett:
Shouldn't system messages like this be styled by WP core itself?
The form elements are styled but it's assumed that themes will supply basic untargeted ui, li, p and h2 styles, as every theme I've tested besides Twenty Twelve seem to have.
#8
follow-up:
↓ 9
@
12 years ago
22179-2.diff adds the styles targeted to the .mu_register class.
I still don't really understand the hesitation behind providing basic un-targeted element type selector styles for p, h-tags, lists, etc. They could be easily bundled in with existing rules.
#9
in reply to:
↑ 8
@
12 years ago
Replying to DrewAPicture:
22179-2.diff adds the styles targeted to the .mu_register class.
I still don't really understand the hesitation behind providing basic un-targeted element type selector styles for p, h-tags, lists, etc. They could be easily bundled in with existing rules.
Because we've already launched the theme publicly, and we need to be *very* careful about changing styles that could break things. We can do it, just will take oodles of testing so won't be a quick one to commit.
Confirmed the problem on Multisite. Definitely doesn't look good at all. Nice catch @pavelevap!