Skip to content

[css-ui-4] add the window-drag text#13801

Open
kyerebo wants to merge 7 commits intow3c:mainfrom
kyerebo:window-drag
Open

[css-ui-4] add the window-drag text#13801
kyerebo wants to merge 7 commits intow3c:mainfrom
kyerebo:window-drag

Conversation

@kyerebo
Copy link
Copy Markdown

@kyerebo kyerebo commented Apr 13, 2026

This change builds off of @diekus' PR to add the window-drag (formerly app-region) CSS property to the css-ui-4 spec. It makes requested edits from the previous PR, as well as adds a note mentioning app-region as an alias as a result of the new resolution at #13102.

This comes out of resolutions #13102 and
#13101 taken on 21/01/26.

diekus and others added 5 commits December 8, 2025 17:16
- adds `window-drag` to css-ui-4
- changes the computed value
- updates line width styling
Updates the spec text with the naming resolution by the CSSWG.

w3c#13102
@kyerebo
Copy link
Copy Markdown
Author

kyerebo commented Apr 13, 2026

Hi @emilio! I noticed you were reviewing Diego's original PR- I've applied the edits you had asked for there. Do you mind taking a look at this one as well?

Copy link
Copy Markdown
Collaborator

@emilio emilio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this property have an effect on event dispatch? I'm assuming that elements with window-drag: move will not get "web" drag events.

The spec should say what the expectation is for something like <div draggable=true style="window-drag:move">.

Looks good to me with these things documented and the questions below asked.

<dl dfn-for=window-drag dfn-type=value>
<dt><dfn>auto</dfn>
<dd>
Represents a UA-chosen default behavior, generally ''move/none''.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any time where none will not be the auto behavior? If so it should be called out. If not... Maybe the initial value should be just none?

Copy link
Copy Markdown
Author

@kyerebo kyerebo Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually don't think it makes sense for the auto behavior to ever not be none. I went ahead and removed auto in lieu of this and made none the initial value. (Please let me know if you think we should keep the auto value).

@kyerebo
Copy link
Copy Markdown
Author

kyerebo commented Apr 14, 2026

I've added a new text blurb that clarifies event dispatch behavior, as well as clarifying draggable behavior. Please let me know if the changes look good to you!

Copy link
Copy Markdown
Collaborator

@emilio emilio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me, but an editor of this spec should also review it :)

@kyerebo
Copy link
Copy Markdown
Author

kyerebo commented Apr 14, 2026

@tabatkins @frivoal Hi Editors! Could I ask one of you to take a look at this spec text for window-drag? Happy to make any changes, thank you for your time.

@kyerebo
Copy link
Copy Markdown
Author

kyerebo commented Apr 14, 2026

@fantasai Noticed you put the following in the older PR:

This probably needs a bit more clarification on what part of the element can be used as a drag target (by tying it to some other definitions, I'm not sure which ones).

Do you think specifying something like-

Specifies that the element's border box can be used as a drag area.

-would be clear enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants