Replies: 6 comments
-
|
We're using components in production on https://lightroom.adobe.com and from my point of view "we're ready!" from the perspective of components being of good quality and usable. On the process/support front though, I think there's probably a bit of work. Once we're |
Beta Was this translation helpful? Give feedback.
-
|
This issue also has a possibility of some breaking changes, particularly to the |
Beta Was this translation helpful? Give feedback.
-
|
Also important to think about here: https://github.com/adobe/spectrum-web-components/issues?q=is%3Aissue+is%3Aopen+label%3Aa11y I'll try and make some time this week to tag these with a form of |
Beta Was this translation helpful? Give feedback.
-
|
The recent Spectrum CSS releases finally get around to renaming packages as per the most current Spectrum specification (e.g. BarLoader => ProgressBar or Dropdown => Picker) and in theory represents a serious breaking change to our component offerings. This could be mitigated by offering both old and new API surface as extensions of each other, but it's hard for me to see whether that's helpful (eases migration) or hurtful (delays migration) in the overall healthy relationship between the library and its users. There is work in progress to catch up to some of those changes in this diff: https://github.com/adobe/spectrum-web-components/compare/westbrook/spectrum-css?expand=1 so people can see the delta there. |
Beta Was this translation helpful? Give feedback.
-
|
Trying to track issues that need to be cleared before a 1.0 here: https://github.com/adobe/spectrum-web-components/projects/1 It's possible that some could be dropped at "feature releases" post 1.0, so speak up where you think we shouldn't be blocked. If there are things missing (please create issues) or things not included that area already listed in the issues, feel free to let me know here to get this project listing closer to complete. |
Beta Was this translation helpful? Give feedback.
-
|
@joekukish makes the great point that pre-1.0 we should normalize non-t-shirt sized uses of the
|
Beta Was this translation helpful? Give feedback.
-
This is a discussion issue to figure out what we'd need to do to feel ready for a 1.0 release of the various packages. We had previously outlined a list of issues that would allow us to get there, what seems like a lifetime ago, and it still has one "Stretch Goal" issue that we've been slowly making advances on: https://github.com/adobe/spectrum-web-components/labels/1.0.0
Things that I can think of just now to take into account for a possible 1.0:
fix: ...but sometimes a feature is a big feature and while it doesn't "break" anything it needs a "feature" version, e.g. content direction...overlaywould then have a more strict update pattern in contexts similar to Safari breaks with overlays and WebGL canvas #848 and Dropdown does not take focus when opens w/ iOS + VO #764 that beg for possibly serious implementation changes, if not specifically API breaking changes 🤞I'm sure there's much more context that I missing, but I wanted to get this conversation into the space so we could find as many realities to keep in mind as we formalize the path from here to there together.
Beta Was this translation helpful? Give feedback.
All reactions