Closed
Bug 1383494
Opened 7 years ago
Closed 3 years ago
Flash objects have screen tearing on Hi-DPI displays if wmode is either "transparent" or "opaque"
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: doomtay, Unassigned)
Details
(Keywords: flashplayer)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170628075643 Steps to reproduce: Open up Firefox on a Hi-DPI Monitor Visit a page with a Flash object, such as http://www.konami.jp/gs/game/mpo+/en/top.html Mouse over character options Actual results: The "currently selected option" bar and other parts of the menu are only partially updated. Expected results: Flash rendering should be updated in full Curiously, this bug only manifests when viewing the SWF from the web page. Viewing the SWF directly (http://www.konami.jp/gs/game/mpo+/en/mpo.swf) works just fine.
Updated•7 years ago
|
Screen tearing also occurs with Nicoviewer's flash player (i.e. http://nviewer.mobi/player?video_id=sm31457372) and http://melusine.eu.org/syracuse/swf/1-mandel/ but not places like Newgrounds or Kongregate
Culprit seems to be wmode being set to either "opaque" or "transparent"
Summary: Flash objects have screen tearing on Hi-DPI displays → Flash objects have screen tearing on Hi-DPI displays if wmode is either "transparent" or "opaque"
Comment 3•7 years ago
|
||
I can't reproduce this in nightly (didn't try 54). But if it's true it's something we should look into, since we're moving all plugins to windowless. NI?qdot because of his history with bug 820831
Flags: needinfo?(kyle)
Comment 4•7 years ago
|
||
Oh! I can reproduce this with async drawing *off*, but not on. Which means this can still affect win32 release where we have async off, but won't affect win64 by default any more. Jim, do you have a roadmap/plan for turning async drawing on for win32?
Flags: needinfo?(jmathies)
Updated•7 years ago
|
Flags: needinfo?(kyle)
Comment 5•7 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #4) > Oh! I can reproduce this with async drawing *off*, but not on. > > Which means this can still affect win32 release where we have async off, but > won't affect win64 by default any more. Jim, do you have a roadmap/plan for > turning async drawing on for win32? Yes, rolling out in 55, 54 has 64-bit enabled. (In reply to doomtay from comment #2) > Created attachment 8889706 [details] > lagtest.html > > Culprit seems to be wmode being set to either "opaque" or "transparent" https://wiki.mozilla.org/Plugins/Async_Drawing#Current_WMODE_Handling For opaque you'll get async non-acclerated painting, and for transparent you'll get the slowest path we have, sync non-acclerated painting. It's better to leave wmode undefined, or choose direct if you can.
Flags: needinfo?(jmathies)
Thanks for the advice. Sadly, this is concerning third-party websites which I have no control over.
Comment 7•7 years ago
|
||
Still seeing this in the latest release (56)?
Flags: needinfo?(doomtay)
Priority: -- → P3
There is no more screen tearing as of v56 for all six wmode settings
Flags: needinfo?(doomtay)
Comment 9•3 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
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
•