Showing results for 
Show  only  | Search instead for 
Did you mean: 
Strollin' around
Status: New idea

With the introduction of chrome and edge ver. 114, the popover API which allows previously hidden content to be toggled in-and-out of view.

This functionality is usually implemented with 3rd party JS libraries like Popper.js which are quite popular, even attracting sponsorships from companies like Twitch and Microsoft

As of now, Firefox on ver. 113 does not have any support, full or partial for this API; and over the coming weeks and month the usage for 3rd party JS libraries is likely to decline due to this functionality already being baked into rendering engines.

Further Reading:

Status changed to: New idea
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

New member

Popover is now supported by all major browsers apart from Firefox:

From what I can tell, this is being worked on with no priority?

This would be amazing to have, especially in context with accessibility with web components (e.g. to implement custom dialogs, tooltips, autocompletes, etc.).

Strollin' around

I would also love to see Firefox supporting the popover API! There are so many great use cases like: tooltips, snackbars, autocomplete, calendar picker, etc. Having popover would make it easier to create robust, accessible custom components.

New member

I'd love to use it, but the thing that's disabled by default and user needs to enable it from config pushes me use libs like Popper.js and etc.

Is there any plan to enable it by default in the future releases ?
Any estimates maybe?

Thank you!

New member

is supported but not enabled by default.. why ?

New member

Is there an ETA for official release?

New member

I thought it was going to be released in Firefox 124 and it just delayed.

Am I suppose to add "Stop using outdated browser like Firefox" warning on my Website 🫠?

Strollin' around

I'm trying hard to continue using and supporting Firefox, but I have to admit it's a bit disheartening to see it constantly coming behind the other browsers. Ever so often I stumble upon a (more or less) new web feature which is implemented in "all" the other browsers (Chrome, Safari, Edge) and then I check Firefox and it's not there yet.

As a developer it felt like a small eternity before the :has() selector was finally supported in Firefox 121. Of course it's all relative. I still have occasional nightmares from making IE 5 exceptions to the code, but those times are long gone. Now web moves forward at an enormous pace. Web developers expect browser to adapt new features faster and faster. And sadly quite often other browsers are managing to do so faster than Firefox.

This time it's the Popover API which is super handy for many things like tooltips, popovers, autocompletes etc. I've already done a feature check in my code to use Popover API for the browsers that support it, but now I have to maintain some nasty legacy logic just for Firefox.

I have a gut feeling that the CSS anchor positioning will be the next thing that will be adapted into other browsers and then again I have to wait for Firefox to (hopefully) implement it some day. That will furthermore help me to get rid of pesky positioning code as the CSS anchor positioning takes care of that for me.

I think Firefox is in a difficult spot and I really hope that you'll find a way to get the momentum back, support new web features faster and really fight the other major browsers for a better market share. But for now I'm seriously considering to switch to Chrome and let go of the Firefox exceptions in our codebase and just forward Firefox users to a page where we suggest to use Chrome, Safari or Edge 😥


Yes, we acknowledge the absence of this API in Firefox. Here is a meta bug for this API:

(you might want to monitor it to see progress)

It is highly probable that support for Popover will be completed in 2024.