Skip to content

Commit 9649cc5

Browse files
committed
Re-generate patch for ed/css/css-ui.json
Drop pointer-events dfn from CSS UI
1 parent 5be7ae9 commit 9649cc5

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

ed/csspatches/css-ui.json.patch

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
From 12a9288c72c5f2ac57192b67fea714978f45a140 Mon Sep 17 00:00:00 2001
1+
From 9f7b7ad2d01bd8f06db43ef0b28dc3f71296f278 Mon Sep 17 00:00:00 2001
22
From: Francois Daoust <[email protected]>
3-
Date: Tue, 30 Jan 2024 09:35:23 +0100
4-
Subject: [PATCH] Add CSS patch to drop pointer-events dfn from CSS UI
3+
Date: Mon, 6 Jan 2025 08:11:45 +0100
4+
Subject: [PATCH] Drop pointer-events dfn from CSS UI
55

66
The definition of `pointer-events` is not yet as complete as that in the SVG
77
spec. Tracking issue at:
@@ -11,10 +11,10 @@ https://github.com/w3c/csswg-drafts/issues/4438
1111
1 file changed, 32 deletions(-)
1212

1313
diff --git a/ed/css/css-ui.json b/ed/css/css-ui.json
14-
index 0532a7609..4dc9009de 100644
14+
index 684bac146..e8ed71344 100644
1515
--- a/ed/css/css-ui.json
1616
+++ b/ed/css/css-ui.json
17-
@@ -562,38 +562,6 @@
17+
@@ -594,38 +594,6 @@
1818
"userSelect"
1919
]
2020
},
@@ -39,7 +39,7 @@ index 0532a7609..4dc9009de 100644
3939
- },
4040
- {
4141
- "name": "none",
42-
- "prose": "Hit-testing acts as if the boxes generated by the element (see [CSS-DISPLAY-3]) were not there, effectively causing the element behind the pointer-events: none element to become the target of hit-testing based events instead. The statement above needs to be be qualified; for some purposes, hit-testing continues to take the element into account. For instance, clicking and dragging to start a text selection will continue to work as usual. What is the precise set of things for which hit-testing is affected by pointer-events?",
42+
- "prose": "Hit-testing acts as if the boxes generated by the element (see [CSS-DISPLAY-3]) were not there, effectively causing the element behind the pointer-events: none element to become the target of hit-testing-based events instead. The statement above needs to be qualified; for some purposes, hit-testing continues to take the element into account. For instance, clicking and dragging to start a text selection will continue to work as usual. What is the precise set of things for which hit-testing is affected by pointer-events?",
4343
- "href": "https://drafts.csswg.org/css-ui-4/#valdef-pointer-events-none",
4444
- "type": "value",
4545
- "value": "none"
@@ -54,5 +54,5 @@ index 0532a7609..4dc9009de 100644
5454
"name": "accent-color",
5555
"href": "https://drafts.csswg.org/css-ui-4/#propdef-accent-color",
5656
--
57-
2.42.0.windows.2
57+
2.37.1.windows.1
5858

0 commit comments

Comments
 (0)