Opened 15 years ago

Closed 15 years ago

#231 closed defect (fixed)

Plugin - SuperClean: TEXT MODE message

Reported by: ianb@… Owned by: gogo
Priority: normal Milestone:
Component: Xinha Core Version:
Severity: normal Keywords:
Cc:

Description

When you use the SuperClean? plugin and you get the cleaning options, the status bar displays this:

"You are in TEXT MODE. Use the [<>] button to switch back to WYSIWYG."

Which isn't really correct.

Change History (6)

comment:1 Changed 15 years ago by Paul Baranowski <paul@…>

Note: This only happens when you select "Clean bad HTML from Microsoft Word".

comment:2 Changed 15 years ago by Paul Baranowski <paul@…>

Here's a fix for it:

File: /plugins/SuperClean/super-clean.js

Add the line "editor.updateToolbar()" in the location below:

  but.onclick = function()
  {
    f = frm;
    var elms = f.getElementsByTagName('input');
    cfg = { };
    for(var i = 0; i < elms.length; i++)
    {
      if(elms[i].getAttribute('type') == 'checkbox')
      {
        cfg[elms[i].getAttribute('name')] = elms[i].checked;
      }
    }

    editor._superClean(cfg, obj);
    editor._textArea.style.display = '';
    if(editor._editMode != modeWhenDone)
    {
      editor.setMode(modeWhenDone);
      editor.updateToolbar();
    }
    editor._superclean_on = false;
    frm.parentNode.removeChild(frm);
  }


comment:3 Changed 15 years ago by gogo

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in changeset:115

comment:4 Changed 15 years ago by niko

  • Resolution fixed deleted
  • Status changed from closed to reopened

i do still get the error!

additionally when i used the CharCounter? plugin the chars dissapear when entering the SuperClean?-dialog.

we should maby use inline-dialog.js

comment:5 Changed 15 years ago by gogo

niko: what error?

comment:6 Changed 15 years ago by niko

  • Resolution set to fixed
  • Status changed from reopened to closed

sorry, error is wrong, i meant i still get the message "You are in TEXT MODE..."

anyway, changeset:151 fixed it

Note: See TracTickets for help on using tickets.