Closed
Bug 1335733
Opened 7 years ago
Closed 7 years ago
flash doesn't respond to mouse when window is maximized (Nightly regression)
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(firefox53 unaffected, firefox54 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox53 | --- | unaffected |
firefox54 | --- | affected |
People
(Reporter: nivtwig, Unassigned)
References
()
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170131030205 Steps to reproduce: Open http://www.mako.co.il/mako-vod with Firefox Nightly (currently on 54.0a1 (2017-01-31) (32-bit)), move the mouse over the menu items, click on one of them. Try this when the Firefox window is not maximized (make the window smaller), and when it is maximized, with Firefox Nightly and stable. Actual results: When the window is maximized the flash content in the site doesn't respond to mouse moves and clicks . It may sometimes respond, because the mouse events are offset left to some other location, and it "thinks" the event is somewhere more to the left of the screen than the actual location. Expected results: The flash content should respond to mouse events, moves and click, in the correct location. This works correctly when the window is not maximized , or with the release version of Firefox, but not with the Nightly version when the window is maximized.
Severity: normal → critical
Keywords: regression
OS: Unspecified → Windows 7
Hardware: Unspecified → x86
Comment 1•7 years ago
|
||
Stefan can you reproduce and check whether this is related to async drawing?
Flags: needinfo?(stefan.georgiev)
Comment 2•7 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 (20170201030207) I was able to reproduce the issue on latest Nightly 54.0a1 32 bits and not able to reproduce it on latest Nightly 64bits. However when I flip the pref dom.ipc.plugins.asyncdrawing.enabled to false the issue is no more reproducible on either builds. In this case the issue is more likely to be related to aSync Drawing.
Status: UNCONFIRMED → NEW
status-firefox53:
--- → unaffected
status-firefox54:
--- → affected
Ever confirmed: true
Flags: needinfo?(stefan.georgiev)
OS: Windows 7 → Windows
Updated•7 years ago
|
Comment 3•7 years ago
|
||
nivtwig, is the user agent in your report the one from the machine/build you were seeing this bug on? If not, what was the OS?
Flags: needinfo?(nivtwig)
(In reply to Tracy Walker [:tracy] from comment #3) > nivtwig, is the user agent in your report the one from the machine/build you > were seeing this bug on? If not, what was the OS? Yes, I saw this on Windows 7,32 bit. The user agent came from the same machine I saw this on. You could also see that in the bug report, I set the OS field to "Windows 7", which was later changed by Stefan to "Windows".
I reduced the importance from Critical to Normal since there is a workaround : disabling async drawing by setting dom.ipc.plugins.asyncdrawing.enabled to false, in about:config.
Severity: critical → normal
Updated•7 years ago
|
Blocks: flash-async-drawing
Comment 6•7 years ago
|
||
Can't reproduce, everything appears responsive to me. Tracy, please try to reproduce. Let get this added to our flash bug list too.
Flags: needinfo?(twalker)
I am the reporter. It works for me now on the latest nightly (as Jim claimed) . It was probably fixed.
Comment 8•7 years ago
|
||
I can not reproduce this either with latest Nightly 54.0a1, 20170228030203.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(twalker)
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•