| Issue 1130: | Rich Text not working correctly in FF2.0.0.2 on linux | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Found in GWT Release: 1.4 RC1 Detailed description: Rich text is not working on my Fire Fox 2.0.0.1 on Fedora Core linux. The rich text control shows up, but you can not enter text (and selecting style options in the drop downs does not work either). Workaround if you have one: Don't use rich text. Links to the relevant GWT Developer Forum posts: N/A |
||||||||||||||
,
Jun 06, 2007
Issue 1126 also reported this vs. FF 2.0.0.3. I may have also seen what may be something similar on FF 2.0.0.4 on OS X. (The app, if you want the code, was the GWTNote sample app in the gwt-google-apis project.)
Owner: gwt.team.jgw
Labels: -Priority-Medium Priority-Critical Category-UI Milestone-1_4_RC2 |
|||||||||||||||
,
Jun 12, 2007
(No comment was entered for this change.)
Status: Accepted
|
|||||||||||||||
,
Jul 17, 2007
I've seen intermittent timing issues on RichTextArea initialization on Gecko-based
browsers. It appears that the setTimeout({}, 1) trick is not sufficient to get the
iframe into a good state.
Status: Started
|
|||||||||||||||
,
Jul 24, 2007
It turned out that all the advice that I could find on the web for initializing
designMode on a dynamic iframe was, well, *wrong*. Everything I've been able to find
suggests using setTimeout({1 | 10 | 100}). When people tell you to 'increase the
timeout and it should work', be afraid. Be very afraid.
In the end, I found a Mozilla-specific solution that uses the iframe's onload event
to set designMode, which appears to be much more reliable (and makes a lot more sense).
Status: ReviewPending
|
|||||||||||||||
,
Aug 13, 2007
Fix committed as r1305.
Status: FixedNotReleased
|
|||||||||||||||
,
Aug 20, 2007
1.4 RC2 now released.
Status: Fixed
|
|||||||||||||||
|
,
Apr 28, 2008
Owner: jgw
|
|||||||||||||||
 Sign in to add a comment
|
|||||||||||||||