I'm experiencing an issue with the updated 4.0.0.6 version of the CuteEditor for .NET related to the initial focus by the browser.  In version 4.0.0.5 of CuteEditor, on my page containing 3 CuteEditor components, focus would somewhat randomly be given to one of the three components.  One element was off the bottom of the visible page and if it happened to randomly get focus, the browser would jump down to that component.  In the 4.0.0.5 release, if the component had more than a page of text and itself had a vertical scrollbar, the editor with focus would also jump to the bottom of it's text (In the 4.0.0.6 release when a component in this case get's focus, the component does not jump to the bottom of the text...but rather 'without clicking it', you need to scroll to the bottom of the component to see the blinking cursor).

 

With the version 4.0.0.6 CuteEditor I am seeing very strange results.  On two of my test servers the components again get random focus.  However with the same exact source code my third server is not setting focus to any of the three components and is functioning as we want it to function.  I can't figure out why the same 4.0.0.6 component is behaving so differently on my three servers.

 

Also, I performed similar tests on the Cutesoft website example page that contains multiple editors:
http://cutesoft.net/example/Multiple.aspx

 

The very first time I loaded this page, the focus was given to the end of the text in the first editor.  Every time since them that I have reloaded/opened a new browser to the multiple.aspx page focus was not given to any of the components.  Again...very strange.

 

Is there a setting I need to change to ensure that focus is never defaulted to any of the CuteEditor components?  I hope i'm not going crazy here...

 

Thank you,

Ryan

Ryan,

 

>>The very first time I loaded this page, the focus was given to the end of the text in the first editor. 

The focus should not be given to any editor.

>>Every time since them that I have reloaded/opened a new browser to the multiple.aspx page focus was not given to any of the components. 

This behaviour is by design.

 

 

Adam,

 

I believe I may have found out what is going on...It appears that the CuteEditor component script is being cached on the client (.NET OutputCache feature?).  My local browser was continuing to use the 4.0.0.5 CuteEditor client scripts from my browser cache.  As soon as I cleared all local files/cookies/etc... from my local browser, I believe that the 4.0.0.6 scripts were finally downloaded to my client browser and focus is now NOT being set (as expected).

I still need to perform more testing from other users browsers to confirm 100% that this is what was happening.  If this is the case...I may need to have users clear their browser local files in order for their clients to start using the 4.0.0.6 code.  Or is there a central place in the CuteEditor code that I could somehow force clients to get the updated 4.0.0.6 client code?

Ryan