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 23771 - "TreatUndefinedAs=Null" seems pointless
Summary: "TreatUndefinedAs=Null" seems pointless
Status: RESOLVED DUPLICATE of bug 23701
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-08 08:15 UTC by Ms2ger
Modified: 2013-11-08 22:27 UTC (History)
4 users (show)

See Also:

Attachments

Description Ms2ger 2013-11-08 08:15:40 UTC 
I don't see how it differs from the default.
Comment 1 Boris Zbarsky 2013-11-08 17:45:02 UTC 
I agree.  It's also unused.

In fact, I believe [TreatUndefinedAs] as a whole can go.  Specifically, for the values:

"Missing" is obsoleted by making that the default behavior.
"Null" is pointless as this bug says
"EmptyString" can be replaced by just making the argument optional and giving it
   a default value of "".
Comment 2 Anne 2013-11-08 22:27:51 UTC 
As I filed a bug for a weak ago, yes...

*** This bug has been marked as a duplicate of bug 23701 ***