We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems aria.js is running too late, causing an issue with heading levels, cf. https://github.com/w3c/respec/issues/4436.
The text was updated successfully, but these errors were encountered:
Trying to read up on things. It looks like aria.js // ariaAttributeReferences() intentionally runs after respec.
ariaAttributeReferences()
On the one hand, e.g., the ARIA spec has ariaAttributeReferences in the respecConfig's postProcess array:
ariaAttributeReferences
https://github.com/w3c/aria/blob/60f526c0a93575a2f3194d85dfd70f1eaf2991d1/index.html#LL145C39-L145C39
If I move it to the preProcess array, we get the correct headings.
But I don't know if post-processing was intentional. git says @jnurthen might remember -- w3c/aria@613eacf.
Then there's also
aria-common/script/aria.js
Lines 797 to 800 in b3b7981
which git blame also says @jnurthen might know - do you remember if this was intentional?
Sorry, something went wrong.
As noted in today's meeting, we should try to refactor the code and move the heading-generating code so that it can be done in pre-processing.
pkra
jnurthen
No branches or pull requests
It seems aria.js is running too late, causing an issue with heading levels, cf. https://github.com/w3c/respec/issues/4436.
The text was updated successfully, but these errors were encountered: