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

Range Editor: vh range values (and other non-absolute units) are shown as calculated pixel values #17

Open
bramus opened this issue Sep 9, 2023 · 2 comments
Labels
bug Something isn't working external Issue caused by an external dependency FAQ This question/bug is part of the FAQ wontfix This will not be worked on

Comments

@bramus
Copy link
Owner

bramus commented Sep 9, 2023

E.g. https://scroll-driven-animations.style/demos/cover-to-fixed-header/css/

When you inspect the#sticky-parallax-header element and edit the range, the animation-range-end shows up as a pixel value. This is not how it was declared in the CSS. The CSS reads animation-range: 0vh 90vh.

@bramus bramus added bug Something isn't working wontfix This will not be worked on FAQ This question/bug is part of the FAQ labels Sep 9, 2023
@bramus
Copy link
Owner Author

bramus commented Sep 9, 2023

Unfortunately this is how the values are represented to me when reading the rangeStart and rangeEnd from the Animation instance. Same with getComputedStyle: the specified values have been computed to px values.

I don’t see a way – without resorting to parsing the stylesheet and running my own cascade - how to get these specified values. Marking as wontfix This will not be worked on and adding it to the FAQ This question/bug is part of the FAQ .

@bramus bramus closed this as completed Sep 9, 2023
@bramus bramus reopened this Sep 13, 2023
@bramus
Copy link
Owner Author

bramus commented Sep 13, 2023

Reopening so that the issue can be found when searching (because search defaults to non-closed issues)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external Issue caused by an external dependency FAQ This question/bug is part of the FAQ wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant