Re: [csswg-drafts] [css-view-transitions-2] CSSOM for CSSViewTransitionRule.navigation does not match implementation (#10654)

The CSS Working Group just discussed `[css-view-transitions-2] CSSOM for CSSViewTransitionRule.navigation does not match implementation`, and agreed to the following:

* `RESOLVED: navigation is a CSSOMString, it returns an empty string when navigation descriptor is missing or invalid`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> noamr: looked at similar rules such as counterstyle. conistent to make this a CSSOMString<br>
&lt;bramus> is also what chrome’s implementation does, but spec says its an enum<br>
&lt;bramus> proposal to make it a CSSOMString that returns an emptry string when missing or having an invalid descriptor<br>
&lt;bramus> emilio: is it usefule to differentiate between missing auto or none?<br>
&lt;bramus> noamr: yes, very important for forwardcompat<br>
&lt;bramus> … if one browser adds another type that others dont have yet, then we want to see that there’s a difference between none or invalid<br>
&lt;bramus> emilio: but then you get auto behavior?<br>
&lt;bramus> noamr: no, the ?? is not read for purpose of nav<br>
&lt;bramus> … its a vt role without navigation descriptor and no initial value<br>
&lt;astearns> s/??/unknown value/<br>
&lt;bramus> … similar to having invalid rule<br>
&lt;bramus> emilio: ok, so it is a meaningful distinction<br>
&lt;ntim> q+<br>
&lt;bramus> … can consider making rule invalid alltogether<br>
&lt;bramus> noamr: want to keep consistent with StyleRule<br>
&lt;bramus> emilio: yes, if missing is relevant info then its fine to expose a string<br>
&lt;astearns> ack ntim<br>
&lt;bramus> ntim: how is it different from navigation none?<br>
&lt;bramus> noamr: auto vs invalid and then auto vs none<br>
&lt;bramus> … none would supersede auto<br>
&lt;bramus> … it has a meaing to not do a nav<br>
&lt;bramus> … while invalid is a no-op<br>
&lt;bramus> ntim: so none cancels the nav from the prev doc?<br>
&lt;bramus> noamr: yes<br>
&lt;bramus> astearns: other qs?<br>
&lt;bramus> … current wpt tests this behavior of CSSOMString?<br>
&lt;bramus> noamr: yes<br>
&lt;bramus> astearns: so proposed resolution is to change to CSSOMString that returns empty value when there is no ?? rule<br>
&lt;noamr> proposed resolution: navigation is a CSSOMString, it returns an empty string when navigation descriptor is missing or invalid<br>
&lt;bramus> RESOLVED: navigation is a CSSOMString, it returns an empty string when navigation descriptor is missing or invalid<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10654#issuecomment-2302325491 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 21 August 2024 15:12:05 UTC