Opened 9 years ago
Closed 9 years ago
#13909 closed Bug (worksforme)
Bleeding test for fake selection
| Reported by: | Marek Lewandowski | Owned by: | Tomasz Jakut |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 4.5.5 |
| Keywords: | Cc: |
Description (last modified by )
On master we have bleeding test test auto fake selection.
We need to investigate what is the reason for this.
Change History (13)
comment:1 Changed 9 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 9 years ago by
| Description: | modified (diff) |
|---|---|
| Status: | new → confirmed |
comment:3 Changed 9 years ago by
| Version: | 4.5.4 → 4.5.5 (GitHub - master) |
|---|
comment:4 Changed 9 years ago by
| Owner: | set to Tomasz Jakut |
|---|---|
| Status: | confirmed → assigned |
comment:5 Changed 9 years ago by
| Milestone: | CKEditor 4.5.5 → CKEditor 4.5.6 |
|---|
comment:6 Changed 9 years ago by
| Milestone: | CKEditor 4.5.6 → CKEditor 4.5.5 |
|---|---|
| Owner: | Tomasz Jakut deleted |
| Status: | assigned → confirmed |
comment:7 Changed 9 years ago by
| Milestone: | CKEditor 4.5.5 → CKEditor 4.5.6 |
|---|
I accidentaly changed the milestone while unassinging myself, so I'm reverting it.
comment:8 Changed 9 years ago by
| Owner: | set to Tomasz Jakut |
|---|---|
| Status: | confirmed → assigned |
comment:9 Changed 9 years ago by
| Status: | assigned → review |
|---|
The problem is caused by the change in Chromium codebase. For some time Chrome throws uncatchable error when someone tries to select more than one range. The detailed description of that problem is available on Chromium tracker.
Therefore the only solution that works is preventing Chrome from trying to select more than one range at once. It seems to be a cosmetical change, because before changes in Chromium selecting more than one range resulted in selecting only the first one.
Pushed branch:t/13909.
comment:10 Changed 9 years ago by
| Milestone: | CKEditor 4.5.6 → CKEditor 4.5.7 |
|---|
comment:11 Changed 9 years ago by
| Milestone: | CKEditor 4.5.7 → CKEditor 4.5.8 |
|---|
comment:12 Changed 9 years ago by
| Milestone: | CKEditor 4.5.8 → CKEditor 4.5.9 |
|---|
comment:13 Changed 9 years ago by
| Milestone: | CKEditor 4.5.9 |
|---|---|
| Resolution: | → worksforme |
| Status: | review → closed |
It looks that this problem has been fixed by the Chromium team, and Chrome no longer throws this exception.
This is not a recent regression it's at least since 4.4.7.