CuteEditor 6.6 fails to show in tabs where 6.3 does (impacts only Chrome, FF)

Last post 04-21-2010, 1:57 PM by LOGIKonline. 3 replies.
Sort Posts: Previous Next
  •  04-21-2010, 3:00 AM 60269

    CuteEditor 6.6 fails to show in tabs where 6.3 does (impacts only Chrome, FF)

    Hi Adam,
     
       I have upgraded from 6.3 to 6.6 but the editor failed to work in the Infragistics tabs I have used ever since CuteEditor 4.x.   It only occurs in Firefox and Chrome but in Safari and IE it works fine. 
     
    The editor fails to load the toolbars and I can not click or resize the editor which is all it displays.  The editors are loaded as hidden at first but then shown later.
     
    Firefox/Chrome video: http://screencast.com/t/ZDJkOTFiMTM 
     
    Safari/IE video:  http://screencast.com/t/N2RhZTYxZ
     
    Any thoughts? 
  •  04-21-2010, 3:47 AM 60271 in reply to 60269

    Re: CuteEditor 6.6 fails to show in tabs where 6.3 does (impacts only Chrome, FF)

    After some more digging, I have found that 6.6 dll works fine if I use the old Gecko_Loader.js which came with v.6.3 (although the height is not properly set for editor's content pane Chrome but is fine in FF)
     
    Can you see about resolving the Loader.js for a clean upgrade?
  •  04-21-2010, 8:57 AM 60275 in reply to 60271

    Re: CuteEditor 6.6 fails to show in tabs where 6.3 does (impacts only Chrome, FF)

    Dear LOGIKonline,
     
    You can visit our online example http://cutesoft.net/example/general.aspx, all files are v6.6, it works in firefox and Chrome, this issue has something to do with your code, can you extract your code which can demo this issue and post it here?
     
    Regards,
    Eric
  •  04-21-2010, 1:57 PM 60286 in reply to 60275

    Re: CuteEditor 6.6 fails to show in tabs where 6.3 does (impacts only Chrome, FF)

    It is not my code, as I identified it in Gecko Loader.js  which fails now in FF and Chrome when placed inside the tab.  It DOES work fine in Safari and IE on the exact page.  The project does not allow for an easy example to be made but since I substituted the Loader from 6.3 and it does work - I will remain using that loader. 
     
    If you get other people inquiring about the oddities with FF or Chrome, you had a heads up.  
     
    If you offered uncompressed javascript files of the Loader I would do a Beyond Compare and inspect further to identify the issue.  I am always amazed how developers are so quick to dismiss it as someone else's fault.  Sending me to the stupid demo page demeans me but more so YOU.  The systems which now encapsulate your editor are more advanced than a retarded demo page.  Perhaps testing your editor inside of hidden dynamic tabs would yield different results.
     
View as RSS news feed in XML