Closed Bug 1081380 Opened 10 years ago Closed 8 years ago

AVM1 MovieClipLoader and loadee have wrong sequence of events

Categories

(Firefox Graveyard :: Shumway, defect, P3)

Product:
Firefox Graveyard
Component:
Shumway
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: yury, Unassigned)

References

Details

The loadee frame scripts starts executing prior MovieClipLoader onLoadComplete event. The test case was disabled at https://github.com/mozilla/shumway/commit/6f577a04ab3f07acf1ab4e23c591f5b0ff6b211a after fixing bug when _initAvm1() is executed twice (https://github.com/mozilla/shumway/commit/9cdf995b2a235f133715e4932c5202d84333cb1d). (Test was passing due to artificial delay created by another AVM1 instance loading)

Per documentation, any movie navigation shall be disabled before onLoadComplete.
See also http://logs.glob.uno/?c=mozilla%23shumway#c77686
Priority: -- → P3
Unclear if this affects any content, but we should re-check before launch.
Assignee: till → nobody
Blocks: shumway-m5
No longer blocks: shumway-m3
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.