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

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

> > Note that `::interest-button` might not need to be shown by default on platforms where a gaze can make just the "show details" button appear.
> 
> I don't see how that would work without compromising end-user privacy. Care to elaborate?

Perhaps I misunderstood this, but I thought the point was that we could make the actual `::interest-button` pseudo (the developer controllable one) have a UA rule like:

```css
display: if(media(showing_interest_is_easy): none; else: inline-block);
```

where the `showing_interest_is_easy` media query matches for input devices where a) there's a native way to hover, **or** b) the platform/OS provides some other way to easily trigger interest via other means. If the only means to trigger interest is the long-press context menu, this media query wouldn't match.

Then, on a VisionPro that supports showing a special privacy-preserving browser-side floating button, that media query would not match, and the developer-accessible `::interest-button` would  not show up. The VisionPro could even detect that the `::interest-button` pseudo was being explicitly rendered (by developer choice), and suppress its own button.

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

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