Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

TinyMCE

  • 4 отговора
  • 56 имат този проблем
  • 41 изгледи
  • Последен отговор от cor-el

more options

We use TinyMCE to provide content editing on clients websites and since Firefox Version 11.0 installed today the content in the textarea fields managed by TinyMCE does not display however when you click the TinyMCE HTML icon it shows the source of the field is still there. When the textarea is resized then the content is displayed but if one leaves the page and returns to it, it once again does not display. This problem occurs on every website we have which uses TinyMCE as the content editor.

We use TinyMCE to provide content editing on clients websites and since Firefox Version 11.0 installed today the content in the textarea fields managed by TinyMCE does not display however when you click the TinyMCE HTML icon it shows the source of the field is still there. When the textarea is resized then the content is displayed but if one leaves the page and returns to it, it once again does not display. This problem occurs on every website we have which uses TinyMCE as the content editor.

Избрано решение

You need to update to the latest TinyMCE. This is a known bug in Firefox 11 and should be fixed in Firefox 12 but it only happens with older versions of TinyMCE (as far as we know). See this forum post from the TinyMCE forums.

Прочетете този отговор в контекста 👍 3

Всички отговори (4)

more options

Избрано решение

You need to update to the latest TinyMCE. This is a known bug in Firefox 11 and should be fixed in Firefox 12 but it only happens with older versions of TinyMCE (as far as we know). See this forum post from the TinyMCE forums.

more options

TinyMCE, Version 3.5b2, now works fine. We upgraded to the latest TinyMCE, Version 3.5b2, right after raising this issue however we found that although it fixed the display (not consistently though), the HTML icon did not show the source of the textarea. This however is now working although the About Firefox still says we are on Version 11.0 so I can only guess that something has changed. We tested this through rebooting machines in case of caching but the issues remained.

We have recommended using Firefox to our clients for many years because of the reliability and conformance to browser development standards, unlike some other browsers, however I am surprised that going from Firefox version 10 to version 11 has caused this problem and in order to get around it we have to upgrade TinyMCE when TinyMCE version 3.4b2 which we had works perfectly on all other browsers we tried. The first step being to recommend clients use a different browser while we try and resolve the issue.

The impact of this is not insignificant because we have had to urgently upgrade TinyMCE on all of our client websites, the client interaction we have had to go though, and in the interim clients have been unable to use their systems in the normal way. Can Firefox introduce into their testing / quality control process a system set up to use TinyMCE versions because there are so many users of this product worldwide? Is there a beta process where Firefox can get software suppliers of the nature of TinyMCE to test their systems before releasing a new version?

more options

Saying "you need to upgrade TinyMCE is unrealistic. In our case, it's a service we use, not own. Welcome to the cloud. Since Chrome, Safari, and IE all can work with the multiple versions of TinyMCE, why can't Firefox? Thank goodness for Mac OS X's Time Machine; I'm back on FF9 and sticking with it; it works with both TinyMCE and our Java applets, unlike FF10 and FF11.

more options