#3584: Theme is too fragile
-----------------------+----------------------------------------------------
 Reporter:  alfonsoml  |       Owner:                
     Type:  Bug        |      Status:  new           
 Priority:  Normal     |   Milestone:                
Component:  General    |     Version:  SVN (CKEditor)
 Keywords:  Confirmed  |  
-----------------------+----------------------------------------------------
Changes (by fredck):

  * keywords:  Pending => Confirmed


Comment:

 You're right, and your TC shows the problem precisely.

 The only totally safe solution is what we have with V2, iframes to isolate
 the editor. But here we have a drastic performance payload, and this is
 one of the benefits on the V3 solution.

 We're using a "reset" mechanism, to minimize CSS conflict. But, it looks
 like it's impossible to have a perfect solution with it, because it
 depends a lot on CSS rules precedence, and the above TC shows one of these
 cases.

 The only thing that comes to my mind, is providing "information". We
 should explain the workarounds for such situations. For example, to fix
 the above TC, it should be enough to add the following rule to the page:

 {{{
 .cke_editor div
 {
         border: 0;
 }
 }}}

 In this way we compensate the previous generic rule.

 Do you have further ideas on this? Is it a "CantFix"?

-- 
Ticket URL: <http://dev.fckeditor.net/ticket/3584#comment:3>
FCKeditor <http://www.fckeditor.net/>
The text editor for Internet
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
FCKeditor-Trac mailing list
FCKeditor-Trac@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac

Reply via email to