Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

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

Adobe Flash shows correct version, but FF 34.0 claims Flash needs update

  • 3 Mbohovái
  • 3 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva alphaa100

more options

Firefox does not seem aware of the Adobe Flash version it runs under Plug-Ins. The current Flash version is NPAPI 16.0.0.296, and that version is displayed by FF 34.0. Yet, FF34.0 flags that condition with an error message "Shockwave Flash is known to be vulnerable and should be updated"

This error was reported perhaps one year ago, but I did not locate the earlier reference, nor its resolution (if any).

Firefox does not seem aware of the Adobe Flash version it runs under Plug-Ins. The current Flash version is NPAPI 16.0.0.296, and that version is displayed by FF 34.0. Yet, FF34.0 flags that condition with an error message "Shockwave Flash is known to be vulnerable and should be updated" This error was reported perhaps one year ago, but I did not locate the earlier reference, nor its resolution (if any).

Opaite Mbohovái (3)

more options

Ñemoĩporã poravopyre

more options

The current Flash version is NPAPI 16.0.0.305. That version was just released just a few days ago. Get it here: https://www.adobe.com/products/flashplayer/distribution3.html

more options

Thanks to both james and the-edmeister for prompt response. This is a somewhat egg-on-the-face moment, since outwardly it appears I had not done due diligence by checking once again before posting my problem.

I say "once again" because my post was made days after first finding the erroneous FF error message. On that discovery, I did check with Adobe and did update, and still got the error even after updating, and restarting the session.

Convinced that the error had continued, I did not check again with Adobe, but decided to put the matter to rest by posting the problem. As it turned out, the ever-elusive latest Adobe version had changed, once again. Give Flash five minutes, and it will need more attention.

Anyway, with two prompt replies, I am assured more than one person will notice if and when FF falls into that behavior again..

Moambuepyre alphaa100 rupive