W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2011

[Bug 12798] Default to [TreatNullAs=EmptyString]

From: <bugzilla@jessica.w3.org>
Date: Mon, 20 Jun 2011 17:48:12 +0000
To: public-script-coord@w3.org
Message-Id: <E1QYia4-0006sy-8v@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12798

Brendan Eich <brendan@mozilla.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brendan@mozilla.org

--- Comment #23 from Brendan Eich <brendan@mozilla.org> 2011-06-20 17:48:10 UTC ---
Need to survey some Gecko/WebKit/Presto forks of content that might care. I
wrote in public-script-coord:

Could someone cite some examples on the web?

I'm prepared to believe they are Out There. We might have to cater to them with
some quirks mode or other. But we need a survey to study the de-facto standard
requirements.

BTW, I'm sympathetic to the idea that WebIDL, for historical or even just-so
ahistorical reasons, might want a "nullable DOMString" type. This is not that
JS-friendly, and JS matters a lot more than Java, C#, etc. But it still could
be that WebIDL and users, even users of the JS APIs, want null -> "" (a falsy
value).

So ignoring compatibility constraints, and ignoring the separate
falsy-might-be-better argument, I'd prefer "ECMAScript ToString" semantics.

But we can't ignore those two issues, I agree. We need to study some JS on the
web that cares.
---

The breaking change could be bad: falsy value becomes truthy, changing control
flow. Also, less bad but still pretty bad: you see "null" instead of "" in data
that is presented to the user.

/be

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 20 June 2011 17:48:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:03 UTC