coreui / coreui-pro / 33874695189

95%

main: 94%

push

github

feat(RangeSlider): tooltipClass for the value tooltip, tooltip keeps the plain look (#1136)

* feat(RangeSlider): customClass for the value bubble, bubble keeps the plain tooltip look

Since #1133 the bubble read the slider's theme slots through inheritance,
so a .theme-<color> slider painted its bubble too and nothing could
theme the bubble on its own. The bubble now resets the --cui-theme-*
slots (new theme-reset() mixin, shared with the .theme-reset helper) in
the components layer, so it stays the plain tooltip inside a themed
slider, while a class from the new customClass option — the Tooltip's
option name, data-coreui-custom-class — lands on the bubble alone and
wins from the helpers layer. Measured in Chromium: bubble in a
.theme-danger slider keeps the default surface, customClass=theme-secondary
paints it secondary, theme-inverse on top of a danger slider paints it
inverse. Docs: options row, Theme variants example; unit test.

* docs(RangeSlider): describe customClass as the tooltip's option

The Theme variants paragraph and the option row talked about a 'value
bubble' and used theme-inverse, which renders the same dark surface as
the default tooltip. They now say tooltip throughout, point at the
Tooltip plugin's customClass, and the second example matches a danger
tooltip to a danger slider.

* refactor(RangeSlider): rename the tooltip class option to tooltipClass

data-coreui-tooltip-class says which element the class lands on; the
Tooltip plugin's customClass name did not, on a component that has
options of its own for the tooltip (tooltips, tooltipsFormat).

4834 of 5434 branches covered (88.96%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

9269 of 9693 relevant lines covered (95.63%)

400.02 hits per line