Skip to content

Base styles fixes and enhancements #10417

@jouni

Description

@jouni

Blockers [total 16.25 days]

Things that should be fixed before v25.0:

Potential blockers

Things I would like to change, but are not mandatory, and should be done before v25.0:

  • Nicer spinner/loader styles, using radial-gradient mask-image instead of border colors
  • Override vaadin-text-color and vaadin-border-color (including secondary variants) in Lumo
  • Consider breaking “padding-container” apart to padding-inline and padding-block values
  • fix forced color mode (test on Win11)
    • focus outline color is not the same in all components
    • button colors
    • text input border colors
    • primary button
    • menu bar submenu indicators
    • checked items checkmark color
    • hovered/focused item in item overlays
    • ... and probably other issues
  • rich-text-editor:
    • the text color “black” is actually “clear color”, change the “icon”. Similarly for bg color, where "white" actually means clear/transparent.
    • add “white-content-area” variant
  • charts: adding [theme] attribute changes font sizes in base styles
  • input field buttons: increase click target area (only on touch devices)
    • same for checkbox/radio

Major enhancements

Things that are not blocking, but would be great to have before v25.0:

  • Animation support for overlay elements (CSS keyframes are problematic with shadow parts, so we should offer something built-in)
  • details/accordion: allow content to scroll with explicit height/max-height
  • grid:
    • internal padding, easier indented rows? Or rather, add a custom property that makes it easy to add bigger padding to the first and last cells in each row.
    • row border-radius, make it easy with a custom prop (set on first and last column cell)
  • input fields: add [slot=input] { text-align: inherit; }
    • text-align on host of input fields should inherit down to the field
  • Use Lucide icons instead of Hero icons
  • property for progress-bar-height
  • MDL iOS safe area insets
    • Probably needs a variant for MDL to opt-in to the insets, when you know it’s covering the entire viewport
      • Or apply only when containment=viewport?

Bug fixes

Other

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions