Hacker News new | ask | show | jobs
by TrueDuality 771 days ago
I suspect this isn't going to get major usage. Making it a dedicated API makes these things easier to target by extensions and thus easier to block. There are legitimate usages but almost all of the ones I encounter are marketing call to actions and invasive support chat boxes which are both almost universally hated and would the target of those blocking action.
4 comments

You don't think sites will use tooltips and dropdown menus. You are probably confusing these for popups which open new browser windows, popover happen within the webpage when a piece of UI needs to be drawn over existing content.
When I first read about this API a while back, I thought the same thing. But it's perfect for adding complex controls on top of inputs when you have limited real estate (e.g. clicking on an input with a font name and showing a font picker popover with a preview of the font). This is obviously possible today without this API, but I like that they added something semantic. I regularly have to wade through the ARIA docs to figure out which role/aria- attributes to use.
What about selecting an image to view?
What about cookie consents?
Also universally hated and widely blocked.
Very much a anti-pattern. The entire concept of these is malicious compliance against the GDPR and not something that the GDPR requires.
The ePrivacy directive does require them, though. (Of course, not in the malicious-compliance form we see today.)