Briefly, I have the YUI editor for v6, and generally use it for the forum settings which I have set to display the "Post Comment" at the bottom of the forum node/comment list. When browsing in Firefox, it works fine - everywhere.

However, when using IE6 or IE7, the whole editor interface breaks, with nothing output in its proper place, and also minus the icons. Note that this is on the forum comments page display (i.e. going to a URL such as node/nn). Now, if I click a reply to summon a new page for the comment textarea, it displays absolutely fine. Ditto if I create a new forum topic, and again ditto if I use the "quote" facility offered by that module. The only time the rendering breaks is when I see a full page of node plus comments (or node on its own) and the 'post comment' box is at the bottom of the same page.

I've tried to change themes, using the standard ones, all to no avail. I've tried turning off advanced forum to use the standard one, again it breaks.

Is there anything obvious that I'm missing here, or does the YUI editor just hate IE when put into v6?

Comments

WallyJtD’s picture

WallyJtD commented

Further testing on this reveals what looks like a rendering problem with YUI editor based upon the URL displayed...

If you go to a forum node (without any comments) and click Post Reply, the YUI editor breaks on rendering the icons and other graphics - although keeping the description text for the icon groups. This happens with Firefox and IE. The URL has something like: /comment/reply/85#comment-form (note the bookmark set).

You can still select the textarea into which you can post - doing so, then pressing Preview redisplays the page, but a different one - the URL being: /comment/reply/85 - where the editor renders perfectly. If the node has comments to which you want to reply (or quote, if using that module), the URL displayed has no bookmarks and therefore the editor renders perfectly. However, replyiing to the original node (thread starter) always results in the URL having a bookmark (#comment) and breaking the editor render....

Strange I know; does anyone else experience this situation and has anyone found a fix?