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.

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

Closed
wants to merge 13 commits into from

Conversation

pkra
Copy link
Member

@pkra pkra commented May 24, 2024

Moved from w3c/html-aam#401

@pkra pkra changed the base branch from monorepo_history--html-aam to main June 12, 2024 19:22
@pkra pkra changed the title [Monorepo] [html-aam PR 401] handling fallback content for the meter element [html-aam PR 401] handling fallback content for the meter element Jun 12, 2024
@pkra
Copy link
Member Author

pkra commented Jun 12, 2024

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
Copy link
Contributor

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(", ")?

@rahimabdi
Copy link
Contributor

Re-assigning reviewers @cookiecrook @cyns.

@scottaohara
Copy link
Member

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).

Authors are encouraged to include a textual representation of the gauge's state in the element's contents, for users of user agents that do not support the meter element.

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?

@scottaohara
Copy link
Member

closed original issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants