react-spectrum

> they are terrible OS citizens I used to feel this way. And then I discovered their Spectrum design and React libraries. I use them in production. And I am a huge fan. I don't think anything like this exists. Opensource or commercial. Don't get me wrong, there are plenty of UI libraries. But nothing has the breadth of coverage that Spectrum does, including design guidelines. https://spectrum.adobe.com/ https://github.com/adobe/react-spectrum And Spectrum 2 is expected later this year.

This code doesn't. It guarantees that within `useControlledState`[1], `defaultValue` is either NaN, an actual number, a number-like string, or something else that can be coerced into one[2]. If `defaultValue` is, for example, `true` or even an empty array, then the result of the expression `isNaN(defaultValue) ? NaN : defaultValue` will pass through `true` or the empty array. 1. <https://github.com/adobe/react-spectrum/blob/main/packages/%...> 2. whether one of those non-numbers is prevented from actually making an appearance at this point for other _reasons_ is a different question, but the fact remains that one making its way through is not something that would be stopped from proceeding further by the isNaN check here (Addendum to, I hope, clarify: I'll reiterate that it's the type annotations on the `useControlledState` call site p

This was an intentional choice. Repositioning when an outer element scrolls is pretty janky in some cases because scroll events don’t fire at 60fps. Also it’s not possible at all in other cases, like if the trigger goes completely out of view. We used to close the popover in this case but this caused usability problems. The new behavior of preventing scroll actually matches native platforms like macOS and helps with these issues. I get that it’s a little opinionated but it was thoroughly considered, not just done out of laziness. More details in this answer: https://github.com/adobe/react-spectrum/discussions/3802#dis...

It’s not perfect though. The only reason I’m not using preact is that my front-end library of choice, react-aria, does not work 100% with preact, though it sounds like it might now be close (unsure). https://react-spectrum.adobe.com/react-aria/index.html https://github.com/adobe/react-spectrum/issues/781

I've been using react-aria on a personal project, as well as building a UI library at work based on TailwindCSS+React Aria. I generally really like the combination. The maintainers are super responsive+helpful on Github and really know how to engage constructively with criticism. I really appreciate what they're doing. The combination of TailwindCSS+React Aria provides one with a pretty great template/scaffolding for building out a fully featured component library. The only downside that I've found is that their typescript support can be a little weird in my experience, but their approach is nonetheless well considered imo. edit: https://github.com/adobe/react-spectrum/pull/1761#issuecomme... is a decent summary of what I'm referring.

I thought the most important part of the article wasn't about the missing API. ( Many of them are draft status ) It was the buggy implementation of a feature that go unfix for years [0]. It say it is supported only to find out it really doesn't. Or those one-offs, I think [1] is a much better take on the problem. And as a Web page browser. I dont have much complain. But in terms of Web Apps.... there is where the fuss is all about. [0]https://github.com/adobe/react-spectrum/wiki/Tracker-for-Ext... [1] https://daverupert.com/2021/07/safari-one-offs/

Yep! ComboBox is also in progress/close. ;) https://github.com/adobe/react-spectrum/pull/421