[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: DOM::Document::getElementsByTagName bug ?
From:       Shift <shift () free ! fr>
Date:       2004-02-02 19:03:44
Message-ID: 200402022003.44568.shift () free ! fr
[Download RAW message or body]

Le lundi 2 Février 2004 10:49, pettay@mappi.helsinki.fi a écrit :
> Just FYI,
>
> http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/html.html#ID-535378
>2642
>
> >Developers need to take two things into account when writing code that
> >works on both HTML and XHTML documents. When comparing element or
> > attribute names to strings, the string compare needs to be case
> > insensitive, or the element or attribute name needs to be converted into
> > lowercase before comparing against a lowercase string. Second, when
> > calling methods that are case insensitive when used on a HTML document
> > (such as
> >getElementsByTagName() and namedItem()), the string that is passed in
> >should be lowercase.
>
> Quoting David Faure <faure@kde.org>:
> > On Monday 02 February 2004 09:16, Shift wrote:
> > > Le lundi 2 Février 2004 08:37, David Faure a écrit :
> > > > No. For HTML documents (not XHTML nor XML), tags are exposed
> >
> > uppercase.
> >
> > > So I should check for both ? upper and lowercase ?
> >
> > Yes, I'd say so.
> >
> > > http://bugs.kde.org/show_bug.cgi?id=57803 is a testcase.
> >
> > I see. Well, it's XHTML, so tags are exposed lowercase - no bug.
> >
> > --
> > David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
> > Konqueror (http://www.konqueror.org), and KOffice
> > (http://www.koffice.org).

Thanks a lot  to you and David.
I can fix my problem now.

Franck

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic