Re: [csswg-drafts] [cssom-view-1] Further restrictions on resolved values for insets? (#9267)

The CSS Working Group just discussed `[cssom-view-1] Further restrictions on resolved values for insets?`, and agreed to the following:

* `RESOLVED: for sticky pos, getComputedStyle will return computed values for insets`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> iank_: i’ll outline how we got here … were investigating bugs when you acces trbl from gCS. these return used values<br>
&lt;bramus> … for pos:rel things are broken in x-compatible ways<br>
&lt;bramus> … but also if there is a new positioning mode ever: do we want to continue returning offsets from gCS?<br>
&lt;bramus> … added use counter for pos:sticky and returning offsets is very rare<br>
&lt;bramus> … want to check if we restricting when to return used insets<br>
&lt;bramus> … as for sticky, everyone has bugs about this<br>
&lt;emilio> q+<br>
&lt;bramus> … are ppl interested in this?<br>
&lt;astearns> ack emilio<br>
&lt;bramus> emilio: do you know how feasible to ??? relative?<br>
&lt;bramus> iank_: need to investigate<br>
&lt;astearns> s/???/also restrict/<br>
&lt;bramus> … usecounters are relatively high but i dont know how they are actually uses<br>
&lt;bramus> …  for sticky (with % or calc) it is 0.0001% of page loads (very low)<br>
&lt;bramus> … for relative usecounter is sitting at 20%-ish<br>
&lt;ydaniv> q+<br>
&lt;bramus> emilio: in general the more computed styles that gCS returns the better<br>
&lt;bramus> … this is pretty obvious for non-abs pos<br>
&lt;bramus> … so sounds good in general, but feels a bit weird to treat sticky/relative differently<br>
&lt;bramus> iank_: today, relative only returns good values in chromium if you are non-inline<br>
&lt;bramus> … all sorts of weirdness ???<br>
&lt;bramus> … we may end up in state where sticky and rel need to be treated differently<br>
&lt;astearns> ack ydaniv<br>
&lt;bramus> … but sticky should be web compatible<br>
&lt;bramus> ydaniv: I needed sth for sticky: to get the static offsets of an element that could be stuck. currently impossible. had to force to static pos and read the offsets and then put it back to sticky<br>
&lt;bramus> iank_: but you are not using gCS there?<br>
&lt;bramus> ydaniv: not for ???<br>
&lt;bramus> iank_: yes, just talking about gCS for trbl<br>
&lt;ydaniv> s/???/offsetTop offsetBottom etc./<br>
&lt;bramus> astearns: I agree with emilio about the more we can agree computed values is correct. risk is that if authors have a script to relies on ??? but that seems unlikely to me.<br>
&lt;bramus> iank_: only resolution I am comfortable with right now is about sticky<br>
&lt;astearns> s/???/relative behavior that they want to apply to sticky elements./<br>
&lt;bramus> … only change if your pos;sticky with a % top, gCS would no longer a return a pixel but the percentage<br>
&lt;bramus> astearns: PROPOSED RESOLUTION: for sticky pos, getComputedStyle will return computed values for insets<br>
&lt;bramus> … concerns or objections?<br>
&lt;bramus> RESOLVED: for sticky pos, getComputedStyle will return computed values for insets<br>
&lt;bramus> iank_: thanks!<br>
</details>


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


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

Received on Wednesday, 15 November 2023 17:54:10 UTC