You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on implementing HTML features, it's common that I end up with multiple tabs open to different parts of the HTML standard. Currently, they all just have "HTML Standard" as the title, and it'd be helpful if it was easier to distinguish between them. For example, here I have 7 tabs open:
Two of those are a spec and diff from whatpr.org. The rest are from various pages from the multipage spec. As you can imagine, it's easy to lose your place. 😅 I can of course modify the title of each one with the dev tools, and sometimes I do, but I don't usually have the patience.
My suggestions are:
The HTML Standard in multipage mode should include the section in their title.
whatpr.org pages should also include their PR # in their title, and whether they're a diff or a preview.
For example, something like:
"4.12 Scripting - The HTML Standard"
"4.10.5 The input element [Preview PR 10917] - HTML Standard"
The text was updated successfully, but these errors were encountered:
Safari has a feature where it attempts to hide duplicate portions of page titles to help with such cases, though I suppose that would not help with the whatpr.org case.
annevk
added
the
meta
Changes to the ecosystem around the standard, not its contents
label
Jan 31, 2025
What is the issue with the HTML Standard?
While working on implementing HTML features, it's common that I end up with multiple tabs open to different parts of the HTML standard. Currently, they all just have "HTML Standard" as the title, and it'd be helpful if it was easier to distinguish between them. For example, here I have 7 tabs open:
Two of those are a spec and diff from whatpr.org. The rest are from various pages from the multipage spec. As you can imagine, it's easy to lose your place. 😅 I can of course modify the title of each one with the dev tools, and sometimes I do, but I don't usually have the patience.
My suggestions are:
For example, something like:
The text was updated successfully, but these errors were encountered: