- From: Alex Rudenko via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Nov 2024 19:12:04 +0000
- To: public-css-archive@w3.org
> If by rendered, you mean after bikeshed is run, not yet. I can find a way to throw the generated html somewhere for you to see. Yes, usually https://github.com/w3c/spec-prod is used to publish a preview but looks like it is not set up in this repo. > No but I'm wondering if it's a good fit. setViewport command only allows to set the width/height and devicePixelRatio but do not seem to include any other viewport properties. If we decide to add a parameter in setViewport then where would all the explanations and diagrams go? I assume it works the same way (it is also Bikeshed-based), in a non-normative section, with files being put to a folder. Note that I am not saying it is required. > I don't understand your question. Setting [=[[DisplayFeaturesOverride]]=] is the very purpose of this. When the override is set then the segments property is recalculated using the array of display features from DisplayFeaturesOverride slot coming from the setdisplayfeatures command. Probably I made an assumption that is not correct. If this command is only meant to override the segments getter available to the page, the current steps look sufficient. Or does the command imply a way to emulate the viewport with segments visually? Is the command expected to also trigger relevant Screen Orientation, Window Resize or Posture change events mentioned in the spec or any other events? And to confirm the DOM attribute cannot be overriden from JavaScript for testing? -- GitHub Notification of comment by OrKoN Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11137#issuecomment-2455500823 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 November 2024 19:12:05 UTC