774939 - Re-enable browser-frame OOP tests for native-android

Status: REOPENED

(Core :: DOM: Core & HTML, defect, P5)

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

After bug 745148, they'll end up running the tests with direct compositor, content pushing layers updates directly to the compositor thread in the parent process.  This configuration is not supported on native-android, and the tests are crashing because of that.

Comment 1

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Attachment: Disable OOP browser-element tests for native-fennec

irc-r=jlebar

Not assigning to myself because I'm not going to work on reenabling these tests for the foreseeable future.

Comment 2

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

https://hg.mozilla.org/integration/mozilla-inbound/rev/c1d2d986d4ef

Please leave this bug open after merging.

Comment 3

[Justin Lebar (not reading bugmail)]

See also bug 766586, and https://hg.mozilla.org/integration/mozilla-inbound/rev/3c6c55befb22.  I was doing to ask that we take the same approach as in the linked cset to disable the tests, but then every test we add would have to be added to that manifest, which would be pretty annoying.

Comment 4

[Ed Morley [:emorley]]

https://hg.mozilla.org/mozilla-central/rev/c1d2d986d4ef

Comment 5

[Justin Lebar (not reading bugmail)]

I think if you want to leave a bug open these days, you have to put something in the whiteboard.

Comment 6

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.