Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058)

mfreed7 left a comment (w3ctag/design-reviews#1058)

> VisionOS has conventions and privacy preserving measures and UI affordances (which are incompatible with this proposal as currently specified). The above suggests adding a custom one off browser specific UI affordance specifically for this feature. That’s problematic as it wouldn’t integrate with how the rest of the OS works - suggesting doing a one off “floating button” for this feature is problematic.

Of course - that's a totally reasonable browser decision. My reading of the [resolution comment](https://github.com/w3ctag/design-reviews/issues/1058#issuecomment-4602914157) was that this was an optional thing. In the case that the browser decides not to show a special button, the `showing_interest_is_easy` media query won't match, and the `::interest-button` will show up. So users still get easy access to interest-invoked content, in the same way they will on touchscreen.

> Additionally, it would be detrimental for users and developers in that it couldn’t be styled in the way that developers would expect. This would also create inconsistency across platforms and OSs as to styling and behavior, leading to a potentially degraded user experience.

I think this is exactly analogous to the long-press context menu, which is similarly a) a browser-provided affordance for additional actions, b) isn't developer stylable, and c) floats above the page and doesn't affect layout.

I think we should focus more on the existing degraded user experience of not having access to content that is readily available to sighted users on desktop browsers with mice attached.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1058#issuecomment-4633713867
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1058/4633713867@github.com>