scrolling legend height not recalculated on resize
See original GitHub issueInitially reported in https://github.com/ropensci/plotly/issues/525, I was able to isolate to a non-R JavaScript only example in codepen. I had hoped v1.7.0
would solve this, but unfortunately I just updated, and the problem persists.
I am happy to attempt to tackle this if desired. I see on line where it checks for firstRender
to draw the legend. I’m wondering if we can handle by just removing this firstRender
check.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
On resize isn't working with my height calculation
So I am using a fixed sidebar which when it reaches a certain point swaps to absolute in order to stop it from...
Read more >height - CSS: Cascading Style Sheets - MDN Web Docs
The height CSS property specifies the height of an element. By default, the property defines the height of the content area.
Read more >Legend – amCharts 4 Documentation
If we want to limit the height of the legend, we can use its maxHeight property. If we do so, it would make...
Read more >Setting 100% height and resize on container resize for grid ...
I have been asking about the ability to resize a grid within a div tag at 100% height, 100% width, and Scroll Header...
Read more >Resizing an SVG When the Window is Resized in d3.js - Chartio
The browser doesn't inherently associate a width or height with an SVG unless ... scale well when compared to, say, an image, is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t. I’d would simply remove/add the handlers.
@timelyportfolio nice catch.
This block should be
my mistake.