Closed
Bug 1080954
Opened 10 years ago
Closed 9 years ago
SWF #106 background is blue, but should be green
Categories
(Firefox Graveyard :: Shumway, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: cpeterson, Unassigned)
References
Details
Reporter | ||
Comment 1•10 years ago
|
||
"Dropped tag during parsing. Code: 77 (CODE_METADATA)" base.js:26
"Dropped tag during parsing. Code: 73 (CODE_DEFINE_FONT_ALIGN_ZONES)" base.js:26
"Dropped tag during parsing. Code: 88 (CODE_DEFINE_FONT_NAME)" base.js:26
"Dropped tag during parsing. Code: 74 (CODE_CSM_TEXT_SETTINGS)" base.js:26
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → mbebenita
Blocks: shumway-m3
Reporter | ||
Updated•10 years ago
|
Priority: -- → P3
Comment 2•10 years ago
|
||
For me, this is green in Flash as well. Looks really good except for drop shadows, in fact. M4 in any case.
Assignee: mbebenita → nobody
Reporter | ||
Comment 3•10 years ago
|
||
Strange. Flash renders the background as green when loading the SWF URL directly in a tab, but blue when loading the SWF in the SWF Archive viewer.
Reporter | ||
Comment 4•10 years ago
|
||
I think we should try to maintain quirk compatibility with Flash, where practical. I'm reopening this bug and moving it from M4 to M5 because the swf looks correct when it is embedded as it would be as an ad.
In the SWF Archive viewer, both Shumway and Flash render the background as blue. I have canvas.filters.enabled=true, if that matters.
http://swf.codeazur.com.br/#d89c97e2a97a291f0375d97bf222aa33271d850727f5a8066b47d4a66bec1f06
But the standalone swf's background is blue in Shumway and green in Flash (even in Chrome)?!
http://swf.codeazur.com.br/archive/d8/9c/97/e2/d89c97e2a97a291f0375d97bf222aa33271d850727f5a8066b47d4a66bec1f06.swf
Summary: SWF #106 background is green, but should be blue → SWF #106 background is blue, but should be green
Assignee | ||
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•