Open Bug 877294 Opened 11 years ago Updated 2 months ago

[Meta] Implement border box mask (mask-border-*) support

Categories

(Core :: Layout, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: jaws, Unassigned)

References

(Blocks 5 open bugs, )

Details

(4 keywords, Whiteboard: p=0)

Assigning as per https://groups.google.com/d/msg/mozilla.dev.platform/jB6I6EvcbH0/wq0TutTan2oJ
Assignee: nobody → ncameron
Status: NEW → ASSIGNED
See https://groups.google.com/d/msg/mozilla.dev.platform/-23mG3x2vdk/ReOWo9_sIAkJ for the original discussion that brought about this bug.
Whiteboard: [Australis:M?]
Depends on: 700926
Depends on: 686281
Whiteboard: [Australis:M?] → [Australis:M?][Australis:P4]
Still want, but not part of Australis project.
No longer blocks: australis-tabs
Whiteboard: [Australis:M?][Australis:P4]
Whiteboard: p=0
No longer blocks: fxdesktopbacklog
Flags: firefox-backlog+
Any chance of having this in the next versions?
No longer blocks: 658467
Summary: Implement mask-box-image support → Implement border box mask (mask-border-*) support
Blocks: 1244492
Unassigning due to lack of activity.
Assignee: ncameron → nobody
Status: ASSIGNED → NEW
Priority: -- → P3
Component: SVG → Layout
Summary: Implement border box mask (mask-border-*) support → [Meta] Implement border box mask (mask-border-*) support
Severity: normal → S3
Type: defect → enhancement

This test is exercising these properties & happens to be part of the interop-2023-cssmasking test set:
https://wpt.fyi/results/css/css-masking/inheritance.sub.html

I suspect there are only parsing and serialization tests for mask-border-* in interop-2023-masking WPT list. We could support them in style first (because they could be added quickly), and leave the layout/painting support later.

(In reply to Boris Chiou [:boris] from comment #7)

I suspect there are only parsing and serialization tests for mask-border-* in interop-2023-masking WPT list. We could support them in style first (because they could be added quickly), and leave the layout/painting support later.

Yup, it makes sense to start with style-system bits first. But note that it won't make a difference for interop2023 scoring until we're ready to enable the properties by default on Nightly, and presumably that would be when we've got some useful portion of the layout/painting support enabled.

(When we're partway through implementing something and we have opt-in pref flips in the testing/web-platform/meta/.../*.ini files, those prefs still aren't activated for upstream wpt.fyi test-runs. wpt.fyi runs essentially "stock" versions of Nightly/release, with only a few prefs toggled for test-harness-stability type purposes.)

Blocks: 1837635
You need to log in before you can comment on or make changes to this bug.