On Mon, Aug 25, 2008 at 6:07 PM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
> Garrett Smith wrote:
There are probably others but I can't think of them. I think the
majority of the time that strings will want to go to ToString,
booleans will want to go to ToBoolean.
>>>
>>> That c
On Mon, Aug 25, 2008 at 12:47 PM, Boris Zbarsky <[EMAIL PROTECTED]> wrote:
> Garrett Smith wrote:
>>
>> The addition operator results in concatenation when either operand is
>> a string. This results in a calls to the internal ToString, which is
>> what I'm suggesting should be the general rule.
>
Garrett Smith wrote:
There are probably others but I can't think of them. I think the
majority of the time that strings will want to go to ToString,
booleans will want to go to ToBoolean.
That can be the default, perhaps. But I suspect usually null should become
"", not "null".
Why?
Note
I just noticed two issues with the last call widget requirements draft:
1. R11 text [1] should replace "Private Key Infrastructures (PKI)"
with "Public Key Infrastructures (PKI)"
2. XML Signature reference [2] should reference the Second Edition of
XML Signature, which includes updating
Garrett Smith wrote:
The addition operator results in concatenation when either operand is
a string. This results in a calls to the internal ToString, which is
what I'm suggesting should be the general rule.
All I'm saying is that this will require annotating a very large number
of API method
On Mon, Aug 25, 2008 at 11:28 AM, Boris Zbarsky <[EMAIL PROTECTED]> wrote:
> Garrett Smith wrote:
>>
>> window.open();
>
> Which should be equivalent to window.open(undefined) (and isn't in some
> UAs), right?
>
> What should window.open(null) do?
>
>> If the first argument is null or undefined or
Garrett Smith wrote:
window.open();
Which should be equivalent to window.open(undefined) (and isn't in some
UAs), right?
What should window.open(null) do?
If the first argument is null or undefined or the empty string, no uri
is loaded and an blank/empty window is displayed.
This is not
On Mon, Aug 25, 2008 at 10:20 AM, Boris Zbarsky <[EMAIL PROTECTED]> wrote:
> Garrett Smith wrote:
>>
>> I already expressed my opinion, agreeing with Liorean. For domstring
>> arguments, call the internal ToString on the input would be the
>> general rule, unless otherwise stated. This would seem
Garrett Smith wrote:
I already expressed my opinion, agreeing with Liorean. For domstring
arguments, call the internal ToString on the input would be the
general rule, unless otherwise stated. This would seem to cover the
majority of cases.
window.open is one of the cases when things are not c
On Mon, Aug 25, 2008 at 8:02 AM, Boris Zbarsky <[EMAIL PROTECTED]> wrote:
> Garrett Smith wrote:
>>>
>>> [Null=Null, Undefined=Null]
>>> [Null=Null, Undefined=Empty]
>>> [Null=Empty, Undefined=Empty]
>>> [Null=Null, Undefined=String]
>>> [Null=Empty, Undefined=String]
>>> [Null=String, Undef
Garrett Smith wrote:
[Null=Null, Undefined=Null]
[Null=Null, Undefined=Empty]
[Null=Empty, Undefined=Empty]
[Null=Null, Undefined=String]
[Null=Empty, Undefined=String]
[Null=String, Undefined=String]
...so that we can do, e.g.:
Window open([Null=String, Undefined=String] in DOMS
On Tue, May 6, 2008 at 4:04 AM, Ian Hickson <[EMAIL PROTECTED]> wrote:
>
> heycam -- see at the end for a request for WebIDL.
>
> On Mon, 25 Apr 2005, Brad Neuberg wrote:
>>
>> True, but having prototypes on DOM objects can be extremely useful and
>> provide all sorts of very powerful options. Mo
12 matches
Mail list logo
