On Aug 14, 2010, at 10:14 PM, Robert O'Callahan wrote:
On Sun, Aug 15, 2010 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
That's difficult to say given that it's supported in most browsers.
We'd need to look for folks complaining to Mozilla. There's a tree of
duplicate bug reports that
On Aug 15, 2010, at 10:27 PM, Mihai Parparita wrote:
On Sun, Aug 15, 2010 at 8:41 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
actually a useful and needed feature, we should hear it. Or if someone from
Webkit or Opera wants to explain why they added it, that would be useful
too.
On Mon, 16 Aug 2010 11:23:55 +0200, Maciej Stachowiak m...@apple.com
wrote:
We do consider this, but since the status quo is every browser but
Firefox implements it, it's not clear that flipping WebKit-based
browsers from one column to the other is a genuine interoperability
improvement.
On Aug 16, 2010, at 2:49 AM, Anne van Kesteren wrote:
On Mon, 16 Aug 2010 11:23:55 +0200, Maciej Stachowiak m...@apple.com wrote:
We do consider this, but since the status quo is every browser but Firefox
implements it, it's not clear that flipping WebKit-based browsers from one
column to
Am 16.08.2010 11:23 schrieb Maciej Stachowiak:
- Is it a genuinely useful feature?
Yes, the ability to get plaintext content as rendered is a useful
feature and annoying to implement from scratch. To give one very
marginal data point, it's used by our regression text framework to
output
On Mon, Aug 16, 2010 at 9:23 PM, Maciej Stachowiak m...@apple.com wrote:
A more hypothetical use would be a rich text editor that has a convert to
plaintext feature. textContent is not as useful for these use cases, since
it doesn't handle line breaks and unrendered whitespace properly.
On Mon, Aug 16, 2010 at 1:43 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
On Mon, Aug 16, 2010 at 9:23 PM, Maciej Stachowiak m...@apple.com wrote:
A more hypothetical use would be a rich text editor that has a convert to
plaintext feature. textContent is not as useful for these use cases,
On Sun, Aug 15, 2010 at 5:57 PM, Adam Barth w...@adambarth.com wrote:
On Sat, Aug 14, 2010 at 10:14 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Aug 15, 2010 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
That's difficult to say given that it's supported in most browsers.
On Sun, Aug 15, 2010 at 6:16 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
Wouldn't you consider the interoperability benefits to the Web platform?
Not to mention the benefit of simplifying the platform a tiny bit by
removing a feature which mostly duplicates another much more well-known
On Sat, Aug 14, 2010 at 11:18 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Aug 15, 2010 at 6:16 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
Wouldn't you consider the interoperability benefits to the Web platform?
Not to mention the benefit of simplifying the platform a
On Sun, 15 Aug 2010 08:30:28 +0200, Adam Barth w...@adambarth.com wrote:
On Sat, Aug 14, 2010 at 11:18 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Aug 15, 2010 at 6:16 PM, Robert O'Callahan
rob...@ocallahan.org
wrote:
Wouldn't you consider the interoperability benefits to the
On Sun, Aug 15, 2010 at 6:30 PM, Adam Barth w...@adambarth.com wrote:
On Sat, Aug 14, 2010 at 11:18 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Aug 15, 2010 at 6:16 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
Wouldn't you consider the interoperability benefits to
On Sat, 14 Aug 2010 20:03:30 -0400, Mike Wilcox m...@mikewilcox.net
wrote:
Wow, I was just thinking of proposing this myself a few days ago.
In addition to Adam's comments, there is no standard, stable way of
*getting* the text from a series of nodes. textContent returns
everything,
innerText is one of those things IE got right, just like innerHTML. Let's
please consider making that a standard instead of removing it. Also, please
don't make the mistake of thinking it is the same thing as textContent. Think
of textContent as pre-formatted text, and innerText as plain text.
On Sun, 15 Aug 2010 11:17:43 -0400, Mike Wilcox m...@mikewilcox.net
wrote:
Michael, good try, but I've been down that road; it's pretty hard to do.
You left in the script text,
Yeh, forgot about that. I'm grabbing text nodes from anything.
spaces were missing, and there were no line
On Sun, Aug 15, 2010 at 11:17 AM, Mike Wilcox m...@mikewilcox.net wrote:
innerText is one of those things IE got right, just like innerHTML. Let's
please consider making that a standard instead of removing it. Also, please
don't make the mistake of thinking it is the same thing as
On Aug 15, 2010, at 6:26 PM, Jonas Sicking wrote:
On Sun, Aug 15, 2010 at 11:17 AM, Mike Wilcox m...@mikewilcox.net wrote:
innerText is one of those things IE got right, just like innerHTML. Let's
please consider making that a standard instead of removing it. Also, please
don't make the
What about lists? Alt text in img?
Rob
--
Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true. [Acts 17:11]
On Aug 15, 2010, at 7:29 PM, Robert O'Callahan wrote:
What about lists? Alt text in img?
It handles lists and the line breaks, but it doesn't indent.
Image attributes are ignored.
Mike
On Mon, Aug 16, 2010 at 12:35 PM, Mike Wilcox m...@mikewilcox.net wrote:
On Aug 15, 2010, at 7:29 PM, Robert O'Callahan wrote:
What about lists? Alt text in img?
It handles lists and the line breaks, but it doesn't indent.
Image attributes are ignored.
Tables? Is there any documentation
On Aug 15, 2010, at 7:53 PM, Robert O'Callahan wrote:
Tables?
TDs are inline and TRs act as line breaks.
Is there any documentation for how the serialization works?
I'm just running the tests as you guys request them. I'm not sure if or how
well this feature is spec'd out.
Mike
On Mon, 16 Aug 2010 09:17:42 +0800, Mike Wilcox m...@mikewilcox.net
wrote:
On Aug 15, 2010, at 7:53 PM, Robert O'Callahan wrote:
Tables?
TDs are inline and TRs act as line breaks.
Is there any documentation for how the serialization works?
I'm just running the tests as you guys
On Sun, Aug 15, 2010 at 8:41 PM, Robert O'Callahan rob...@ocallahan.org wrote:
actually a useful and needed feature, we should hear it. Or if someone from
Webkit or Opera wants to explain why they added it, that would be useful
too.
FWIW, WebKit has supported innerText since at least when it
== Use Case ==
It's common that a web page has a string of untrusted characters
(e.g., received via cross-site XMLHttpRequest or postMessage) that it
wishes to display to the user. The page wants to display the string
using a simple, secure API.
== Workarounds ==
Currently, the path of least
Wow, I was just thinking of proposing this myself a few days ago.
In addition to Adam's comments, there is no standard, stable way of *getting*
the text from a series of nodes. textContent returns everything, including
tabs, white space, and even script content.
BTW, I haven't checked, but I
On Sat, 14 Aug 2010, Adam Barth wrote:
We should expose a property on HTMLElement similar to innerHTML called
innerText. When assigning a string to innerText, the string is placed
in a text node (and is not parsed as HTML).
How would this differ from textContent?
HTMLElement.innerText
On Sat, Aug 14, 2010 at 5:04 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 14 Aug 2010, Adam Barth wrote:
We should expose a property on HTMLElement similar to innerHTML called
innerText. When assigning a string to innerText, the string is placed
in a text node (and is not parsed as HTML).
On Sun, Aug 15, 2010 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
That's difficult to say given that it's supported in most browsers.
We'd need to look for folks complaining to Mozilla. There's a tree of
duplicate bug reports that lead to
On Sat, Aug 14, 2010 at 10:14 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Sun, Aug 15, 2010 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
That's difficult to say given that it's supported in most browsers.
We'd need to look for folks complaining to Mozilla. There's a tree of
29 matches
Mail list logo
