Closed
Bug 1463387
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 11100 - Fix crash when setting aliases on computed style.
Categories
(Core :: DOM: CSS Object Model, enhancement, P4)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 11100 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/w3c/web-platform-tests/pull/11100
Details from upstream follow.
Anders Hartvoll Ruud <andruud@chromium.org> wrote:
> Fix crash when setting aliases on computed style.
>
> The incoming CSSPropertyID may be an unresolved property, therefore
> CSSUnresolvedProperty::Get must be used rather than CSSProperty::Get.
>
> This bug exists in Chrome stable as well, but it was pretty hard to
> discover (by e.g. ClusterFuzz) because aliases were not enumerated until
> recently.
>
> R=futhark@chromium.org
>
> Bug: 844816
> Change-Id: I97c81764d2027f86004d3b02316cac44412ef0ea
> Reviewed-on: https://chromium-review.googlesource.com/1065993
> WPT-Export-Revision: 9f9e733d745ab5ad3885e0f8f8bff99716660390
| Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → DOM: CSS Object Model
Product: Testing → Core
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
Ran 1 tests and 5 subtests
OK : 1
PASS : 5
| Assignee | ||
Comment 4•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=fa3cd307936a46602f8ec160b1d90cea04edfd15
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a2f445725579
[wpt PR 11100] - Fix crash when setting aliases on computed style., a=testonly
Comment 6•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•