docs: correct and reformat the chart style property tables - #5985
Merged
Conversation
The tables listed eight properties no rule reads any more, omitted
eleven that exist, and gave --lumo-* variables as default values in a
release whose default theme is Aura. They were also the last tables
under articles/components/ still using the Default Value column that
every other styling page dropped for Supported by.
Switch to the standard format, which removes the stale defaults along
with the need to maintain any of them, and correct the membership. The
per-theme differences move into prose above the tables, where they don't
have to be repeated per row.
Keep the vaadin-chart {...} selector and say why it isn't html {...}:
Lumo declares most of these properties on the chart element, so a value
inherited from html never applies. Verified in the browser against Aura,
Lumo and no theme, along with every property listed and every one
removed.
Part of vaadin/web-components#12700.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
DiegoCardoso
force-pushed
the
docs/charts-style-property-tables
branch
from
September 9, 2026 15:03
ceacc31 to
e6e3f1b
Compare
Preview DeploymentThis PR has been deployed for preview. URL: https://docs-preview-pr-5985.fly.dev Changed pagesAdded content is highlighted in green; removed content is marked in red on each page.
Built from fdb0eeb |
web-padawan
approved these changes
Sep 10, 2026
DiegoCardoso
added
the
target/v25.2
web-padawan
pushed a commit
that referenced
this pull request
Sep 10, 2026
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
3 participants
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.
The tables on the Charts style properties page listed eight properties no rule reads any more, omitted eleven that exist, and gave
--lumo-*variables as default values in a release whose default theme is Aura. They were also the last tables underarticles/components/still using theDefault Valuecolumn that every other styling page dropped forSupported by.Switching to the standard format removes all eighteen stale defaults along with the need to maintain any of them, so this does both at once.
Removed — verified inert: the four
--vaadin-charts-contrast-*pct,tooltip-border-color,tooltip-background-opacity,color-positive,color-negative. Lumo still assigns the last four, but nothing reads them.Added:
surface,label,point-border,minor-grid-line,font-size,button-border-radius,button-disabled-label,candlestick-line,range-input-background,range-input-background-hover,tooltip-shadow.Other Chart Colorsis gone — removing the four deadcontrast-*pctproperties emptied it down tocontrast, which moves to Common Properties.Selector guidance kept, and now explained
The page says to use
vaadin-chart {...}, which contradicts thehtml {...}advice on every other styling page, so it looked like drift worth fixing. It isn't: Lumo declares most of these properties on the chart element, and a value inherited fromhtmlnever overrides a declared one. The page now says so.Verification
Driven in a browser against Aura, Lumo and no theme:
vaadin-chart {...}html {...}Every listed property was confirmed to change rendering — four chart configurations were needed, since
point-borderonly applies to pie/column/bar/funnel/pyramid/treemap, the button properties need a range selector, and the tooltip ones need a visible tooltip. Every removed property was confirmed to change nothing, with live properties as controls on the same chart. Two hover-state properties rest on source alone;:hovercan't be forced from script.The documented set now matches the stylesheet exactly.
Part of vaadin/web-components#12700.
🤖 Generated with Claude Code