Clarify self-navigation behavior in a presentation. #461
Conversation
|
PTAL @tidoust as you filed the original issue :-) |
index.html
Outdated
| navigate</a>, it SHOULD NOT offer to open the resource in a new | ||
| <a>top-level browsing context</a>, but instead SHOULD abort the | ||
| navigation and possibly throw a <a>SecurityError</a> (consistent | ||
| with the <a>steps to navigate</a>). |
There was a problem hiding this comment.
That is not entirely "consistent" with the steps to navigate: the steps to navigate in HTML mandate the SecurityError be thrown when the exceptions enabled flag is set, whereas this makes it optional.
If the SecurityError exception cannot be mandated because it remains a challenge implementation-wise, I would suggest to drop "(consistent with the steps to navigate)".
There was a problem hiding this comment.
Throwing the exception isn't an implementation concern from my point of view. Rather I didn't want to get into the details here of when to throw a SecurityError and thus duplicate HTML. I rephrased this, let me know if that addresses your feedback.
|
Thanks! |
This addresses feedback in Issue #455, to link navigation behavior to the HTML 5.1 navigation steps, and clarify how the receiving user agent should respond.
There's also a bunch of changes from attempting to run tidy-html5 which I'll clean up in another commit on this PR.
Preview | Diff