Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Review Following Hyperlinks #1482

Closed
scottaohara opened this issue Jun 20, 2018 · 7 comments
Closed

Review Following Hyperlinks #1482

scottaohara opened this issue Jun 20, 2018 · 7 comments
Assignees

Comments

@scottaohara
Copy link
Member

Review the differences between WHATWG Following Hyperlinks and W3C Following Hyperlinks to determine if we would like to similarly trim down the steps

@scottaohara scottaohara added this to the HTML5.3 WD5 milestone Jun 20, 2018
@LJWatson LJWatson modified the milestones: HTML5.3 WD5, HTML5.3 WD6 Jul 30, 2018
@LJWatson LJWatson removed this from the HTML5.3 WD6 milestone Sep 13, 2018
@patricia-gallardo
Copy link
Contributor

It seems that the simplification is based around defining concepts:

  • what "cannot navigate" means
  • what is a "node document"
  • what is a "targetAttributeValue"
  • how to "get an element's target given subject"
    etc
    I'm not sure either text is very readable - do you have any pointers with regards to which direction we want to go? If some of these terms are defined elsewhere, then repeating them here is probably not very useful?

@patricia-gallardo
Copy link
Contributor

I'm still working out what differences exist in semantics, but I do believe there is a typo in our version:
"Otherwise, if target is an a or area element with no target attribute"

If I'm not mistaken this should be:

"Otherwise, if subject is an a or area element with no target attribute"

@patricia-gallardo
Copy link
Contributor

Other notes:

The section linked to in the whatwg step number 7 seems quite more involved than step 3 in the w3c version:
https://html.spec.whatwg.org/#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name

Especially it seems that the w3c version does not talk about the impact of noopener wrt choosing the target

@patricia-gallardo
Copy link
Contributor

The similar section in the w3c version seems to be
http://w3c.github.io/html/single-page.html#the-rules-for-choosing-a-browsing-context

@patricia-gallardo
Copy link
Contributor

High level the differences are:
whatwg has added a step before the ones in the w3c section:
"1. If subject cannot navigate, then return."

Further they have split step 3 in the w3c version, into five steps (steps 4 to 8) in the whatwg version.
A part of this difference is that they refer to the section about choosing the browsing context instead of trying to write out the steps.

We could probably do these changes as well (or similar ones), since step 3 is quite long and repetitious, and might be missing some nuance.

@patricia-gallardo
Copy link
Contributor

patricia-gallardo commented Oct 9, 2018

@siusin
Copy link
Contributor

siusin commented Jul 29, 2019

We're closing this issue on the W3C HTML specification because the W3C and WHATWG are now working together on HTML, and all issues are being discussed on the WHATWG repository.

If you filed this issue and you still think it is relevant, please open a new issue on the WHATWG repository and reference this issue (if there is useful information here). Before you open a new issue, please check for existing issues on the WHATWG repository to avoid duplication.

If you have questions about this, please open an issue on the W3C HTML WG repository or send an email to [email protected].

@siusin siusin closed this as completed Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants