623538 - Update how <input type='email' multiple> to follow what the specifications currently say

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Mounir Lamouri (:mounir)]

The specifications about <input type='email' multiple> have just changed. We should update our implementation.

See: http://html5.org/tools/web-apps-tracker?from=5739&to=5740

Comment 1

[Andrew Quartey [:drexler]]

This looks challenging enough.I have already read up the current specs from http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#attr-input-multiple and the little pop-up widget to the side indicates firefox has partial support for the multiple attribute. Mounir, is this dependent on another feature awaiting implementation?

Comment 2

[Andrew Quartey [:drexler]]

Attachment: Impl

Comment 3

[Andrew Quartey [:drexler]]

Attachment: Impl

Wrong patch initially.

Comment 4

[Mounir Lamouri (:mounir)]

Comment on attachment 795201 [details] [diff] [review]
Impl

Review of attachment 795201 [details] [diff] [review]:
-----------------------------------------------------------------

Currently, Gecko only sanitize values that are set via script or when the element is parsed. We do not sanitize the value set by the user assuming that it will not parse constraint validation. I also do not see where in the specifications it is mentioned that the value sanitization algorithm should be run for user-entered values. A consequence of that is with this code, a valid value would not pass sanitization and the win in sanitizing is to make sure the servers can have simple values to process.

Before taking that patch, I think we should figure out if there is a problem in our implementation of value sanitization or in the HTML specifications.

Comment 5

[Marion Daly [:mdaly]]

Old patch on bug. Heads up Overholt.

Comment 6

[Andrew Overholt [:overholt]]

I don't think the assignee is still actively working on this.