Closed
Bug 1461092
Opened 7 years ago
Closed 7 years ago
Unship GetPropertyCSSValue in beta.
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
(Keywords: site-compat)
Attachments
(1 file)
1.08 KB,
patch
|
xidorn
:
review+
RyanVM
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Xidorn pointed out in dev-platform@ that this is probably safer to do in 61, and I think I agree.
Assignee | ||
Comment 1•7 years ago
|
||
Approval Request Comment
[Feature/Bug causing the regression]: N/A
[User impact if declined]: N/A
[Is this code covered by automated tests?]: N/A
[Has the fix been verified in Nightly?]: N/A
[Needs manual test from QE? If yes, steps to reproduce]: N/A
[List of other uplifts needed for the feature/fix]: none
[Is the change risky?]: not risky
[Why is the change risky/not risky?]: This API has been unshipped in the 61 nightly cycle already without any reported problem (see dependent bug). We're going to unship it in 61 directly.
[String changes made/needed]: none
Attachment #8975244 -
Flags: review?(xidorn+moz)
Attachment #8975244 -
Flags: approval-mozilla-beta?
Updated•7 years ago
|
Attachment #8975244 -
Flags: review?(xidorn+moz) → review+
Keywords: site-compat
Comment 2•7 years ago
|
||
Comment on attachment 8975244 [details] [diff] [review]
Unship getPropertyCSSValue in beta too.
I read through the dev-platform thread and it sounds like everyone's on board with flipping this pref on 61. Approved for 61.0b5.
Attachment #8975244 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 3•7 years ago
|
||
uplift |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Updated the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/cssstyledeclaration-getpropertycssvalue-has-been-deprecated/
You need to log in
before you can comment on or make changes to this bug.
Description
•