Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Popover API

developer.mozilla.org

Post reply on HN
Print view View original

151–160 of 166 posts

Re: Popover API

#151

Post by hkdobrev »

unakrav wrote: post #136
staminade wrote: post #43

I think the Popover API will be really transformative when CSS Anchor Positioning[1] arrives as well. Anchor positioning will let you position elements relative to others on the page. Combined with the Popover API it will let you implement things like custom tooltips and context menus in a declarative way and without any need for libraries like PopperJS [2] [1] https://developer.chrome.com/blog/tether-elements-to-eac…

I just shipped a new article all about how to use the CSS anchoring API, which is landing in Chromium next week! https://developer.chrome.com/blog/anchor-positioning-api

The source link at the top of the article leads to a 404.

Re: Popover API

#152

Post by [deleted] »

nerdponx wrote: post #45
bestest wrote: post #18

Earlier quoted context omitted.

I think you're comparing apples with grapples. A popover is floating element that appears to display a contextual piece of information when required. What you're mentioning is something completely different.

And surely this new API will not be abused. Right?

[deleted]

Re: Popover API

#153

Post by chrishtr »

swyx wrote: post #148
mardifoufs wrote: post #139

Earlier quoted context omitted.

I love articles with actual running examples, thanks! Now I'm wondering how quickly this will get adopted, it looks very cool!

whats a reasonable expectation for this to get adopted across safari/firefox/edge? 1yr? 3yrs?

Implementation already begun for Firefox:

https://groups.google.com/a/mozilla.org/g/dev-platform/c/4cb...

Re: Popover API

#154

Post by karaterobot »

staminade wrote: post #60
jcutrell wrote: post #49

Earlier quoted context omitted.

How is anchor different from relative?

The article I linked goes into the details, but basically a relative approach constrains your markup: The positioned thing must be a child of the relatively positioned anchor or a wrapper element, and you often cannot sensibly position it without using JS to check the location of the anchor. E.g. a popover menu for a button must check if the button is close to an edge of the viewport and position the menu element app…

I've been eagerly awaiting anchor positioning, but using it for diagram connectors had not occurred to me yet! That would solve so many problems that I currently have (or plan) to use D3 for.

Re: Popover API

#155

Post by threatofrain »

betagammaxyz wrote: post #103
threatofrain wrote: post #46

Earlier quoted context omitted.

Let's say there's a native app that can also do pop ups. What's to stop the native app from basically stealing the likeness of your password manager? In other words, as web apps seek to become like native apps, they may also accrue the risks which are characteristic of that space.

There's not much to stop what you describe, other than the trust you place in a native app when you install it. Super common experience to have to give superuser access once during an installation process, and most bets are off regarding security once you do that. That's part of the added friction involved in running a native app; you have to trust it more. Only other alternative I can think of would be an Apple App…

I see two parts to this. One is the role of user choice in deterring system damage from bad apps, and the other is the role of app stores in shielding the user from having to make this choice to begin with.

On the matter of websites, if the decision rests on individual choice, then individuals certainly have a choice to visit (and thus trust) a particular domain name and cert. That users need merely type in a name, and that there's a giant company helping you search for these apps, simply means that web apps are easy to find and install (and native apps are only slightly harder to install).

Then there's the role of the app stores, which I imagine practically deals with the supermajority of garbage, spams and scams out there. We could also have orgs whose sole job is to maintain lists of credibility, if that's what people want. Then a web user could download a browser extension or use a browser that subscribed to these lists by default. In some ways that's what ad blockers are, except ad blockers are even more precise and there's nothing quite like it in the native world.

Re: Popover API

#157

Post by chrismorgan »

tomsmeding wrote: post #83
clementmas wrote: post #52

Earlier quoted context omitted.

As someone pointed out, it's indeed harder to animate but it's fully accessible, supports escape key to close, has a built-in backdrop and has built-in focus trap. Safari took a while to support it but now it's available everywhere. I think it's better than using a tag.

Apparently it's unsupported in the Firefox ESR version in Ubuntu 20.04, which still receives support from Canonical until 2025. I found that out because someone reported that my site didn't work.

This doesn’t sound right at all.

Ubuntu itself doesn’t have an ESR package, only https://packages.ubuntu.com/focal/firefox which is at 125.

The Mozilla PPA does have an ESR package, but per https://launchpad.net/~mozillateam/+archive/ubuntu/ppa?field... it’s at 115.

has been supported since Firefox 98, meaning ESR 91 was the last release lacking it, and it reached end of support over a year and a half ago.

Re: Popover API

#159

Post by antifa »

sseagull wrote: post #121
The_Colonel wrote: post #110

Earlier quoted context omitted.

I don't think this is often called "pop-up", mostly I see either popover or tooltip.

Maybe by developers. But the public certainly calls them pop-ups https://www.google.com/search?hl=en&q=%22newsletter%20pop%2D...

Either way those are called modals, not popovers.

Re: Popover API

#160

Post by SushiHippie »

nojs wrote: post #94
delichon wrote: post #53

These are popovers: https://kagi.com/proxy/passover-popovers-6.jpg?c=gBnCtLe1QYl... No you can't have that word to mean something else, it's sacred. And because you tried you can't have any of my popovers either.

That is quite a curious URL. The querystring is identifying the file, but it looks as if it’s hosted at https://kagi.com/proxy/passover-popovers-6.jpg

That's the image proxy from the kagi search engine.

It's very likely built this way so

a) if you download it the image has the correct file name

b) the source URL is encoded in the query string and you can't abuse Kagi as a 'file host' by just plugging in any URL

Post reply on HN