-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tabbed mode spec #95
Conversation
@loubrett Ready for you to look now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor comments about linking stuff.
I haven't thought through the URLPattern stuff any more yet so I'll have a think about that next week.
I just pushed a major rework. Still incomplete so don't re-review yet. |
Copy-pasted from Louise Brett's source doc. Need to clean up, linkify and edit.
Now there is just a single processing section at the h2 level.
Too numerous to list individual changes. A lot of moving around. Many additional details added, including: - List of invariants that must be followed (e.g. home tab never navigates out of home scope, regular tab never navigates into home scope). - Specifying that home tabs open at the start_url. - Properly defining within and outside of home scope terms. - Properly defining what happens when you click the new tab button.
Define a boolean condition first, rather than defining a set. Makes it more readable. Also exclude fragments (but not query).
…non-normatively, and just talk about it as an idea, not a formal term. Add a note about ignoring the fragment but not the query.
Do not use the at-risk string syntax. Add more detail about the default matching the query, or not.
Now, the three invariants are non-normative discussion of what is intended, rather than a hard rule. The normative logic elsewhere should speak for itself. This way, we do not need to formally find a concept of 'initial URL' and can just informally talk about documents that rewrite their URL.
@dmurph adding as editor. PTAL, thanks, and let me know if you want to discuss! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial comments - also happy to go over in-person in a meeting
Now has an explicit concept of "has a new tab button" (analogous to "has a home tab"). The parser algorithm no longer (accidentally) sets the new tab URL to the start URL if it is within home tab scope. Add a note clarifying why the new tab button is not allowed to be in home tab scope. Also note the start URL default, which is easy to miss as it is buried in the parser algorithm.
Done in consultation with dmurph and loubrett, to make the navigation rules much clearer and hook into the HTML navigable machinery.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although nit: the display_mode link in the rendered text seems broken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks Dan. Yes, I mentioned this to you in a chat: we need to wait until w3c/csswg-drafts#7306 gets pushed out to the editor's draft, and then it will automatically resolve itself (because the definition of "display mode" was moved from CSS mediaqueries-5 to Manifest; Manifest updated right away, CSS did not). I don't know when that will be; it was last updated in May 2022, coming up to two years... Edit: filed an issue about this. |
Based on an earlier draft by @loubrett (Louise Brett).
Preview | Diff