Closed
Bug 1212803
Opened 9 years ago
Closed 7 years ago
on Firefox41/42+ wmode=direct breaks flash setting panel
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: eric.helier, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150929144111
Steps to reproduce:
Since Firefox41 update, we are unable to click on flash settings panel (webcam activation in particular) on our application that requires wmode=direct (stage3d content).
Our application can be tested here :
http://fitlive.youarethemodel.com/examples/basic.html
Other similar applications that behave the same :
https://www.beyond-reality-face.com/overview#techdemo-app
http://www.trylive.com/demos/trylive-eyewear/player-fitting-room
Note that it seems related to the wmode "direct" value.
See for example this application (wmode opaque) works (even if it is hard to click on the buttons of settings panel) :
http://fitphoto.youarethemodel.com/demoflash/test-fitproducts-v4.html
Actual results:
Clicks on the flash security panel don't work
Expected results:
Clicks on the flash security panel should work
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Reporter | ||
Comment 1•9 years ago
|
||
I just updated to Firefox 41.0.2 and still the same problem occurs
Reporter | ||
Comment 2•9 years ago
|
||
Firefox 42.0.0 do not resolve theproblem
Severity: normal → critical
Hardware: x86_64 → All
Version: 41 Branch → 42 Branch
Reporter | ||
Updated•9 years ago
|
Summary: on Firefox41 wmode=direct breaks flash setting panel → on Firefox41/42+ wmode=direct breaks flash setting panel
Comment 3•9 years ago
|
||
We are also facing this bug on Mozilla 42 on Windows 8.
Reporter | ||
Comment 4•9 years ago
|
||
It seems it has been resolved with Firefox v43
Comment 5•9 years ago
|
||
Not is is not fixed. I can still see it inside firefox v43. Even with the keyboard we are unable to click the buttons.
Comment 6•9 years ago
|
||
I upgraded my FF to 43.0.4 and the issue has been resolved. Guys could you please confirm
![]() |
||
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•