Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mas.to is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hello! mas.to is a fast, up-to-date and fun Mastodon server.

Administered by:

Server stats:

13K
active users

mas.to: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.5

Matthias Zöchling

Hello and people, can you help me figure out which browser behavior is correct? It’s about the Popover API and the Top Layer:
cssence.com/2024/popover-inset

Please be Firefox, please be Firefox. 🤞

cssence.comThe Popover API and inset:unsetInconsistent cross-browser behavior on the top layer.
#WebDev#Browsers#Bug
Dec 17, 2024, 11:03 AM·Public·Web
1boost·0favorites
Public
Matthias Zöchling

@pepelsbey Great, thank you, that helps. So yeah, judging by your thread, it's still TBD.

Eventually it won't matter much because we'll just anchor-position everything.

Nevertheless, there should be concensus among browsers, one way or another. Based on what I've read in the blog post from @hdv, I'm guessing it's gonna be "another":

> In summary, elements lose their position context when they are upgraded to the top layer. And that's okay, we have other options.
—hidde.blog/positioning-anchore

Hidde's blogPositioning anchored popoversPopovers are in the top layer, how can we position them relative to invokers that are not?
ExploreLive feeds
About