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
1.32.0 + 1.32.1 inconsistently changes custom component iframe heights #8285
Comments
## Describe your changes In 1.32.0, we introduced some changes to custom components that rendered an iframe of a certain height instead of a default of 0. This change ensures that when the `frameHeight` is `undefined`, it will use 0. ## GitHub Issue Link (if applicable) Closes #8285 ## Testing Plan - Added a test to make sure it's set (and the Skeleton appears and disappears) --- **Contribution License Agreement** By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.
Hey @naterush ! Thanks for getting to us. We have merged a fix to this, and it will be in the next release hopefully in the next day or so. Just want to let you know that the end state should mimic the same behavior as before. The only difference you might notice is the time period before your custom component is loaded, we will display a "skeleton". The skeleton will disappear and collapse down for the message passing. You can bypass this by sending down a Happy to answer any more questions, but I thank you for your patience in this! |
## Describe your changes In 1.32.0, we introduced some changes to custom components that rendered an iframe of a certain height instead of a default of 0. This change ensures that when the `frameHeight` is `undefined`, it will use 0. ## GitHub Issue Link (if applicable) Closes #8285 ## Testing Plan - Added a test to make sure it's set (and the Skeleton appears and disappears) --- **Contribution License Agreement** By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.
## Describe your changes In 1.32.0, we introduced some changes to custom components that rendered an iframe of a certain height instead of a default of 0. This change ensures that when the `frameHeight` is `undefined`, it will use 0. ## GitHub Issue Link (if applicable) Closes streamlit#8285 ## Testing Plan - Added a test to make sure it's set (and the Skeleton appears and disappears) --- **Contribution License Agreement** By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.
Checklist
Summary
After upgrading to Streamlit>1.32.0, our custom component sometimes default to an iframe height of 150 pixels and never update. This happens most often on Safari. Another custom component that exists for message passing and is otherwise empty also defaults to 150 pixels now, which visually breaks apps as well.
Reproducible Code Example
First,
pip install mitosheet streamlit==1.31.0
.Then, run the following app:
Then, upgrade to
pip install streamlit==1.32.0
, and run the app again.Steps To Reproduce
Just look at the app between these two versions of Streamlit, and you will immediately notice visual differences.
Expected Behavior
This is what you see:
Screenshot on
streamlit==1.31.0
Screenshot on
streamlit==1.32.0
:Normally:
Of if you're unlucky:
Current Behavior
The differences
There are two major differences between these screen shots:
Note that I have only been able to trigger the unlucky case on safari. It's pretty inconsistent, so it may appear on other browsers as well (I suspect it's just a performance related race condition), but I was not able to replicate it after a bit of testing.
My guess is that it's related to this PR: #8179. I'm no expert, but this made it into the 1.32.0 release, and it deals with default component height (including callbacks that update the iframe height).
Our issue is here: mito-ds/mito#1263
Is this a regression?
Debug info
Additional Information
N/A
The text was updated successfully, but these errors were encountered: