Slight delay before CSS is applied

I'm creating an editor by doing a replace() on an element. In the config object, I set the path for a css file. When the editor replaces the content in the div, there is a split second delay before the CSS in the specified path is applied which creates this ugly transition between the two. Any suggestions for improving this if possible?

Wed, 05/11/2011 - 03:27

test1

Joined: 20/04/2011

Posts: 13

Re: Slight delay before CSS is applied

Any ideas on this at all would be helpful. This causes an issue with the autosize plugin because when it first loads, the font is larger and then the css gets applied and the font becomes smaller but the boxes height was set to match the larger font.

Does anyone know why the css isn't applied when the text first loads? I at least need to find a way to detect when the editor is completely loaded meaning the loaded and css applied so I can hide it until it's complete.

Wed, 05/11/2011 - 11:59

typeof

Joined: 24/04/2011

Posts: 99

Re: Slight delay before CSS is applied

Could you publish a test case illustrating this problem?

Wed, 05/11/2011 - 18:19

test1

Joined: 20/04/2011

Posts: 13

Re: Slight delay before CSS is applied

You can actually see the problem occur in the "divreplace" sample that comes in the _samples folder with ckeditor. It's more noticeable in firefox then in chrome. It only really happens for a split second, but it becomes a problem when you have other things on the page and autosize on because when the div gets replaced, everything on the page gets pushed down for a split second and then pops back up into place.

This shows that the CSS isn't fully applied before the events get triggered to say the editor is ready. I'm just trying to track down if there is a way to fire an event after the css is applied. Otherwise I might just have to put a timed delay on it which is sort of lame.

Thu, 05/12/2011 - 00:18

typeof

Joined: 24/04/2011

Posts: 99

Re: Slight delay before CSS is applied

CKEditor creates a LINK element to fetch your CSS and I don't think that it cares about the loading/applying progress.

So generally everything is up to the browser...

You mentioned hiding editor until the CSS is loaded. Maybe simply unhide it in your CSS file?