A role on our site has access to Full HTML, Filtered HTML, and PHP Code input formats. We have different style sheets for Full and Filtered HTML.

When I toggle between Full and Filtered HTML, the text editor is updated appropriately. However if I start to toggle between one of the HTML input formats and PHP Code in Internet Explorer 8, it breaks. Specifically, another textarea appears below the text editor, and any further toggling between Full and Filtered HTML does not change the text editor styling.

See the attached picture for more information. We are not seeing this issue in Firefox, and we have implemented FCKEditor 2.6.4.1, on Drupal 5.19 using WYSIWYG 5.x-2.0.

CommentFileSizeAuthor
wysiwyg-error.png51.93 KBsgdev

Comments

sun’s picture

sgdev’s picture

Hmm... similar look of the problem, but not the same. It seems as though #527920 happens every time users access a node to edit, as soon as they reach the page. I'm not seeing this issue. Also our issue is not a problem in Firefox, Safari, Opera, or Chrome. Only IE8.

As well, this is specifically connected to the PHP Code input format. When toggling between Filtered HTML and Full HTML, there is no issue.

sun’s picture

Title: Toggling between Input formats in IE8 causes text editor issues » FCKeditor: IE8: Switching to PHP input format adds a duplicate textarea
Status: Active » Postponed (maintainer needs more info)

Better title. Still no clue.

Phliplip’s picture

I also have this issue, when switching between WYSIWYG powered inputformat and pure text input format.

Also, no problem on FF - Only Internet Explorer (8)

twod’s picture

I am not able to reproduce this using IE8, TinyMCE, Wysiwyg 5.x-2.0 and jQuery update 5.x-2.0 on a new Drupal 5.21 installation. (Or when using a D6 install with the same editor.)
Are you seeing any JavaScript errors (lower left corner of statusbar in IE) when switching to an input format using the 'none' editor?

If the editor instance is not removed there should be some error or malfunction in the tinymce-3.js file (assuming you're using TinyMCE, like in the screenshot).
If not, are you able to attach a debugger to the process, insert a breakpoint in the detach() method and step through it?

sun’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Sorry, without further information this issue can only be marked as won't fix.

Feel free to re-open this issue if you want to provide further information. Thanks.