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

[Bug 13145] Spec Element.innerText

From: <bugzilla@jessica.w3.org>
Date: Mon, 15 Aug 2011 18:48:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qt2Db-00012r-6n@jessica.w3.org>

--- Comment #11 from Aryeh Gregor <ayg@aryeh.name> 2011-08-15 18:48:58 UTC ---
The algorithm in comment #0 depends on HTML, specifically <br>.  How can it go
in DOM if it depends on HTML?  Also, if it's specced as in comment #0, it will
be useless legacy cruft, so we don't want to expose it on anything other than
HTMLElement, since browsers don't support it on Element and there's no reason
for them to start.  So if it's defined like comment #0, it should be in HTML.

I agree that if we want to do a complicated rendering-dependent definition,
this should be in the same place as Selection, which should be the editing
spec.  However, currently we're not doing that no matter what, because we have
no one to write the spec text.

So if it's going to be specced anywhere right now, it should be in HTML, IMO.

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 Monday, 15 August 2011 18:49:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:01 UTC