This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following error messages :- "Attribute placeholder is only allowed when the input type is e-mail, number, password, search, tel, text, or url." and "Attribute required is only allowed when the input type is checkbox, date, datetime, datetime-local, e-mail, file, month, number, password, radio, search, tel, text, time, url, or week." Are incorrect for the following markup. <input id="email" name="email" class="form-control" placeholder="Enter Email" type="email" required> The correct type is "email" and NOT "e-mail" as confirmed by MDN documentation. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input Please advise.
Yes, I also noticed this issue today... placeholder is allowed on type="email"
Same for the "maxlength" attribute.
Same for "required" and "pattern" attributes: Attribute required is only allowed when the input type is checkbox, date, datetime, datetime-local, e-mail, file, month, number, password, radio, search, tel, text, time, url, or week. <input type="email" required pattern="@"> Attribute pattern is only allowed when the input type is e-mail, password, search, tel, text, or url. <input type="email" required pattern="@">
Same as bug 28362 *** This bug has been marked as a duplicate of bug 28362 ***
Why is the bug I posted marked as being a duplicate of a bug posted more than 24 hours later!!!!.
(In reply to omar.crea from comment #2) > Same for the "maxlength" attribute. (In reply to Alexey Smolianinov from comment #3) > Same for "required" and "pattern" attributes: > > Attribute required is only allowed when the input type is checkbox, date, > datetime, datetime-local, e-mail, file, month, number, password, radio, > search, tel, text, time, url, or week. > <input type="email" required pattern="@"> > > Attribute pattern is only allowed when the input type is e-mail, password, > search, tel, text, or url. > <input type="email" required pattern="@"> All caused by the same bug, all now fixed. (In reply to Phil Ellett from comment #5) > Why is the bug I posted marked as being a duplicate of a bug posted more > than 24 hours later!!!!. Dunno but thanks for taking time to report it originally.