Yup, this is an old issue that I seem to find data in one form or another going back to 2006. My company is still using IE6 but have plans to go to IE8 sometime next year. My application will deploy before IE8 is rolled out to the company so as much as it pains me I have to be able to support IE6 till then.
Here is the issue. I have a Flex web application and because of the limited features on the Flex Rich Text Editor I am overlaying, where needed, the CKEditor. I originally was using FCKEditor for this and it worked but with some unique issues (another message on taht topic is located on these forms). When version 3.0 came out most all of the issues with Flex and FCKEditor were gone (Yup, I did a "touchdown" style dance on that one) and all looks good. A couple of issues but mostly just me learning how the new editor and config worked. Well, I have an issues that in looking back seems to have been here before fro many users.
All of my form fields, with the exception of the CKEditor are Flex classes. A user, using IE6, can enter in a subject (Flex Object) with no issues. They then click on the Message area (CKEditor) and are able to enter in a message, no problems. However, once they enter into the CKEditor (focus is set) they cannot type anywhere else. For example, if they decide, after entering a message, to alter the Subject any they will click on the subject field (Flex Object) and the cursor even shows indicatingtehy have focus but any typing they do appears in the CKEditor area as the editor has reset (stolen) the focus.
I tested this by placing an Alert Box (Flex Object) on the clicking of the subject area to see what happened. What should have happened was that when I clicked on the subject field after being in the CKEditor area is that I would have gotten the Alert and after clicking it closed receive no additional messages.
What really happens is after clicking the Alert close it again pops up (infinite loop). This is where CKEditor is reclaiming control (focus). Note that in IE7 and IE8 this does not happen.
Any ideas on this one? Again, this seems to be a bug that has been going on since 2006 with reports of it being fixed along the way but it appears to be back again.
Here is the issue. I have a Flex web application and because of the limited features on the Flex Rich Text Editor I am overlaying, where needed, the CKEditor. I originally was using FCKEditor for this and it worked but with some unique issues (another message on taht topic is located on these forms). When version 3.0 came out most all of the issues with Flex and FCKEditor were gone (Yup, I did a "touchdown" style dance on that one) and all looks good. A couple of issues but mostly just me learning how the new editor and config worked. Well, I have an issues that in looking back seems to have been here before fro many users.
All of my form fields, with the exception of the CKEditor are Flex classes. A user, using IE6, can enter in a subject (Flex Object) with no issues. They then click on the Message area (CKEditor) and are able to enter in a message, no problems. However, once they enter into the CKEditor (focus is set) they cannot type anywhere else. For example, if they decide, after entering a message, to alter the Subject any they will click on the subject field (Flex Object) and the cursor even shows indicatingtehy have focus but any typing they do appears in the CKEditor area as the editor has reset (stolen) the focus.
I tested this by placing an Alert Box (Flex Object) on the clicking of the subject area to see what happened. What should have happened was that when I clicked on the subject field after being in the CKEditor area is that I would have gotten the Alert and after clicking it closed receive no additional messages.
What really happens is after clicking the Alert close it again pops up (infinite loop). This is where CKEditor is reclaiming control (focus). Note that in IE7 and IE8 this does not happen.
Any ideas on this one? Again, this seems to be a bug that has been going on since 2006 with reports of it being fixed along the way but it appears to be back again.