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

Include id for searched feature #4925

Closed
marcoscaceres opened this issue May 22, 2019 · 3 comments
Closed

Include id for searched feature #4925

marcoscaceres opened this issue May 22, 2019 · 3 comments
Labels
Misc. site/data request

Comments

@marcoscaceres
Copy link
Contributor

For the purpose of link checking from W3C specs, it would be really useful if a feature could include the id of the feature being searched for in the document itself (e.g.., id="gamepad")... otherwise the W3C link checker fails :(
marcoscaceres pushed a commit to w3c/gamepad that referenced this issue May 22, 2019
chore: disable caniuse for now
eab3415 
It's causing link checker to fail. Filed Fyrd/caniuse#4925
@Fyrd
Copy link
Owner

Fyrd commented May 24, 2019

I don't quite understand...the link can be https://caniuse.com/gamepad or https://caniuse.com/#feat=gamepad which just shows the feature specifically. Is that not sufficient?

@marcoscaceres
Copy link
Contributor Author

marcoscaceres commented May 24, 2019 •
edited

@Fyrd sorry for not being clear. Let me try again: the link validator I'm using can't seem to find a specific HTML element with id="gamepad" (I also manually searched the source, and couldn't find one). However, I wasn't aware I could use a path... so might be able to get around the problem just using that.

@marcoscaceres
Copy link
Contributor Author

Going with the path option. Thanks @Fyrd!

@marcoscaceres marcoscaceres mentioned this issue May 27, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Misc. site/data request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Fyrd @marcoscaceres