Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions ed/csspatches/css-ui.json.patch
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
From 12a9288c72c5f2ac57192b67fea714978f45a140 Mon Sep 17 00:00:00 2001
From 9f7b7ad2d01bd8f06db43ef0b28dc3f71296f278 Mon Sep 17 00:00:00 2001
From: Francois Daoust <[email protected]>
Date: Tue, 30 Jan 2024 09:35:23 +0100
Subject: [PATCH] Add CSS patch to drop pointer-events dfn from CSS UI
Date: Mon, 6 Jan 2025 08:11:45 +0100
Subject: [PATCH] Drop pointer-events dfn from CSS UI

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

diff --git a/ed/css/css-ui.json b/ed/css/css-ui.json
index 0532a7609..4dc9009de 100644
index 684bac146..e8ed71344 100644
--- a/ed/css/css-ui.json
+++ b/ed/css/css-ui.json
@@ -562,38 +562,6 @@
@@ -594,38 +594,6 @@
"userSelect"
]
},
Expand All @@ -39,7 +39,7 @@ index 0532a7609..4dc9009de 100644
- },
- {
- "name": "none",
- "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?",
- "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?",
- "href": "https://drafts.csswg.org/css-ui-4/#valdef-pointer-events-none",
- "type": "value",
- "value": "none"
Expand All @@ -54,5 +54,5 @@ index 0532a7609..4dc9009de 100644
"name": "accent-color",
"href": "https://drafts.csswg.org/css-ui-4/#propdef-accent-color",
--
2.42.0.windows.2
2.37.1.windows.1

Loading