-
Notifications
You must be signed in to change notification settings - Fork 125
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
[html-aam PR 401] handling fallback content for the meter element #2222
Conversation
resolves #27 this PR looks to treat the fallback content (the subtree) of the meter element as `aria-valuetext`. However, an author updates the value of the meter element, but does not update the subtree/fallback content, then the `value` needs to instead take preference over the fallback content, as the fallback contnet would no longer represent the true value of the `meter` element.
Co-authored-by: James Craig <cookiecrook@users.noreply.github.com>
Now pointing to main. |
<td></td> | ||
<td class="comments"> | ||
<div> | ||
If the `meter` element's subtree contains text content, user agents SHOULD expose this content, along with the element's initial value, by exposing the fallback content via the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cookiecrook's migrated comment provided below:
element's subtree contains text content, user agents SHOULD expose this content
Should this use "text node"?
Or innerText
?
along with the element's initial value, by exposing the fallback content
I dunno what this means... Does this mean concat the innerText and aria-valuenow, or convert aria-valuenow to a percentage and then concat? Does "along with" mean prepend? append? join(", ")
?
Re-assigning reviewers @cookiecrook @cyns. |
tbh, i'm having doubts about this PR and if this isn't potentially going to add a lot of complexity for fallback content that is primarily meant for instances of user agents where the meter element isn't supported (per the html spec specifically stating this).
so while i originally created this PR to try and address HTML AAM issue 27, I'm now wondering if this PR and that issue should instead be closed? |
closed original issue. |
Moved from w3c/html-aam#401