1478806 - Get rid of nsIBrowserElementNextPaintListener

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, enhancement)

Description

[Boris Zbarsky [:bzbarsky]]

There's no particular reason for us to have this interface.  The only consumer is JS-implemented, and the only caller has JS values to start with; we can just pass these as jsval.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Attachment: Remove nsIBrowserElementNextPaintListener

Comment 2

[Andrew McCreight [:mccr8]]

Comment on attachment 8995333 [details] [diff] [review]
Remove nsIBrowserElementNextPaintListener

Review of attachment 8995333 [details] [diff] [review]:
-----------------------------------------------------------------

Please put something like your comment 0 in the bug into the commit message.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Attachment: Additional fix needed to make this actually work

I forgot that passing things through xpconnect like that would double-wrap instead of unwrapping... In the new setup we need to call the function directly, not call its member.

Gotta love code that catches exceptions and doesn't report them in any way.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/3ccc5dbbd0b8
Remove nsIBrowserElementNextPaintListener.  r=mccr8

Comment 5

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/3ccc5dbbd0b8