Opened 11 years ago
Closed 11 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 |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.4 |
| Component: | Login and Registration | Version: | 4.3 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | multisite |
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
@
11 years ago
- Component Themes → Login and Registration
- Focuses multisite added
- Milestone Awaiting Review → 4.4
#3
in reply to: ↑ 2
@
11 years ago
Replying to SergeyBiryukov:
I guess we should change the ID in
wp-signup.phpandwp-activate.phpto 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.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
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.phpandwp-activate.phpto something unique to those files.