10 minutes | Paragon CLI: install-theme | @Adam Stankiewicz | [inform/demo] We recently released a new Paragon CLI. It comes with a single command to start: paragon install-theme Allows consumers to install and use a custom @edx/brand aliased NPM package during local development without risking modifying/committing changes to the default installed @edx/brand-openedx package. Example: {
"scripts": {
"build:with-theme": "paragon install-theme && npm build",
"start:with-theme": "paragon install-theme && npm start",
}
}Next steps: Future CLI ideas: Our roadmap includes: Porting over existing CLI tools into the new Paragon CLI as additional commands. Tracking Segment events when these CLI commands are used by consumers. Automated migrations for consumers (i.e., dealing with breaking changes).
Notes: |
10 min | Floating labels & AutoSuggest | @Jeff Witt | It’s weird, weird, and more weird.
- suggestion overwrite floating label (recent observation)
- Google moving floating label out of the way when there is a suggestion from the browser (how?)
- Chrome AutoSuggest positioning is different for different people
- Chrome AutoSuggest capture with Share Screen is different for different people
Requests:
- Use AutoComplete attribute with granular semantic values
- Use AutoComplete whenever possible
- Store form results (particularly user data) and auto-populate fields when possible (WCAG 2.2 requirement)
- Notes: Screen readers don’t always read out form input placeholders. Shouldn’t rely on placeholders for labeling. Floating label acts as a both a placeholder and a label. Why aren’t floating labels great? UX/a11y has stopped recommending the use of floating labels. The browser native autosuggest hides form control feedback. Seems to be different browser behavior related to autocomplete overlays, etc. for different users? Chrome seems to move the autosuggest in some situations, but not all. [question] Is there a way to style the Chrome default autocompletes/autosuggests?
|