fix(useDisplay): More intuitive use of mobile-breakpoint
#20311
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.
resolves #19883
Description
The
mobile-breakpoint
prop requires:mobile='null'
to work, otherwise it is ignored. It is not intuitive and developers ask about it on Discord or assume it does not work, because components' API docs don't mention this requirement.I wish we could let user work with
mobile-breakpoint
and don't bother about the other prop. The logic could then be:mobile === true
, then force mobile viewmobile-breakpoint
is set, accept it's value to resolve mobile statemobile='null'
makes the component rely on default mobile breakpointMarkup: