Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gecko Bug 1545239] Make each test cases independent in resize-observer/observe.html. #16877

Merged
merged 3 commits into from May 16, 2019

Conversation

moz-wptsync-bot
Copy link
Collaborator

I think it's better to make sure each test is independent from others, so we
create elements inside each test function. (Only change observe.html
because I touch only this file in this bug.)

Differential Revision: https://phabricator.services.mozilla.com/D29889

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1545239
gecko-commit: 01338a1e26b7d838ddd591fca9a7495e338c6c96
gecko-integration-branch: central
gecko-reviewers: dholbert

I think it's better to make sure each test is independent from others, so we
create elements inside each test function. (Only change observe.html
because I touch only this file in this bug.)

Differential Revision: https://phabricator.services.mozilla.com/D29889

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1545239
gecko-commit: 01338a1e26b7d838ddd591fca9a7495e338c6c96
gecko-integration-branch: central
gecko-reviewers: dholbert
1. Add new tests with an extra argument of "content-box"/"border-box" in
   observe(), and test contectBoxSize and borderBoxSize.
2. Add a new test for changing the writing mode. Changing writing mode makes
   the element change the orientation, but the logical box size is still
   the same, so we shouldn't fire the event.

Differential Revision: https://phabricator.services.mozilla.com/D28739

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1545239
gecko-commit: b34ea6abce97b002de66d2d0376b84e347f3151a
gecko-integration-branch: central
gecko-reviewers: dholbert
Differential Revision: https://phabricator.services.mozilla.com/D30129

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1545239
gecko-commit: a0c91ab4d3477cdb041c00dee13354cafafb83fd
gecko-integration-branch: central
gecko-reviewers: dholbert
Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

@dholbert
Copy link
Contributor

CC @BorisChiou
The nightly-stability test failures start with:

TEST-UNEXPECTED-FAIL | /resize-observer/idlharness.window.html | ResizeObservation interface: existence and properties of interface object - assert_own_property: self does not have own property "ResizeObservation" expected property "ResizeObservation" missing

https://taskcluster-artifacts.net/ZXxdYQZVT3W96ftXdDMiaQ/0/public/logs/live_backing.log

@dholbert
Copy link
Contributor

It looks like that failure is really a bug in the test, and is tracked in w3c/csswg-drafts#3839

@dholbert
Copy link
Contributor

So the firefox-nightly-stability "failure" here is actually Firefox getting the correct result, and is a test-issue that predates this change (per w3c/csswg-drafts#3839 ).

So, we should disregard that & should consider this pull request as force-merge-worthy. CC @gsnedders would you mind helping with that?

@jgraham
Copy link
Contributor

jgraham commented May 16, 2019

I can help!

@jgraham jgraham merged commit 3d80ec3 into master May 16, 2019
@dholbert
Copy link
Contributor

Thanks @jgraham! And sorry to frequently bug you for this sort of thing, @gsnedders - I should bias more towards @jgraham. :D

@moz-wptsync-bot moz-wptsync-bot deleted the gecko/1545239 branch May 16, 2019 16:26
@dholbert
Copy link
Contributor

Also: sorry, my diagnosis in #16877 (comment) was actually wrong (but all is well).

The real reason the firefox-nightly-stability task failed was because of a stability issue, not a test-failure issue. Specifically, the resize-observer/eventloop.html test failed sometimes and passed other times.

Anyway, that's not a concern here because:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants