Clicking on "Switch to Plain Text" collapses text input DIV.
| Project: | YUI Rich Text Editor |
| Version: | 6.x-2.32 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Browser: Firefox 3.04
When either editing existing content or creating new content, if I click the "Switch to Plain Text" button, the message input textarea completely collapses, allowing you to neither see nor edit the content. Clicking on "Switch to Rich Text Editor" restores it fine.
Firebug also reports:
oTidyBrowser is not defined
$('#toggleEditor-'+id).bind('click', function () { toggle = 'on'; });
which points to:
69 var toggle = 'off';
70 $('#toggleEditor-'+id).bind('click', function () { toggle = 'on'; });
71 $('form').bind('submit', function (e) {
72 if (toggle == 'on') {
73 toggle = 'off';
74 return false;
75 }
IIRC this oTidyBrowser error, which I've seen before with non-Drupal, non-YUI sites, is a catch-all for memory leaks or some such thing. But to be safe, I disabled Web Developer and restarted the browser. It made no difference.
#1
I tried this on FF 3.0.1, 3.0.2, and 3.0.4 with no problem. I also tried it using YUI 2.6.0 and 2.5.2. This was in Windows XP.
Send over a screenshot and/or let's see if anyone else has had this issue?
#2
Unable to duplicate.
#3
I'll do you one better. You can see for yourself. Go to http://www.homeownerslike.us. Register a username. Then click on "Homepage" in the top nav. That will drop you in the editor. Click on the "Switch to Plain Editor" button. The message editor collapses and disappears.
#4
Reactivating this with a link to an example of the problem (See Msg #3 in this thread). It happens in both FF3 and IE7 so it's likely not a browser problem but a CSS/JS collision somewhere.
#5
I can duplicate this behavior if both Coder button and plaintext button are activated, which it says on the editor settings page should not be the case. So smanes, could you check this in your settings?
#6
Yes, disabling Coder button fixed my (same) problem, so it seems that it is somehow related to the issue.
100% it has nothing to do with CSS, as I know CSS very well it doesn't operate with collapsing windows etc. It is more JavaS-related issue imho. In may depends from WebBrowser, however it doesn't look so. I'm using Opera 10 aplha and Firefox 3.1 beta 2, so very experimental browsers and this issue was in both and after unchecking was in nor one.
What is important too - I'm using Drupal 5.16 with YUI 2.5.0
p.s. I' love this module. TY!