@primer/react-brand@0.40.1
See documentation for this release
Patch Changes
-
#754
d061705c
Thanks @joshfarrant! - TheRiverStoryScroll
component now enforces that its children must beRiver
components through type checking, instead of relying on a run-time check. -
#739
24bd6338
Thanks @joshfarrant! - Fixed a bug in theSubNav
component where the submenu toggle was rendered as an empty button on mobile viewports. -
#736
73cf706e
Thanks @lukasoppermann! - Replaced the--brand-VideoPlayer-tooltip-padding
design token in theVideoPlayer
component with two new tokens that separately account for padding along each axis:--brand-VideoPlayer-tooltip-padding-inline
and--brand-VideoPlayer-tooltip-padding-block
.Note: This update does not introduce any visual changes. Please update any manual references to
--brand-VideoPlayer-tooltip-padding
to use the new tokens.- --brand-VideoPlayer-tooltip-padding + --brand-VideoPlayer-tooltip-padding-inline + --brand-VideoPlayer-tooltip-padding-block
-
#722
99328ce0
Thanks @danielguillan! - Added support for<b>
elements toBento
,RiverBreakout
,SectionIntro
,Timeline
, andTestimonial
components, as<em>
is semantically interpreted by screen readers for emphasis, while<b>
allows duo-tone text to function purely as a visual decoration.Usage example:
<SectionIntro> <SectionIntro.Heading> <b>Expressive headline</b> about an exclusive set of features. </SectionIntro.Heading> </SectionIntro>
Important
The updated components still support the use of<em>
elements for backward compatibility, but moving forward, the only recommended element for emphasized text is<b>
. -
#733
2dcb9bad
Thanks @danielguillan! - Fixes Label component multiline reflow -
#746
4af8db14
Thanks @joshfarrant! - Fixed a bug whereCard
components rendered within a dark colour mode would not take the full width of their container.