popover=hint

[mfreed7]

Request for Mozilla Position on an Emerging Web Specification

• Specification title: popover=hint
• Specification or proposal URL (if available): (slightly out of date as of 1/19/24) Add popover=hint whatwg/html#9778
• Explainer URL (if available): https://open-ui.org/components/popover-hint.research.explainer/
• Proposal author(s) (@-mention GitHub accounts): @mfreed7, @josepharhar
• Caniuse.com URL (optional):
• Bugzilla URL (optional):
• Mozillians who can provide input (optional):

Other information

This is related to, but not blocked/gated by, the invokers proposal.

See also, whatwg/html#9776.

[mfreed7]

Any thoughts on this one? There's now an approved spec PR and a prototype implementation that seems to work nicely. We'd love to get implementer support.

[bramus]

It was recently announced that this is getting prototyped in Gecko: https://groups.google.com/a/mozilla.org/g/dev-platform/c/vaT1aQGETLM/m/XyjTUsHVBgAJ

[mfreed7]

It was recently announced that this is getting prototyped in Gecko: https://groups.google.com/a/mozilla.org/g/dev-platform/c/vaT1aQGETLM/m/XyjTUsHVBgAJ

Given that this is being prototyped, would it be appropriate to say that Gecko is supportive of the API?

[zcorpan]

We've discussed this and we're positive. We have some reservations for interesttarget, but that is a separate proposal.

[mfreed7]

We've discussed this and we're positive.

Thanks!

We have some reservations for interesttarget, but that is a separate proposal.

Yep, makes sense. There is more to do on interesttarget, but I think we're making progress.

[jcsteh]

There is some great progress with regard to figuring out the accessibility story here as can be seen in the accessibility section of the explainer. However, I see some open questions there (e.g. what to do about a hidden details target) and I don't think we have a clear resolution on those. Furthermore, beyond the explainer, I don't see an ARIA pull request anywhere to formally spec the accessibility API mappings, though please let me know if I missed something. While I trust that these things will be addressed given the solid work so far, I do think the accessibility story needs to be finalised (and specified) before anyone considers shipping this to the web at large.

[mfreed7]

Thanks for marking this positive!

There is some great progress with regard to figuring out the accessibility story here as can be seen in the accessibility section of the explainer. However, I see some open questions there (e.g. what to do about a hidden details target) and I don't think we have a clear resolution on those. Furthermore, beyond the explainer, I don't see an ARIA pull request anywhere to formally spec the accessibility API mappings, though please let me know if I missed something. While I trust that these things will be addressed given the solid work so far, I do think the accessibility story needs to be finalised (and specified) before anyone considers shipping this to the web at large.

I just wanted to acknowledge this comment and say that I agree on both counts. We need to update the explainer a bit, and we'll get an ARIA PR going also. Both good reminders, thanks! + @aleventhal to help me remember this. 😄