Opened 14 years ago
Closed 11 years ago
#6422 closed Bug (fixed)
Second click on combo should close it also with shared spaces
| Reported by: | Dinu | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | UI : Floating Panel | Version: | 3.1 |
| Keywords: | IE | Cc: |
Description
This is just cosmetic... the usual implementation is that clicking an expanded combo colapses the dropdown back.
Change History (11)
comment:1 Changed 14 years ago by
| Component: | General → UI : Floating Panel |
|---|---|
| Status: | new → pending |
comment:2 Changed 14 years ago by
Ok, sorry I didn't test it more, I thought it was by design. It doesn't work just for shared toolbar. (_samples/sharedspaces.html)
comment:3 Changed 14 years ago by
| Version: | → 3.4.1 |
|---|
comment:5 Changed 14 years ago by
| Status: | pending → confirmed |
|---|
Ok I see the problem; I can confirm it also on Firefox.
comment:6 Changed 14 years ago by
| Milestone: | → CKEditor 3.6 |
|---|---|
| Summary: | Second click on combo should close it → Second click on combo should close it also with shared spaces |
comment:8 Changed 14 years ago by
| Milestone: | CKEditor 3.6 |
|---|
comment:9 Changed 14 years ago by
Nope, still present:
IE7,8: go to sharedspaces sample.
- Click any of the editors with the shared toolbar
- Click on any of the dropdowns (styles, format, font, size); the dropdown box opens
- Click again on the same dropdown (on the toolbar box, not any of the options): the box closes then opens again
comment:10 Changed 12 years ago by
| Keywords: | IE added |
|---|---|
| Status: | pending → confirmed |
| Version: | 3.4.1 → 3.1 |
Reproducible in IE6-8 from CKEditor 3.1.
comment:9 shows correct TC.
comment:11 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | confirmed → closed |
I wasn't able to reproduce this problem any more in IE8 and CKEditor 4.3.3.
Note: See
TracTickets for help on using
tickets.
This is our current implementation. If it does not work for you, pleave provide more exact steps to reproduce the bug, browser and OS.
Also, can you reproduce the bug on the demo or the sample pages?