- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Oct 2023 17:31:36 +0000
- To: public-css-archive@w3.org
One thought is that the naming likely depends in some ways on how you expect to extend this in the future. One concern about many of the proposals here is that it feels like they have a *lot* of future extension points (argument to at rule, adding new descriptors, adding new values to existing descriptors) and it's not clear to me how the possible uses of those extension points differ. The extension types that I see mentioned in #8048 are: * extending to specific URL patterns, possibly cross-origin, in addition to just `same-origin` * distinguishing based on navigation types or back/forward * in item 8 above there also seems to be another suggestion for a future extensibility point, but I don't understand what it is. It might be helpful for group discussion to have a summary of the possible future extension areas and where you'd expect each one to fit in. (In particular, when I look at the above syntax options, I wonder whether there might be too many possible extension points, particularly when I see three places where there could later be multiple values but right now there's only one.) (I'm also a little confused by the term navigation-triggered, and curious when a navigation-triggered view transition is different from a cross-document view transition. Is one a subset of the other?) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9383#issuecomment-1773129736 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 October 2023 17:31:38 UTC