Opened 16 years ago
Closed 15 years ago
#3292 closed Bug (expired)
CKEDITOR.dom.range.getBoundaryNodes with collapsed range
| Reported by: | Garry Yao | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.1 |
| Component: | General | Version: | |
| Keywords: | Cc: |
Description
Currently the 'getBoundaryNodes' function is returning incorrect elements when range is collapsed, based on the semantic of the function, it should return 'null' for boundary nodes instead.
Attachments (1)
Change History (4)
Changed 16 years ago by
| Attachment: | range_boundaryNodes_collapsedRange.patch added |
|---|
comment:1 Changed 16 years ago by
A concrete example of failure caused by this bug would be when you asking 'CKEDITOR.dom.range.checkEndOfBlock' with the following, it will give a positive answer, which is wrong.
<p>^text</p>
comment:2 Changed 16 years ago by
| Milestone: | CKEditor 3.0 → CKEditor 3.1 |
|---|
It looks like we don't need getBoundaryNodes anymore. The code using it should now use the dom walker to achieve in boundaries processing.
We need to check it later.
comment:3 Changed 15 years ago by
| Resolution: | → expired |
|---|---|
| Status: | new → closed |
There's still few usage of CKEDITOR.dom.range::checkEndOfBlock in the codebase but we're about to deprecate it, so this ticket expired.
Note: See
TracTickets for help on using
tickets.
Unit Test Case