We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

How come in Firefox Nightly the Flash Player plugin will not update to the newest version?

  • 4 Mbohovái
  • 218 oguereko ko apañuãi
  • 1 Hecha
  • Mbohovái ipaháva eagle_storm

more options

I use Firefox Nightly and whenever I attempt to update the Flash Player plugin to the newest version it doesn't update. If I check the version of Flash in Aurora it has the newest version, yet Nightly remains the same. Why will the Flash plugin in Nightly not update? Is there a way of updating the Flash plugin in Nightly or not?

I use Firefox Nightly and whenever I attempt to update the Flash Player plugin to the newest version it doesn't update. If I check the version of Flash in Aurora it has the newest version, yet Nightly remains the same. Why will the Flash plugin in Nightly not update? Is there a way of updating the Flash plugin in Nightly or not?

Opaite Mbohovái (4)

more options

I solved this problem by installing this.

http://labs.adobe.com/downloads/flashplayer10_square.html

more options

I've tried that also, that's the first thing I did. For some reason, Nightly still doesn't recognize the change in the version of Flash. I thought it might have something to do with the directory in which Nightly was installed, so I uninstalled it and then reinstalled it, same problem. I'm wondering if maybe Nightly is sort of locked down, if you will, and all of the plugins etc are the same for everyone to provide a true control group for testing purposes.

more options

You can see the installed plugins on the about:plugins page.
You can set the pref plugin.expose_full_path to true on the about:config page to see the full path of plugins on the about:plugins page.
It is best not to leave that pref set to true as it exposes that full path to web servers, so reset that pref to false after you are done with the about:plugins page.

You can open about:plugins and about:config via the location bar, like you open a website (about: is a special protocol to access some build-in pages).
If you get a warning when opening the about:config page then you can confirm that you want to continue.

more options

Solved.. Thank You