Closed Bug 769352 Opened 10 years ago Closed 9 years ago
DOM/content implementation for <input type=date>
Implement the content part of the <input type=date> as described in http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#date-state-%28type=date%29 I'm going to break this bug into separate smaller bugs and to use this one to reference them.
Isn't the hard part here the UI, not the DOM bits?
(In reply to Boris Zbarsky (:bz) from comment #1) > Isn't the hard part here the UI, not the DOM bits? Yes. The plan is to have the DOM bits done and use the native widgets on Android and do a UI on B2G. We will disable it on desktop as long as we don't have a UI there.
Raphael / Mounir: How close are we to landing the dependent patches? Many seem to have r+ and some are r?
(In reply to Mark Finkle (:mfinkle) from comment #3) > Raphael / Mounir: How close are we to landing the dependent patches? Many > seem to have r+ and some are r? We found some issues that need to be think of but as-is, the patches might be ready to land. However, I never did the last review because if I land those patches, I will have to dedicate some time to maintain the feature (fix any issue that might pop-up) and I do not have right now the bandwidth to get familiar with the code. I was hoping to do that this month but other stuff came :(
DOM implementation is now complete and lives behind a pref: "dom.experimental_forms". Given that the implementation comes with no UI, it is only available on Mobile.
You need to log in before you can comment on or make changes to this bug.