You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the design spec, popovers opened from the block toolbar should have the same dark border (isAlternate) style by default. Currently, consumers need to set that prop on their popovers manually.
What is your proposed solution?
See if we can do this automatically, likely by using the context system.
I found a little more context in #45137, where the "isAlternate" is refactored/deprecated in favor of a variant.
But it boils down to this, you can have two styles of popovers. This one:
Notice how it opens from the block toolbar and has the same black borders as the block toolbar.
This one:
Notice how it doesn't open from the block toolbar, and has the light gray borders, plus a drop shadow.
The thing is, a developer should not have to choose a variant if we can automate this for them. The gray with box shadow can be default, but if something opens from the block toolbar, it should always be the dark version. That way we avoid this issue where someone forgot the variant:
The text was updated successfully, but these errors were encountered:
What problem does this address?
According to the design spec, popovers opened from the block toolbar should have the same dark border (
isAlternate
) style by default. Currently, consumers need to set that prop on their popovers manually.What is your proposed solution?
See if we can do this automatically, likely by using the context system.
More context from @jasmussen (#49838 (comment))
I found a little more context in #45137, where the "isAlternate" is refactored/deprecated in favor of a variant.
But it boils down to this, you can have two styles of popovers. This one:
Notice how it opens from the block toolbar and has the same black borders as the block toolbar.
This one:
Notice how it doesn't open from the block toolbar, and has the light gray borders, plus a drop shadow.
The thing is, a developer should not have to choose a variant if we can automate this for them. The gray with box shadow can be default, but if something opens from the block toolbar, it should always be the dark version. That way we avoid this issue where someone forgot the variant:
The text was updated successfully, but these errors were encountered: