oo... sory there was no Cc: [EMAIL PROTECTED]
send again.
--
hi Ian :
> On Mon, 2 May 2005, Toshirou Takahashi wrote:
> > >
> > > You can already do this -- just include the correct encoding
> > > information in the Content-Type header for the JS file, as in:
> > >
> > >Content-Type: text/
On Mon, 2 May 2005, Toshirou Takahashi wrote:
> >
> > You can already do this -- just include the correct encoding
> > information in the Content-Type header for the JS file, as in:
> >
> >Content-Type: text/javascript;charset=utf-8
>
> It is a good method. I also agree and I can do.
>
> H
Ian Hickson wrote:
> On Sun, 1 May 2005, Toshirou Takahashi wrote:
> >
> > i hope to add the charset attribute to HTMLScriptElement, on 2.12.1.
> >
> > Because the person who made .js file doesn't know whether the file is
> > used with what charset all over the world.
>
> You can already do t
On Sun, 1 May 2005, Anne van Kesteren wrote:
>
> I was thinking about checking descendents instead of children as last
> option. Not sure how that is for performance though. Perhaps the
> specification should be updated after real world problems have occured
> with the current specification ins
Ian Hickson wrote:
It was intended. Whether it is desired or not, I am not 100% sure.
I'm open to alternate algorithms.
I was thinking about checking descendents instead of children as last
option. Not sure how that is for performance though. Perhaps the
specification should be updated after real w
On Sun, 1 May 2005, Anne van Kesteren wrote:
> >
> > It returns 0, because the table contains neither tbody nor tr
> > children.
>
> I was wondering if that was desired.
It was intended. Whether it is desired or not, I am not 100% sure. I'm
open to alternate algorithms.
> > As the spec says:
On Sun, 1 May 2005, Anne van Kesteren wrote:
>
> You really want to use the BOM of UTF-8 instead of this I guess.
See
http://www.ietf.org/internet-drafts/draft-hoehrmann-script-types-02.txt
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
ï wrote:
Wouldn't it be safer to declare the encoding in the js file itself?
It could be in a magic comment at the start of the document:
//@charset("utf8")
Not very elegant, but less error prone than to specify the encoding
everywhere the file is included.
You really want to use the BOM of UTF-8
Ian Hickson wrote:
What happens here:
[snip]
It returns 0, because the table contains neither tbody nor tr
children.
I was wondering if that was desired.
This 'messes up' perfectly valid tables like:
[snip]
... no?
As the spec says: The colspan and rowspan attributes are ignored by
this algorithm.
On Fri, 29 Apr 2005, Anne van Kesteren wrote:
>
> Some initial comments on possible problems I spotted.
Thanks!
> # Columns, rows, and cells can each have specific classes applied to
> # them by the data provider.
>
> Classes is nowhere defined. Is this about the HTML CLASS attribute? If
> so,
On Sun, 1 May 2005, Toshirou Takahashi wrote:
>
> i hope to add the charset attribute to HTMLScriptElement, on 2.12.1.
>
> Because the person who made .js file doesn't know whether the file is
> used with what charset all over the world.
You can already do this -- just include the correct encod
Wouldn't it be safer to declare the encoding in the js file itself?
It could be in a magic comment at the start of the document:
//@charset("utf8")
Not very elegant, but less error prone than to specify the encoding
everywhere the file is included.
regards
Olav Junker Kjær
Toshirou Takahashi wrot
12 matches
Mail list logo
