Skip to content

Update notes-2021-03-11.md #558

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

Merged
ryzokuken merged 1 commit into from
Apr 18, 2021
Merged

Update notes-2021-03-11.md #558

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
4 changes: 3 additions & 1 deletion meetings/notes-2021-03-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,9 @@ SFC: I see two fundamental questions. (1), are time zone and calendar pickers us

MCM: If we focus on pickers, we should collaborate with Open UI, whose purpose of existence is to (partly to) work on pickers.

RCA: ___
RCA: I believe one of the main drivers to have this proposal are picker’s , but also the web performance in general. Most popular libraries like moment-timezone(8 Million weekly downloads), have an extra cost depending on how many locales you support, those must be optimized by bundlers, in case you want to reduce the typical 1mb that momentjs has with all extra data.

Projects like OpenUI can bring us several opportunities to improve pickers that need this kind of data, but actual UI’s implemented in browsers lack those features and aren’t perfect dealing with timezones or other “special” localization features.

FYT: So, going back to the original question, do we satisfy the three points for Stage 2?

Expand Down