Closed
Bug 342096
Opened 18 years ago
Closed 18 years ago
Flash movie mouse positioning is off, when WMODE is other than windowed and flash is positioned higher than top edge of page
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mdoemling, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
There are alignment circumstances under which a flash movie assumes incorrect mouse positions, i.e. the actual mouse position is different from what the flash "thinks" it is. This prevents proper use of flash buttons or any other functionality that requires mouse positioning.
The following conditions will cause this flash mouse positioning bug:
- the WMODE of the flash is other than the default of "windowed"
- the positioning of the flash is such that its top edge is higher (or same height) than that of the page, i.e. "top" is <= 0.
When repositioning the flash dynamically with javascript the problem goes away, i.e. this may be repaint related.
I wonder if the underlying cause for this bug is the same as for bug 266933 (https://bugzilla.mozilla.org/show_bug.cgi?id=266933). That bug, by the way, is reported as FIXED, but in fact it is not fixed.
Reproducible: Always
Steps to Reproduce:
1. See test case
This bug has been around for a long time, I think pre 1.0.
Updated•18 years ago
|
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → Trunk
Comment 1•18 years ago
|
||
I've tried the testcase with my debug build which has the fix for bug 271442.
It seems fixed with that.
Depends on: 271442
Comment 2•18 years ago
|
||
This is worksforme with current branch (1.8.1) and trunk build.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
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
•