W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 19968] splitText() can create ranges with end before start

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Nov 2012 11:49:40 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19968-2532-d0LfEsAPw9@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19968

--- Comment #1 from Mats Palmgren <matspal@gmail.com> ---
> IE gives "(#text bc, 2) (BODY null, 1)", which is the most
> broken of all.

I think the latest IE has been fixed.
The result I get with the preview version(*) of IE10 for Windows 7 is:
(#text bc, 1) (BODY null, 2) 

(*) IE10.0.9200.16438 to be exact

Furthermore, the subset of tests in test_Range-mutations.html that failed
with my fix in 803924 also fails in that IE version:

splitTextTests.push(
        ["paras[0].firstChild", 1, "paras[0]", 0, "paras[0]", 1],
        ["paras[0].firstChild", 1, "paras[0]", 1, "paras[0]", 1],
        ["paras[0].firstChild", 1, "paras[0].firstChild", 1, "paras[0]", 1],
        ["paras[0].firstChild", 2, "paras[0].firstChild", 1, "paras[0]", 1],
        ["paras[0].firstChild", 3, "paras[0].firstChild", 1, "paras[0]", 1],
        ["paras[0].firstChild", 1, "paras[0].firstChild", 2, "paras[0]", 1]
);

After I fixed the testSplitText() function in test_Range-mutations.html
to implement the proposed spec change, both IE and my patched Firefox
pass those tests.

I think this strengthens the argument for changing the spec in the way
I propose, since two UA vendors have *independently* implemented the
same fix.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 16 November 2012 11:49:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 16 November 2012 11:49:42 GMT