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

Known issues #1

Closed
foolip opened this issue May 3, 2022 · 7 comments
Closed

Known issues #1

foolip opened this issue May 3, 2022 · 7 comments

Comments

@foolip
Copy link
Member

foolip commented May 3, 2022

What are some known issues with viewport units / viewport measurement?

web-platform-tests/interop#41 lists some.

w3c/csswg-drafts#6453 also came across my radar, but I'm not sure if it's an interop issue, I don't know current browser behavior.

@bramus
Copy link
Collaborator

bramus commented May 20, 2022

One thing that's on my radar is the inconsistency between Safari and Chrome when it comes to viewport units and the keyboard.

As I understand it from running some tests using https://urlbarsize.netlify.app/urlbarsize-allowresize.html (forked from https://bokand.github.io/demo/urlbarsize.html to also include a textfield you can focus):

  • Safari on iOS calculates 100vh against the layout viewport. When the keyboard gets shown/hidden, the calculated value for 100vh does not change. The keyboard does not really overlay the contents, but Safari does this thing where it shifts the layout viewport up
  • In Chrome on Android, 100vh is calculated against the visual viewport. When the keyboard gets shown/hidden, the calculated value for 100vh changes along with that.

Could be that (part of) this gets solved when the Virtual Keyboard API lands (allowing devs to set overlaysContent to true), but would be nice to see all browsers use the same default behavior there.

@foolip
Copy link
Member Author

foolip commented May 25, 2022

The thread in https://twitter.com/madebyfabian/status/1460376294332456968 is about virtual keyboard interaction, with @jensimmons and Maciej chimed in.

@bfgeek
Copy link

bfgeek commented May 26, 2022

There is also w3c/csswg-drafts#7194

@gsnedders
Copy link
Member

  • Relationship between initial containing block and layout viewport and visual viewport is unspecified,
  • height: -webkit-fill-available is widely used, but is still prefixed everywhere (v. stretch, got deferred to L4, and appears practically untested in WPT,
  • CSSOM attributes like innerHeight still refer to the old CSS 2 definition of viewport, so it's unspecified what they do with dynamic viewports,
  • Lack of WPT infrastructure to test dynamic viewport behaviour.

@bramus
Copy link
Collaborator

bramus commented May 31, 2022

Mentioning w3c/csswg-drafts#7194 as related

@foolip
Copy link
Member Author

foolip commented May 31, 2022

@bramus
Copy link
Collaborator

bramus commented Aug 10, 2022

Closing this issue as we will be discussing items listed here in separate issues.

@bramus bramus closed this as completed Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants