Rolf Smeds

Implementing this for the regular Combo Box as well would also help circumvent this issue: https://github.com/vaadin/flow-components/issues/3470

@fabst2w when the component is disabled, a tooltip would not work anyway as `pointer-events:none` is applied (this is the same for all components). Readonly should be used if you want...

Sorry, @urkl, the wrapping chips mode didn't make it to the current version, as we decided to prioritize the single-line mode which was requested by other users and is better...

Neither for or against refactoring min/max to be based on this, but I do think it's meaningful to provide the min/max API after this is in, as it's a simpler,...

Argh, well, yes, of course it does, now that I think about it. And thanks to the design of the picker, it's really easy to scroll _a lot very quickly_....

> Before optimizing the API though: Which are the primary 3 use cases this is meant for? Disabling weekends? Disabling days when the veterinary has no available timeslots? Those two...

The use case mentioned above, _"Disabling days when the veterinary has no available timeslots"_, is precisely that: any arbitrary dates.

Acceptance Criteria for TabSheet component: https://github.com/vaadin/platform/issues/3152

Ah, we should rephrase that a bit: The intention is _not_ - to force developers to put all styles in a single stylesheet – only to make it possible to...

### Breakdown of refactorizations and features needed to support `::part()` in all components #### Refactoring components' DOM structures to expose nested components for `::part()` styling - [x] [DatePicker: Move date-picker...