Opened 12 years ago
Closed 12 years ago
#9223 closed Bug (fixed)
Float panel doesn't scroll with page for inline
Reported by: | Piotrek Koszuliński | Owned by: | Piotrek Koszuliński |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 4.0 |
Component: | General | Version: | 4.0 |
Keywords: | Cc: |
Description
Context menu and rich combo don't scroll with page once opened.
Change History (7)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Call for a concept review for an approach, as simple as the following code show:
// Applies for rich combo and panel button: if ( editor.elementMode == CKEDITOR.ELEMENT_MODE_INLINE ) this._.panelDefinition.parent = editor.ui.space( 'chrome' );
For context menu instead, looks like it doesn't need any fix, except for overlapping the floatspace in some case.
comment:3 Changed 12 years ago by
Owner: | set to Piotrek Koszuliński |
---|---|
Status: | new → assigned |
comment:4 Changed 12 years ago by
Status: | assigned → review |
---|
Created branch t/9223.
Richcombos and panelmenus are now positioned relatively to the toolbar (the new UI's 'chrome' element - second commit in the branch may not be a safe change) when floatspace is used. I also fixed context menu overlapping the floatspace.
comment:5 Changed 12 years ago by
Status: | review → review_passed |
---|
The patch works pretty well, I've checked thoroughly but finding no code broken by the chrome space change, so R+
comment:6 Changed 12 years ago by
I've pushed t/9223 with revert main element's id change. We don't need it and it wasn't backward compatible.
comment:7 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | review_passed → closed |
First of all - it turned out that we cannot hide panels on focus, because then reaching the end of panel which has scrollable iframe inside usually ends with disappearing panel. Not the most usable thing in the world :D
Detailed issue description from my chat with Garry:
So we've got to keep constant floatpanel to floatingspace position. There are two ways:
BTW. Context menus positioning works correctly, so this exception has to be somehow included in both solutions.