W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] [resize-observer-1] physical, rather than logical, dimensions – for images (#4005)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Mar 2020 16:49:16 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-600742769-1584550155-sysbot+gh@w3.org>
The CSS Working Group just discussed `[resize-observer-1] physical, rather than logical, dimensions – for images`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [resize-observer-1] physical, rather than logical, dimensions – for images<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4005<br>
&lt;dael> fantasai: Someone posted a strong use case to return phsyical dimensions. Prop is add phsyical to what resize-observer can return. Use case makes sense and we should do this<br>
&lt;dael> iank_: Use case is? How will they use this?<br>
&lt;dael> astearns: By my reading the block and inline size in a flow that is orthogonal to an image's useful orientation doesn't really help<br>
&lt;dael> astearns: Though in reading htis I'm a little confused as to if you know that's the case why you can't just flip the sizes you get. Are there cases where you don't know if block directio is useful?<br>
&lt;dael> myles: Spec that canvas rotated in veritical?<br>
&lt;dael> fantasai: NOt rotated. If he wants width of image he has to switch based on writing mode so he needs to switch to decide if he wants inline or block<br>
&lt;dael> iank_: No objections to adding but it's not explicitly a use case since it doesn't say how he's going to use information<br>
&lt;dael> fantasai: You can ask him for more details<br>
&lt;dael> myles: In agreeing with iank_ another solution solved by this would be not return logical and only physical. Need some information to know that both is better than just phsyical<br>
&lt;dael> fantasai: We're already returning block size. It's just that on image you then need writing mode<br>
&lt;fantasai> s/block/inline &amp; block/<br>
&lt;dael> astearns: I don't think we can remove inline and block size and return something else<br>
&lt;dael> myles: Not clear to me canavas is used enough that it's a problem to change behavior<br>
&lt;dael> fantasai: Shouldn't return different APIs depending on the element.<br>
&lt;dael> astearns: Hearing a little concern about adding something that may or may not be useful given data. Do we need to go back with code examples or request more information?<br>
&lt;dael> dholbert: Also asking if they want to observe it or have it returned. From sketch is seems logical size isn't changing but physical is<br>
&lt;dael> AmeliaBR: Wouldn't they change at same or observing from change of writing mode?<br>
&lt;dael> dholbert: When writing mode changes they want notification? Not sure<br>
&lt;dael> AmeliaBR: Trickier. Observing size has changed and adding 2 entries to dictionary is straight forward. Changing what triggers observation is more complex<br>
&lt;dael> astearns: We have some questions and poster offered a more fleshed out use case so let's ask for more details on these questions.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4005#issuecomment-600742769 using your GitHub account
Received on Wednesday, 18 March 2020 16:49:18 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC