-
Notifications
You must be signed in to change notification settings - Fork 7
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
trailing/leading spaces in roles cause issues #464
Comments
Great catch; thanks @jnurthen! |
Quick update, as it's been a while! I have fixed this on my local machine; just have a few performance tests to run. I'm expecting to complete that over the weekend, and push new versions of both the test suite and this extension (it'll take a while after that for the extension to be reviewed by the browsers; usually that's not more than a few days). |
Originated by matatk/landmarks#464 - thanks :-)
Originated by matatk/landmarks#464 - thanks :-)
Originated by matatk/landmarks#464 - thanks :-)
Originated by matatk/landmarks#464 - thanks :-)
Originated by matatk/landmarks#464 - thanks :-)
* Handle the role attribute as a token list. * Bump page-structural-semantics-scanner-tests to include token list tests. * Don't check for valid roles twice (checked performance; seems negligible, but definitely was duplicated work). * Move some of the functions around so that definition order matches order called in getLandmarks(). * Add a couple of TODO notes. Fixes #464
2.11.1 has been released and contains the fix for this bug. It's available in Firefox and Chrome now; Opera and Edge should follow in several days, after review. Thanks again for your report. |
role="main " is not recognized as a landmark.
Trailing and leading spaces should all be allowed as roles are space-separated tokens in HTML https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#space-separated-tokens
Further role="main foo" and role="foo main" (assuming foo isn't a known role in the latter case) should also both resolve to main in the landmarks extension.
The text was updated successfully, but these errors were encountered: