Ah, going to the JavaDocs I see that you are correct. I also notice this snippet here:
A rich text editor that allows complex styling and formatting. Because some browsers do not support rich text editing, and others support only a limited subset of functionality, there are two formatter interfaces, accessed via getBasicFormatter() and getExtendedFormatter (). A browser that does not support rich text editing at all will return null for both of these, while one that supports only the basic functionality will return null for the latter. I can try it (probably this weekend) to check for both formatters, and if both are null, switch the input to a text box. Obviosuly it'll only accept plain text, but it's better then it not working at all. On Nov 3, 6:12 pm, "pbyo...@gmail.com" <pbyo...@gmail.com> wrote: > I haven't tried this theory out yet, but having the same problem, I > surmise it is because the TextArea is a child of a FocusPanel, which > seems to behave differently in Safari, both on and off the iPhone. You > might fiddle with this and see if it is the problem. > > On Nov 2, 6:20 am, Sean <slough...@gmail.com> wrote: > > > So, I have a Text Area with the RichTextToolBar attached and when I > > click on the Text Area in IE, FF and Chrome everything works fine. > > > However, with the iPhone it doesn't seem to recognize it as a text > > input and doesn't bring up the keyboard. Is there anyway to fix that? > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
