Re: [csswg-drafts] [css-viewport-1] Add automation support for viewport segments (#11137)

> 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.
 
Yes, I'm not entirely sure why. I'm not really a regular contributor to the CSS WG. I just happen to work on adding the viewport segments functionality.

> 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 meant more the fact that the BIDI spec doesn't really cover the concepts but just defines the commands. For me it felt natural to have the Automation story sit next to the property it covers.

> If this command is only meant to override the segments getter available to the page, the current steps look sufficient. 

This is correct. Please note that the entire viewport segments concept also defines [MQs](https://www.w3.org/TR/mediaqueries-5/#mf-vertical-viewport-segments) and [env variables](https://drafts.csswg.org/css-env-1/#viewport-segments) which will also be invalidated and recalculated. After this patch lands, I was planning to reference this addition on the MQ spec and CSS variable spec to cover the [DisplayFeaturesOverride] case.

> 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? 

Screen orientation, Window Resize and posture change are not expected to change when the internal slot is set.

> And to confirm the DOM attribute cannot be overriden from JavaScript for testing?

The `segments` property is a read only frozen array so no (unless I'm mistaken). Besides the automation aspect for authors to try their websites on different foldable devices the intention of this patch is also for testing purposes for user agents. If we can override the display features coming from the Windows and Android native APIs we can also verify the calculation of the `segments` property, the CSS MQs and the CSS Env variables through various configurations (more than one fold for example), 





-- 
GitHub Notification of comment by darktears
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11137#issuecomment-2455556478 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:42:57 UTC