Changes between Initial Version and Version 1 of Ticket #14413, comment 7


Ignore:
Timestamp:
Feb 29, 2016, 5:01:33 PM (8 years ago)
Author:
Jakub Ś
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14413, comment 7

    initial v1  
    66
    77This means that autogrow plugin works as expected (when you look at plugins default behaviour) but {{{autoGrow_onStartup}}} doesn't kick in. Now the real problem is that height either can't be calculated or is calculated incorectly for element with style {{{display:none}}} and this is what is happening in case of inactive tab. To solve this problem I would suggest to load the second editor (from inactive tab) when it is being viewed for the first time.
     8
     9
     10**NOTE:** When I removed {{{autoGrow_onStartup}}} and set {{{autoGrow_minHeight}}} to 200 I ended up with both tabs loading as to small but gaining correct size once editor was focused. Since it works correctly (I'm talking default behaviour) it is possible that {{{autoGrow_onStartup}}} calculates the height for editor in {{{display:none}}} tab incorrectly. I'm not sure however if there is anything editor can do here. I don't imagine autogrow searching DOM for {{{display:none}}} parent element and making them visible until it calculates the height.[[BR]]
     11This is IMO rather a matter of loading the instance once tab is shown for the first time or making the inactive tab visible (for example off screen) until height is calculated.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy