Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104884
MIME-Version: 1.0
References: <CAEPJdu=DYZ8RTUtb-mDOGPdXGK4Z-h59rUq_A=wB=u6AaO7aDg@mail.gmail.com>
 <C3F1FF05-7D74-4B5F-82D9-B527B4E5F9BB@gmail.com>
In-Reply-To: <C3F1FF05-7D74-4B5F-82D9-B527B4E5F9BB@gmail.com>
Date: Sat, 23 Mar 2019 10:33:46 +0100
Message-ID: <CAEPJdu=dQFwB6=YXBAW0REXP+bZHUrRxkbDsKwyQLAXBr-iSzA@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: PHP Internals <internals@lists.php.net>, Thomas Weinert <thomas@weinert.info>
Content-Type: multipart/alternative; boundary="000000000000cc9e740584bfab85"
Subject: Re: [PHP-DEV] [RFC] DOM Living Standard API
From: kontakt@beberlei.de (Benjamin Eberlei)

--000000000000cc9e740584bfab85
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 22, 2019 at 11:26 PM Claude Pache <claude.pache@gmail.com>
wrote:

> Beware that behaviour of some methods should differ between HTML and
> non-HTML documents. For instance, the RFC says:
>
> > DOMElement=E2=86=92nodeName casing was previously undefined, it is now =
changed
> to always uppercase.
>
> However, the DOM Living Standard says it is uppercase (even,
> ASCII-uppercased) only in the HTML namespace. For XML documents, the casi=
ng
> is not modified.
>

You are absolutely right, i missed that in the convoluted description of
the behavior :-) I need to rethink how this would fit with the
compatibility flags, it might cause a problem given that loadHTML for
example doesn't automatically put the elements into HTML namespace. I
updated the RFC to reflect this.

To be honest, the compatibility thing is what i am least sure in,
especially if this should be combined with the new methods + removal of
unused code or should be handled separately.


> =E2=80=94Claude
>
>

--000000000000cc9e740584bfab85--