Changes between Initial Version and Version 1 of Ticket #9814, comment 8


Ignore:
Timestamp:
Apr 29, 2014, 11:01:13 AM (6 years ago)
Author:
Piotrek Koszuliński
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9814, comment 8

    initial v1  
    1 I remember that there were some problems with initializing editor in hidden elements. Problems which could not be solved. But if I remember correctly, they were related to the classic editor (using iframe). It indeed makes sense to investigate this.
     1I remember that there were some problems with initializing editor in hidden elements. Problems which could not be solved. But if I remember correctly, they were related to the classic editor (using iframe). It indeed makes sense to investigate the case described in this ticket, because it's related to inline editor, so it may be a different problem.
    22
    3 What should check if editor can be initialized in hidden element and if it's usable after the element has been shown. I mean only setting display property. Not detaching editor's DOM which is a separate topic (and in case of classic editor it won't be fixed because of browsers nature and complexity of the hack).
     3However, we should check if **all kinds** (even classic editor) of editors can be initialized in hidden elements and if they are usable after the elements have been shown. This TC covers only setting display property. Not detaching editor's DOM which is a separate topic (and in case of classic editor it won't be fixed because of browsers nature and complexity of the hack).
    44
    55I'm setting milestone to 4.4.2. It does not mean that we'll fix all issues. First we need to find what is really broken.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy