- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Tue, 19 Aug 2025 14:52:49 +0000
- To: public-css-archive@w3.org
> OK, this may be an option if we really want to split view-based triggering and other events. I'm not sure how much of control we want to allow there, because this already expands to 4(!) ranges - something that the events I suggested try to avoid. I also worry we may get some pushback, design-wise, about adding another specific property just for `view-trigger` and have all the rest of the events as values for `event-trigger`? To support this generality though we would end potentially adding all of these to the functional syntax that you had proposed - which is IMO more complicated than having a dedicated property space for it. If authors don't need to specify some of these most of the time we could leave them out for now and give them reasonable default values. E.g. maybe you can specify the primary axis ranges and we use cover in the off axis, or maybe we leave off the ability to specify aribtrary percentages on the ranges. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3201090854 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 August 2025 14:52:50 UTC