Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add link to WICG thread. #2

Merged
merged 1 commit into from
Jun 19, 2019
Merged

Add link to WICG thread. #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,10 @@ for the native components and controls that the platform delivers to be heavily
# Controls to standardize (initial thinking)
* `<dropdown>` (modern replacement for select)
* `<file>` (modern replacement for input type="file")
* `<toggle>` (proposal from Google is [here](https://github.com/tkent-google/std-switch)
* `<std-switch>` (proposal from Google is [here](https://github.com/tkent-google/std-switch))

# Moving this to a standards body
Once I get buy in (actively working on this now) from other browser vendors, web developers, frameworks, design systems I'll
move this repo to the location that makes the most sense. (I plan to open a WICG thread for this, this week).
move this repo to the location that makes the most sense.

WICG Discourse: https://discourse.wicg.io/t/standardize-form-controls-components/3646