Closed Bug 741754 Opened 13 years ago Closed 12 years ago

Dynamically added Flash plugins are shown as plugin placeholders even when plugins are set to allowed on that site

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: martijn.martijn, Unassigned)

References

()

Details

(Keywords: testcase)

You need to have the Setting for Plugins set to "Tap to Play" to see this bug. Steps to reproduce: - Visit http://people.mozilla.org/~mwargers/tests/plugins/flash/flashembed_dynamicrepeating.html every 2 seconds a new Flash plugin is being created - The plugin doorhanger appears, tap on "Yes" to play it Expected result: - Flash plugins are shown, every new Flash plugin that is created should directly be shown as a Flash plugin, not as plugin placeholder Actual result: - Existing Flash objects are shown as Flash plugins now, but newly created Flash objects are rendered as plugin placeholders. Tested on the Samsung Galaxy Nexus, yesterday's trunk build.
Summary: Dynamically added Flash plugins are not → Dynamically added Flash plugins are shown as plugin placeholders even when plugins are set to allowed on that site
That's odd. I would have thought clickToPlayPluginsActivated would have caught that: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#1930
I think bug 741128 might have fixed this. I'm seeing activated flash objects instead of placeholders. The quality of the flash content is bad (some of the squares are all black or all white), but that's likely a different bug.
Blocks: 744060
Martijn, are you still seeing this issue? My comment in comment 2 makes it sound like this got fixed.
Yes, I'm still seeing this in the build from 2012-04-10.
Ok, this is wfm now in 2012-04-14 trunk build on the Samsung Galaxy Nexus. No idea what fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.