TPE DOM/Date time input types: Difference between revisions

No edit summary
Line 63: Line 63:
|-
|-
! Issue !! Description !! Status !! Comments/Corresponding Action  
! Issue !! Description !! Status !! Comments/Corresponding Action  
|-
| Determine locale for the date/time || Could be 1. Browser UI locale  2. User preferred locale || WIP || Consult with Peter
|-
|-
| CLDR data access mechanism ETA assessment ||  || WIP || Checking with Zibi
| CLDR data access mechanism ETA assessment ||  || WIP || Checking with Zibi
|-
|-
| Working model with 3rd party QA and revisit QA plan in our master plan ||  || In Plan || To discuss with Vance
| Working model with 3rd party QA and revisit QA plan in our master plan ||  || In Plan || To meet with SV by the week of Sep12
|-
| Moving advanced functions of time picker to later phase || 1. Follow-up bugs creation 2. Schedule in the master plan  || WIP || Jessica and Scott are creating bugs
|-
|-
| Does the feature need to support non-E10s ? ||  || WIP ||  
| Moving advanced functions of time picker to later phase || 1. Follow-up bugs creation 2. Schedule in the master plan || WIP || front-end : 1301281 1301284 1301302
Platform: 1301295 1301304 1301306 1301308 1301310 1301312
Shall add/schedule these to section #5 of the master plan in the workshop
|-
|-
|}
|}
Line 94: Line 92:
|-
|-
| Project master schedule  || master plan sign off|| DONE ||  
| Project master schedule  || master plan sign off|| DONE ||  
|-
| Determine locale for the date/time || Options: 1. Browser UI locale  2. User preferred locale || DONE || decision = 2. user preferred locale
|-
| Does the feature need to support non-E10s ?  || single process mode  || DONE || Yes. Necessary.
|-
|-
|}
|}
Confirmed users
628

edits