author Jim Chen <>
Wed, 19 Jul 2017 14:29:59 -0400
changeset 418393 7773fb9e0bf35ad416aa2c1f785148e48d50f299
parent 302971 b39a7e4289d8de57151b826dec3902130f9d0634
child 437533 fff0a54320b0cd3924790f744f93533bfd386b1e
permissions -rw-r--r--
Bug 1351170 - 1. Correctly calculate start offset for non-text nodes; r=masayuki When the start node is a non-container node (i.e. <br>), and the start offset is 0, we should not include a newline character for the node. For example, for this range, > <br/>hello > \___/ the start node/offset is (<br/>, 0) and end node/offset is ("hello", 1). The calculated range offset should be 0, and the range length should be 2: 1 for the <br/> newline character plus 1 for "h". The patch also ensures this behavior for pre-mode nsContentIterator, for both start and end node adjustments. For start nodes, we include any non-container nodes with offset 0 in the range. For end node, we exclude any non-container nodes with offset 0 from the range. MozReview-Commit-ID: Lt2tCLbapq7