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

UI: Fix layout height #24370

Merged
merged 4 commits into from
Oct 9, 2023
Merged

UI: Fix layout height #24370

merged 4 commits into from
Oct 9, 2023

Conversation

cdedreuille
Copy link
Contributor

Closes #24261

What I did

To support older browsers we can't use 100dvh to set the height of the layout to be always visible on mobile. Instead, the most reliable way is to set the height using javascript. A common pattern is to set a css variable for --vh that you can then use elsewhere if needed it on your app.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

@cdedreuille cdedreuille changed the base branch from next to release-8-0 October 4, 2023 13:14
@cdedreuille cdedreuille self-assigned this Oct 4, 2023
@cdedreuille cdedreuille added maintenance User-facing maintenance tasks ci:normal labels Oct 4, 2023
return {
width: '100%',
height: '100svh', // We are using svh to use the minimum space on mobile
height: 'var(--vh, 100vh)',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Emotion supports array values for fallbacks:
https://emotion.sh/docs/object-styles#fallbacks

Suggested change
height: 'var(--vh, 100vh)',
height: ['100dvh', '100vh],

IIUC, the bug that requires 100dvh only happens on iOS and that supports the CSS feature?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is more about supporting old browser versions, and we haven't yet decided which versions to support in SB 8.0. https://caniuse.com/viewport-unit-variants

The fallback syntax looks interesting, I can't find any info on how this works? Is it a browser feature, or does Emotion do something clever with a list of CSS features per user agent?

based on the docs you linked, I think the syntax is the other way around in your suggestion.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh that's interesting. I didn't know Emotion had fallbacks. I'll try it out now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having the same property twice on a single class is a CSS feature.
CSS is fault-tolerant.

Emotion allows you to use this feature with the array syntax.

True, the exact implementation might have to be reversed from the code suggestion I added.

@cdedreuille
Copy link
Contributor Author

@JReinhold @ndelangen I've implemented the change and removed the JS code 😊 It does work as intended.

CleanShot 2023-10-06 at 16 42 38@2x

@ndelangen ndelangen merged commit 37ada8b into release-8-0 Oct 9, 2023
14 checks passed
@ndelangen ndelangen deleted the fix-layout-height branch October 9, 2023 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:normal maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove height: 100svh in favour of a solution that work for Chrome 100 and above
3 participants