Closed Bug 1009619 Opened 10 years ago Closed 10 years ago

Extra controls for HTML5 input types

Categories

(Core :: Layout: Form Controls, defect)

29 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 558594

People

(Reporter: marvin.froehlich, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 2014042500

Steps to reproduce:

The new HTML5 input types like "search" or "date" are not fully implemented. For example a "search" field should display an x like control in the right end, if the content is not empty to clear the field.

This lag seems to be worse on Linux.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Resolution: --- → DUPLICATE
No, this bug is not a duplicate of the linked bug. The linked bug only refers to the search field. This bug reports, that (almost) ALL input fields need proper implementation.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
(In reply to Marvin Fröhlich from comment #2)
> No, this bug is not a duplicate of the linked bug. The linked bug only
> refers to the search field. This bug reports, that (almost) ALL input fields
> need proper implementation.

Please be more specific in your bug report: "ALL input fields need proper implementation." is an useless description, and cannot be linked to any specific task.

The "search field should display an x like control in the right end, if the content is not empty to clear the field." is specific enough, and linked to bug 558594 indeed.

<input type="date"> not being implemented is another bug.

Given that those bugs already exist, I don't get what is different in your bug report.
Thanks for your report, but we're already aware of these shortcomings.
See bug 888320 and dependencies, or search bugzilla for "input" and "type"
in the Summary.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.