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

fix(panel): fix panel close routine if it was closed immediately #4127

Merged
merged 1 commit into from Feb 2, 2023

Conversation

peitschie
Copy link
Contributor

fixes #4108 (again)

In practice, the time until the transition start is variable depending on the browser, amongst other things. Android + Chrome is between 27 => 44ms with a fast phone, but can take longer under many circumstances.

This removes the hardcoded time and instead looks for the transition start.

Depends on the new transitionStart method added to Dom7 in nolimits4web/dom7#62

fixes framework7io#4108 (again)

In practice, the time until the transition start is variable depending on
the browser, amongst other things. Android + Chrome is between 27 => 44ms
with a fast phone, but can take longer under many circumstances.

This removes the hardcoded time and instead looks for the transition start.
@nolimits4web nolimits4web merged commit 74aa9d8 into framework7io:master Feb 2, 2023
@peitschie
Copy link
Contributor Author

Thanks for the quick review and merge @nolimits4web

Just wanted to note, the Dom7 library in Framework7 core will need to be bumped to the new 4.0.5 release to ensure the new method is available 😅

@peitschie peitschie deleted the panel-close-fix branch February 2, 2023 09:00
@nolimits4web
Copy link
Member

Yes, it should be there in F7 7.1.4

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

Successfully merging this pull request may close these issues.

Opening and closing panel quickly breaks any further tap/click events
2 participants