Closed
Bug 1565350
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 17778 - [css-transforms] Avoid using assert_own_property on testing style properties.
Categories
(Core :: CSS Parsing and Computation, task, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla70
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 17778 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/17778
Details from upstream follow.
Boris Chiou <boris.chiou@gmail.com> wrote:
[css-transforms] Avoid using assert_own_property on testing style properties.
These
assert_own_property
tests cause these CSS tests to fail on Firefox only, and I think these properties are not supposted to be own properties, so use a similar way as https://github.com/web-platform-tests/wpt/pull/16892, to test the existence of these properties.cc @emilio
Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=e2355241748b394270a43ec7df3c7e494c4163ff
Updated•5 years ago
|
Type: -- → task
Assignee | ||
Comment 2•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=5aa14f6b87a37ccfe4f8678219f4125cf5afaf95
Assignee | ||
Comment 3•5 years ago
|
||
Failed to get results from try push
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/3f420b25532c [wpt PR 17778] - [css-transforms] Avoid using assert_own_property on testing style properties., a=testonly
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in
before you can comment on or make changes to this bug.
Description
•