+1 This would have an easy adoption path for existing content. And it falls back to the current behavior, which is great too.

@scottaohara couldn't this go directly to the CSSWG or would you want an explainer/proposal from the group?

+1 - I like this idea. There might be some implementation concerns, depending on how the existing tooltip rendering works. I.e. it might not be trivial to add arbitrary styling, if the tooltip is provided via some native OS widget. But that's not a good reason not to do this, so I'm in favor.

I do somewhat agree that this might be best to take directly to the CSSWG as a suggestion/request. The "explainer" is roughly a paragraph long. Just add a ::title pseudo element that references the tooltip popover.

There is some overlap between this proposal and the popover feature, but I don't think that's bad. And if this encourages the "easy" cases to just use the pseudo element, leaving the more complex cases to popover, that's likely a good thing.

@mfreed7 @gregwhitworth - is it even possible to transfer this issue over to the csswg? does anyone have the permissions available to do that? I obviously have not gotten around to refiling the issue, but transferring it seems like it could achieve that while also bringing along the current discussion thread?

if not, i can re-file over there and just reference back this issue.

Hmm, I don't think that's possible, at least for me. Moving issues between accounts is some kind of voodoo I haven't learned. Perhaps Greg knows how?

https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository says transfer isn't possible between repositories owned by different users (openui and w3c in this case). (I see the "Transfer issue" UI, but it doesn't give any allowable destinations.)

thanks both. i'll repost the issue then.

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.

closing this issue since there is an issue for this in the css wg.