Fix Select widget border not rendering due to BLANK name collision#6359
Closed
charles-001 wants to merge 1 commit into
Closed
Fix Select widget border not rendering due to BLANK name collision#6359charles-001 wants to merge 1 commit into
charles-001 wants to merge 1 commit into
Conversation
`Widget.BLANK` (added in 7.1.0, checked in `render_line`/`render_lines` since 7.2.0) collides with `Select.BLANK`, which is a `NoSelection` sentinel object. Because `NoSelection` is truthy, the `if self.BLANK:` check inadvertently matches, causing `Select` to skip normal rendering and return blank strips — losing its border. Use `is True` instead of truthiness to ensure only the boolean `True` triggers blank rendering. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
Since |
Member
|
Yeah, this doesn't seem the right solution. The right solutions is generally the one you don't have to justify to those that come after you. Having My fault entirely of course. I wonder why I didn't notice that. I don't think there is any other choice but to rename This would require a major version bump, which is unfortunate. |
Author
|
Yeah, I think that makes the most sense Will. |
Merged
Member
|
Thanks. Gone with #6374 |
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.
Summary
Widget.BLANK(aClassVar[bool]defaulting toFalse) was added in v7.1.0 to allow widgets to opt into blank renderingSelect.BLANKis a pre-existingNoSelectionsentinel object used to represent "no value selected"render_lineandrender_lineswere optimized to checkif self.BLANK:and skip normal rendering — butNoSelection()is truthy, soSelectinadvertently enters the blank rendering path, causing its border (and all visual chrome) to disappearif self.BLANK is True:to match only the booleanTrue, not arbitrary truthy objectsReproduction
Expected: Select has a heavy border
Actual (7.2.0+): Select renders with no border
Test plan
Widget.BLANK = Truestill produces blank rendering for widgets that use it