Closed
Bug 492012
Opened 16 years ago
Closed 15 years ago
SWF does not get correctly the onclick event if an "overflow:hidden" div is behind it
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: rober.morales, Unassigned)
References
()
Details
(Whiteboard: [CLOSEME 2010-12-01])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Right-Click in a zone that overlap an "overflow:hidden" div throws the contextual menu away. Right-Click in the rest of the SWF runs as expected.
Reproducible: Always
Steps to Reproduce:
1.http://82.223.160.224/css/bug_firefox_swf/swf_flash.html
2.Right-Click on the swf (over the div)
3.Right-Click on the swf (out of the div)
Actual Results:
Contextual menu is not displayed properly, such as left-click events on the play button.
Expected Results:
Clicks runs well with the "overflow:hidden" div, as without this.
Trident and WebKit renders correctly this html and manage correctly the click.
The "click" feature and the "embeding SWF" feature are very common and important.
Severity is Major.
Any comment on that issue?
While, we are using Chrome. (We need that for using a corporative site)
Comment 2•15 years ago
|
||
Can you retest using latest truck nightly?
http://nightly.mozilla.org/
Comment 3•15 years ago
|
||
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
All seems ok.
Thanks you.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•