Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Broken references in WebDriver #1735

Open
5 tasks
dontcallmedom-bot opened this issue Apr 24, 2023 · 0 comments
Open
5 tasks

Broken references in WebDriver #1735

dontcallmedom-bot opened this issue Apr 24, 2023 · 0 comments

Comments

@dontcallmedom-bot
Copy link

While crawling WebDriver, the following links to other specifications were detected as pointing to non-existing anchors:

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.
rakuco added a commit to rakuco/webdriver that referenced this issue Jul 4, 2023
@rakuco
editorial: Use "content navigable" instead of "nested navigable"
d9d74cc 
The term was renamed in the HTML spec in whatwg/html#8712 so the current
reference was broken as mentioned in w3c#1735.

While here, use ReSpec's shorthand syntax to refer to these sub concepts
directly and avoid having to specifically link to them in the index at the
end of the document.
@rakuco rakuco mentioned this issue Jul 4, 2023
Merged
rakuco added a commit to rakuco/webdriver that referenced this issue Jul 4, 2023
@rakuco
editorial: Use "content navigable" instead of "nested navigable"
10153af 
The term was renamed in the HTML spec in whatwg/html#8712 so the current
reference was broken as mentioned in w3c#1735.

While here, use ReSpec's shorthand syntax to refer to these sub concepts
directly and avoid having to specifically link to them in the index at the
end of the document.
rakuco added a commit to rakuco/webdriver that referenced this issue Aug 7, 2023
@rakuco
editorial: Use "content navigable" instead of "nested navigable"
7679754 
The term was renamed in the HTML spec in whatwg/html#8712 so the current
reference was broken as mentioned in w3c#1735.

While here, use ReSpec's shorthand syntax to refer to these sub concepts
directly and avoid having to specifically link to them in the index at the
end of the document.
whimboo pushed a commit that referenced this issue Aug 7, 2023
@rakuco
editorial: Use "content navigable" instead of "nested navigable" (#1750)
e64e2c8 
The term was renamed in the HTML spec in whatwg/html#8712 so the current
reference was broken as mentioned in #1735.

While here, use ReSpec's shorthand syntax to refer to these sub concepts
directly and avoid having to specifically link to them in the index at the
end of the document.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dontcallmedom-bot