W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13145] Spec Element.innerText

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Jul 2011 20:40:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QeYtp-0003SM-Ue@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13145

--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-06 20:40:45 UTC ---
I've been told in no uncertain terms that it's not practical for non-Gecko
browsers to remove.  Depending on the rendering tree to the extent WebKit does,
on the other hand, is insanely complicated to spec in terms of standard stuff
like DOM and CSS.  Also, it potentially breaks for detached nodes (WebKit
behaves totally differently in that case).  I do have an abortive effort here:

http://aryeh.name/spec/innertext/innertext.html

But Gecko people seemed pretty unhappy about this kind of complexity and
rendering dependence in a DOM property.  And on the other hand, I got the
impression WebKit is reluctant to rewrite their innerText implementation at
all.  So I'm figuring that the spec that will be implemented by the most
browsers possible is one that's as simple as possible, basically just a compat
shim.  If multiple implementers actually want to implement something like the
innerText spec I started writing, I'd be happy to resume work on it, but that
wasn't my impression.

Do you have a link to info about the <script> issue?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 6 July 2011 20:40:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC