- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Feb 2015 06:32:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #155 from Koji Ishii <kojiishi@gmail.com> --- I put test cases on jsbin: http://jsbin.com/casoyi Chrome Canary: 1. B1,SIP,SR1,H1,BODY,HTML,[object HTMLDocument],[object Window] 2. B2,SR2,H2,BODY,HTML,[object HTMLDocument],[object Window] 3. C3,SR4 Chrome with experimental impl: 1. B1 2. B2,SR2 3. C3,SR4 Could you tell me what the current Gecko gives? That'd help us to figure out if the bug is in algorithm, or in my impl. The third case was added because I added an assertion to ensure the INSERTION-POINTS stack is empty at the end of the algorithm, and it fails on one of our tests for editing. The produced event paths are the same. Not sure if this is an non-issue, or issues in both algorithm. Hayato, do you have insights? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 16 February 2015 06:32:53 UTC