Opened 9 years ago
Closed 9 years ago
#33843 closed defect (bug) (fixed)
Invalid HTML on wp-signup.php or wp-activate.php with default themes
Reported by: | jfarthing84 | Owned by: | wonderboymusic |
---|---|---|---|
Milestone: | 4.4 | Priority: | normal |
Severity: | normal | Version: | 4.3 |
Component: | Login and Registration | Keywords: | has-patch |
Focuses: | multisite | Cc: |
Description
I don't know if this was indeed invalid 5 years ago as described in #13832, but it's not anymore. You most certainly do get two div
tags with an id of "content" when using Twenty Fifteen or Twenty Sixteen while viewing either wp-signup.php
or wp-activate.php
.
Attachments (1)
Change History (6)
#2
follow-up:
↓ 3
@
9 years ago
- Component changed from Themes to Login and Registration
- Focuses multisite added
- Milestone changed from Awaiting Review to 4.4
#3
in reply to:
↑ 2
@
9 years ago
Replying to SergeyBiryukov:
I guess we should change the ID in
wp-signup.php
andwp-activate.php
to something unique to those files.
This seems like the route to go.
If anybody is relying on existing behavior for custom signup styling or JS, we could be introducing a breaking change. Though I think the audience actually designing themes for integrated use with these is pretty small. And those specifically using #content
to create a custom experience even smaller. :)
We could probably change now and make sure to note it on Make/Core and with the theme team.
Confirmed. This wasn't an issue with previous themes, as they only had
id="content"
in content templates, but Twenty Fifteen and Sixteen have it inheader.php
, which results in this markup:Changing Twenty Fifteen is no longer feasible, as that could break child themes. I guess we should change the ID in
wp-signup.php
andwp-activate.php
to something unique to those files.