Hm, I guess I've been successfully convinced otherwise (i.e., "patch
upcoming!")... ^_^;
- Roland
On Tue, Mar 23, 2010 at 5:53 PM, Maciej Stachowiak wrote:
>
> On Mar 23, 2010, at 1:40 AM, Roland Steiner wrote:
>
> Hm, but the first line could also be a comment (starting with '#') which
> Mozil
On Mar 23, 2010, at 1:40 AM, Roland Steiner wrote:
Hm, but the first line could also be a comment (starting with '#')
which Mozilla also skips. IOW, I read the spec as "return the first
line that is a (valid) URL". But of course I could be convinced
otherwise...
It doesn't start with "#"
On Tue, 23 Mar 2010, Roland Steiner wrote:
>
> Hm, but the first line could also be a comment (starting with '#') which
> Mozilla also skips. IOW, I read the spec as "return the first line that
> is a (valid) URL". But of course I could be convinced otherwise...
The empty string is a valid URL.
Hm, but the first line could also be a comment (starting with '#') which
Mozilla also skips. IOW, I read the spec as "return the first line that is a
(valid) URL". But of course I could be convinced otherwise...
Cheers,
- Roland
On Tue, Mar 23, 2010 at 5:37 PM, Maciej Stachowiak wrote:
>
> On
On Mar 23, 2010, at 1:01 AM, Roland Steiner wrote:
Hi all,
On the topic of dataTransfer.setData, there seems to be a small
inconsistency between browsers when it comes to leading new-lines.
e.g., dataTransfer.setData("text/uri-list", "\nhttp://foo";) followed
by dataTransfer.getData("URL
Hi all,
On the topic of dataTransfer.setData, there seems to be a small
inconsistency between browsers when it comes to leading new-lines. e.g.,
dataTransfer.setData("text/uri-list", "\nhttp://foo";) followed by
dataTransfer.getData("URL").
Mozilla returns an empty string (see
http://mxr.mozilla.
6 matches
Mail list logo
