This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14169 - setCustomValidity should have [TreatNullAs=EmptyString] for compat with opera/webkit/moz
Summary: setCustomValidity should have [TreatNullAs=EmptyString] for compat with opera...
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 14:22 UTC by contributor
Modified: 2011-09-16 06:44 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-09-15 14:22:10 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/association-of-controls-and-forms.html
Multipage: http://www.whatwg.org/C#dom-cva-setcustomvalidity
Complete: http://www.whatwg.org/c#dom-cva-setcustomvalidity

Comment:
setCustomValidity should have [TreatNullAs=EmptyString] for compat with
opera/webkit/moz

Posted from: 85.227.155.223 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.51
Comment 1 Anne 2011-09-15 17:21:27 UTC 
Opera/Mozilla/WebKit are the ones that are doing the null -> "" the wrong way around. If we switch the default why does this method needs to be preserved?