web-platform-tests / interop

web-platform-tests Interop project
https://wpt.fyi/interop
318 stars 27 forks source link

The Layout Viewport and Viewport-Relative Lengths #870

Open bramus opened 1 month ago

bramus commented 1 month ago

Description

This is a partial reprise from this issue from last year, but this time not as an investigation project - something that was already covered in 2022.

The focus of the proposal targets:

Right now there is no interop across browsers on mobile, nor in WebViews and IABs.

Specification

(see list above)

Additional Signals

ryantownsend commented 1 month ago

@bramus does this cover the Virtual Keyboard? Because that’s a minefield that definitely needs a cross-browser CSS-only solution.

bramus commented 1 month ago

The Virtual Keyboard API is not included in the scope of this proposal.

jgraham commented 1 month ago

Is this proposal already covered by web-platform-tests (assuming that they can be run on mobile)?

bramus commented 1 month ago

There are some basic tests using the units:

But these tests don’t actually test the changes that would occur on mobile. Some of the demos from https://github.com/web-platform-tests/interop-2022-viewport could form the basis for new tests.

gsnedders commented 1 month ago

Right now there is no interop across browsers on mobile, nor in WebViews and IABs.

I don't think anyone currently is trying to tackle automated testing in web views or other embedded browsers (like Android's Custom Tabs or iOS's SFSafariViewController), for what it's worth, which makes those problems harder.

Even in general, while I think existing browsers with dynamic viewport sizing all hide/show UI elements on scroll, how much you have to scroll probably depends between browsers (and quite possibly how you scroll — I wouldn't be particularly surprised if some browser required a user scroll (v. from JS, or loading a fragment) to hide UI elements). I suspect that testing this in an automated way cross browser may be somewhat difficult?

johannesodland commented 1 month ago

@bramus Firefox-ios closed their issue, so I opened a new one here: https://github.com/mozilla-mobile/firefox-ios/issues/22607