This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Format tools or Rich text editors do not work in Firefox

  • 8 antwoorde
  • 10 hierdie probleem
  • 124 views
  • Laaste antwoord deur Merl

more options

I use Win 7 64 bit and Firefox 16. Problem is that I, and some other users at the forum we belong to, can't use the Format tools or rich text editor to edit text.. For instance, when you type your text and want to change the format to bold etc. the editor gives a code like this:

[undefined=undefined]Found Thread[/undefined] Where it should be [b]Found Thread[/b] The word undefined pops up with all the formatting tools.

Using another browser like Chrome or IE the formatting or rich text editor works just fine. Like I said it's not just me that is having this problem, we are quite a few people on the forum that is having the same problem.

Any advise to solve this problem will be appreciated greatly.

Thanks in advance

Kind regards Mea Albrecht

I use Win 7 64 bit and Firefox 16. Problem is that I, and some other users at the forum we belong to, can't use the Format tools or rich text editor to edit text.. For instance, when you type your text and want to change the format to bold etc. the editor gives a code like this: <nowiki>[undefined=undefined]Found Thread[/undefined]</nowiki> Where it should be <nowiki>[b]Found Thread[/b]</nowiki> The word undefined pops up with all the formatting tools. Using another browser like Chrome or IE the formatting or rich text editor works just fine. Like I said it's not just me that is having this problem, we are quite a few people on the forum that is having the same problem. Any advise to solve this problem will be appreciated greatly. Thanks in advance Kind regards Mea Albrecht

Gewysig op deur cor-el

Gekose oplossing

"Due to a change in Firefox 16.1, when using the editor to insert MyCode you might encounter an issue where the tags are shown as [undefined=undefined]/undefined. This has been fixed in MyBB 1.6.9, but until we release it we have provided a patch for you to apply to your own boards."

http://community.mybb.com/thread-127983-post-926896.html?highlight=Firefox#pid926896

The fix is discussed here - http://community.mybb.com/thread-127322-post-922533.html#pid922533
An administrator of that forum can manually apply that fix, or just wait for the MyBB 1.6.9 update.

Lees dié antwoord in konteks 👍 4

All Replies (8)

more options

Firefox doesn't supports all the codes or this similar bbcode. This may be a bug, are you sure you're using the latest Mozilla client? Try out the beta with better performance or wait for a moderator to solve this problem issue. Thank you for the report. - John.

more options

Mozilla has a Rich Text Editor built into Firefox.
http://www-archive.mozilla.org/editor/midas-spec.html

One simple line of code on the web page enables it.
document.getElementById("edit").contentDocument.designMode="on";

more options

In a rich text editor HTML code (<b>TEXT</b>) should be used and not BBCode [b]TEXT[/b]

Do all visitors that use Firefox 16 have this issue?

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).

  • Do not click the Reset button on the Safe mode start window or otherwise make changes.
more options

None of the above helped :( Our forum uses MyCode, a simplified version of HTML. It was working just fine until about a week ago. 3 Other ladies have the same problem. All of us uses FF. When we use another browser like Chrome there is no problem with the formatting tools. If we type the code manually like this "[b]TEXT/b", while using FF it does format the text, but we want to be able to use the formatting tools and not do everything manually. I added a picture of the problem. Maybe it will help to identify the problem.

more options

Gekose oplossing

"Due to a change in Firefox 16.1, when using the editor to insert MyCode you might encounter an issue where the tags are shown as [undefined=undefined]/undefined. This has been fixed in MyBB 1.6.9, but until we release it we have provided a patch for you to apply to your own boards."

http://community.mybb.com/thread-127983-post-926896.html?highlight=Firefox#pid926896

The fix is discussed here - http://community.mybb.com/thread-127322-post-922533.html#pid922533
An administrator of that forum can manually apply that fix, or just wait for the MyBB 1.6.9 update.

more options

Thank you so much. It worked and everything is back to normal.

more options

I didn't have this problem with FF16 but I have a similar problem with 17. I support a web site running DotNetNuke 5.6.3, which includes its own Rich Text Editor. I've been able to edit using the wysiwyg editor for years. Today when I tried to edit a module, I had NO rich text editor although the Rich Text Editor button was checked. All I could see and edit was raw HTML. Suggestions for mybb.com etc. won't help because this site is written in ASP.NET.

I really prefer the FireFox interface but the more often you do things like this, the more time I have to get used to Chrome, which displays the editor just fine.

more options

I have the same problem with a forum which is a Web Wiz originally (though our admins re-coded a lot of things). After updating to Firefox 17, mine and several of our other members' rich text editor stopped working, even though the box was checked in our profiles. It works just fine in Chrome and IE, I checked.

I'm a content admin, not a code admin; does the fix proposed for FF 16 work on this FF 17 problem as well?