Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Layout Viewport and Viewport-Relative Lengths #870

Open
bramus opened this issue Oct 9, 2024 · 6 comments
Open

The Layout Viewport and Viewport-Relative Lengths #870

bramus opened this issue Oct 9, 2024 · 6 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@bramus
Copy link

bramus commented Oct 9, 2024

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
Copy link

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

@bramus
Copy link
Author

bramus commented Oct 10, 2024

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

@jgraham
Copy link
Contributor

jgraham commented Oct 16, 2024

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

@gsnedders
Copy link
Member

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
Copy link

@bramus Firefox-ios closed their issue, so I opened a new one here: mozilla-mobile/firefox-ios#22607

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus-area-proposal Focus Area Proposal
Projects
Status: No status
Development

No branches or pull requests

5 participants