Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88123 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54533 invoked from network); 9 Sep 2015 11:24:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Sep 2015 11:24:47 -0000 Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 176.9.114.167 spritz.beccati.com Received: from [176.9.114.167] ([176.9.114.167:33340] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/00-54133-DF610F55 for ; Wed, 09 Sep 2015 07:24:46 -0400 Received: (qmail 23911 invoked from network); 9 Sep 2015 11:24:42 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 9 Sep 2015 11:24:42 -0000 To: Christoph Becker , internals@lists.php.net References: <55EF58B4.4080005@gmx.de> X-Enigmail-Draft-Status: N1110 Message-ID: <55F016E9.3000309@beccati.com> Date: Wed, 9 Sep 2015 13:24:25 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55EF58B4.4080005@gmx.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] DOMElement::nodeValue is not W3C conforming From: php@beccati.com (Matteo Beccati) Hi Christoph, > In bug #70029 it has been reported that DOMElement::nodeValue currently > does not conform to the W3C specs. Instead of NULL, it returns the > ::textContent. > > I had committed the patch for master only, to avoid the undesirable BC > break for PHP 5.6, but there have been concerns that the BC break might > even be to severe for PHP 7.0. > > Therefore I'm bringing this issue to the list. Is it okay to fix the > behavior for PHP 7.0? Shall we wait until 7.1? Does that require an RFC? I don't think it requires an RFC, but I would say it it safer to leave it for 7.1, unless extremely pressing. As little as it might seem it's still a BC-break that would be otherwise introduced in 7.0-rc3. That said, I'll be ok if it gets fixed in 7.0. I just raised it as it was causing PHPUnit to bypass all the tests, thus broken builds for all the projects depending on it. Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/