Closed Bug 1555165 Opened 6 months ago Closed 5 months ago

Parse backdrop-filter CSS property

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: cbrewster, Assigned: cbrewster)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

Assignee: nobody → cbrewster
Blocks: 1178765

Probably worth waiting me to land bug 1552878, which will make this a one-liner basically?

Priority: -- → P3
Blocks: 1561060
Attachment #9073856 - Attachment description: Bug 1555165 - Parse backdrop-filter CSS property r?emilio,boris → Bug 1555165 - Part 1: Parse backdrop-filter CSS property r?emilio,boris

Triggered autoland.

Keywords: checkin-needed

Hmm, I think this might need a rebase - something must've changed on mozilla-central recently (or even more recently on autoland), perhaps.

The specific error is shown at https://lando.services.mozilla.com/D36062/ which says Details: abort: uncommitted changes. That's a slightly odd error, but I'm guessing it means the patch failed to import...?

Flags: needinfo?(cbrewster)

"part 0" was the problematic bit, so I just removed that from the stack (via edit-parent-revision on part 1) and tried lando again. I'm pretty sure Lando will be able to rebase the "part 1-part2" stack on top of current autoland, because that worked locally for me.

Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e4fecbe399e1
Part 1: Parse backdrop-filter CSS property r=emilio,boris
https://hg.mozilla.org/integration/autoland/rev/cba1f1b068da
Part 2: Update backdrop-filter WPT tests and expectations r=boris
Attachment #9073874 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Flags: needinfo?(cbrewster)
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/17701 for changes under testing/web-platform/tests
Upstream PR merged
You need to log in before you can comment on or make changes to this bug.