Joss Mackison

No longer maintained. Use something like [react-remove-scroll](https://github.com/theKashey/react-remove-scroll) or [body-scroll-lock](https://github.com/willmcpo/body-scroll-lock) instead.

Adding a case for things like https://seek-oss.github.io/capsize/ Input: ```json5 text: { regular: { size: { $value: '14px', $type: 'dimension' }, lineheight: { $value: 1.4, $type: 'number' }, } } ```...

I'm not an a11y expert, but I have some thoughts: - accessible patterns should be the default, rather than making consumers opt-in e.g. `enableAccessibleClearIndicator` - using hard-coded english for labels...

Thank you for detailing your requirements and constraints, providing context helps a great deal. However, I'm still not comfortable introducing an unexpected tab stop. > there isn't a consensus on...

@gwyneplaine I actually wrote some stuff down just yesterday regarding [prop patterns](https://github.com/thinkmill-training/react-patterns/tree/master/patterns/props-api-design#interesting-and-alternative-patterns)

What about a "versions" (or similar) section that has latest + a link to all changes? * * * # Project name Some descriptive copy fruitcake caramels bear claw cookie...

@Noviny I think there's value in presenting the latest version, but badges are often overlooked because there's a wall of them without context; this mitigates that issue.

You could link wherever you like. The badge is a nice solution because nobody's updating the readme with each patch.

I wasn't aware of custom queries, thanks for the heads up! Looking at this with fresh eyes, I think there's a sensible way to write the expectation with existing APIs...

> Do you believe this use case is worth adding to the core library? No, I think my mental model was at odds with the library's design decisions. --- However,...