TPE DOM/Date time input types

Introduction

This project is to enable the feature on Desktop that HTML input fields should contain a date or time or allow users to select a week in a year.

The project aims to provide basic input/pickers (date, month, time, date time, and week) for web authors and at the same time to meet HTML standard criteria including "Step", and "Max/Min".

Other than the functions listed above, the project shall also take care of localization (incl. the different format per locale) and accessibility (Input = Cursor Only, Cursor+Keyboard, or Keyboard only).

Last but not least, as per the current scope, only Gregorian calendar is considered.

References

• Project spec organized by Jessica. This document abstracted the essential user stories (as a web author viewpoint) from HTML living standard.
• UX spec Comprehensive living UX spec also available in Bug 1069609 .
• Visual spec UX spec might not be 100% correct regarding visual elements, so please refer to the visual spec which is also attached in Bug 1069609 .
• HTML input types
• Discussion thread
• QA Plan
• Jessica's Lightning talk in the Hawaii All Hands, Dec 2016
• Date/Time inputs post on Firefox Nightly blog

Note

Features landed on master will be pref-off, if the l10n integration is not done yet for that specific picker. Once it gets l10n part done, we will pref-on it on nightly /developer-edition.

Main Members

Product manager: Joe Cheng

Engineering program manager: Wesley Huang

Engineers: Jessica Jong (platform: DOM/layout part), Scott Wu (front-end: xul element/html content)

UX designer: Morpheus Chen, Tina Hsieh

Visual designer: Helen Huang

Localization: Zbigniew Braniecki (Gandalf)

Softvision QA:

Project Manager: Rares Bologa

QA members: Brindusa Tot, Simona Badau, Roxana Leitan

Roadmap

• Public Trello board
• Aligned living schedule available in google sheet (permission required as it's more for internal tracking)
• High-level overview of date time input status on Firefox Desktop

Project Dashboard

Project status on Meeting minutes

Bug Priority Tagging

• P1 - Fix in the current release or iteration
  • Major issues those in which a large number of users will be impacted, or a smaller number of users will be significantly impacted
  • Major identifiable regressions
  • Non-localizable strings
  • Top Crashes
  • sec-high, sec-critical security bugs
  • Data loss
• P2 - Fix in the next release or iteration
  • Enhancements/features we surely want in the next release
  • Non-critical string changes (due to l10n)
• P3 - Backlog
  • Polish and other minor issues
  • Other new features
• P4 - None. We're not using this
• P5 - Will not fix, but will accept a patch

Meta Bugs

• Project meta

1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);

• Meta bug for defects tracking

1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);

Ship Bugs

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Open Issues

Issues DONE