Closed Bug 707913 Opened 13 years ago Closed 9 years ago

No Comply demo doesn't work

Categories

(Web Compatibility :: Site Reports, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: spammaaja, Unassigned)

References

()

Details

(Keywords: regression)

Error: uncaught exception: [Exception... "Not enough arguments [nsIDOMWindow.mozRequestAnimationFrame]" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: https://developer.mozilla.org/media/uploads/demos/p/a/paulrouget/48e4f7c1e4f72277868270f10ea80ed8/no-comply_1322595143_demo_package/sequences.js :: <TOP_LEVEL> :: line 387" data: no] Error: uncaught exception: [Exception... "Not enough arguments [nsIDOMWindow.mozRequestAnimationFrame]" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: https://developer.mozilla.org/media/uploads/demos/p/a/paulrouget/48e4f7c1e4f72277868270f10ea80ed8/no-comply_1322595143_demo_package/sequences.js :: startDemoInterval :: line 461" data: no] Regression range: Good: http://hg.mozilla.org/mozilla-central/rev/bc48009a6bbb Bad: http://hg.mozilla.org/mozilla-central/rev/cc94a16983b0 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=bc48009a6bbb&tochange=cc94a16983b0
Keywords: regression
Bug 704171 - Remove the no-argument form of requestAnimationFrame Done intentionally?
Component: DOM → English US
Product: Core → Tech Evangelism
Version: Trunk → unspecified
(In reply to JK from comment #1) > Bug 704171 - Remove the no-argument form of requestAnimationFrame > > Done intentionally? Yeah.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Yep, this is using a Gecko-only feature that we removed.
Assignee: nobody → english-us
QA Contact: general → english-us
Blocks: 704171
@dmose, @cj, can you please look at this?
Hmm, I've never used it in this fashion myself -- I think Dave did the mozRequestAnimationFrame patch. What's the difference here? -- is it just that the mozRequestAnimationFrame function used to call back to wherever it was called from? If so I should be able to patch that up quickly.
It used to fire the MozBeforePaint event. So if you're adding functions as listeners for that event, you should just pass those same functions directly to mozRequestAnimationFrame.
The MozBeforePaint and empty mozRequestAnimationFrame is now fixed up in the latest commit at: https://github.com/cjcliffe/NoComply/commit/01d994e440cc12b5c5fcaa56b4476c6a05fb09db Whatever was broken in Firefox with workers between 7.x and 8.x still affects it though so it will halt before the tunnel scene. I don't know enough about debugging the workers in that code so it will remain broken until someone can investigate.
Still broken. Moving to desktop component.
Assignee: english-us → nobody
Component: English US → Desktop
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.