Fix rangeslider "fixed" rangemode using placeholder range of autoranged counter axis - #7967
Open
Guhapriya01 wants to merge 4 commits into
Open
Conversation
Guhapriya01
marked this pull request as ready for review
August 16, 2026 09:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes plotly/plotly.py#5614
Problem
With
rangeslider.yaxis.rangemode: "fixed"and no explicit range, the slider renders two grey bands on initial load; toggling rangemode away and back clears them. The bands are the opp-axis masks, which shade the slider outside the fixed y-range — visible only when that range disagrees with the data.Cause
rangeslider/defaults.jsdefaults the fixed range offyAxOut.range. When the counter axis autoranges, that is still theDFLTRANGEY[-1, 4]placeholder at supplyDefaults time. Unlikerangemode: 'auto', nothing revisits it afterwards.Toggling works only because it forces a second supplyDefaults, by which point the axis holds its computed range.
Fix
Flag a
fixedrange defaulted off a not-yet-autoranged axis, and letdoAutoRangefill it in via the path'auto'already uses. The flag is deleted once consumed, sofixedresolves once and then stays put, and the internal key is not copied out tolayout.No schema change;
auto,match, explicit ranges and non-autoranged axes are unaffected.