Hide Forgot
+++ This bug was initially created as a clone of Bug #724673 +++ securitylevel_name: Public All devices failed to activate and write text into RichTextArea element. Devices treated text area as uneditable space no different from surrounding page's background. On the other hand, element's toolbar seemed to work fine, buttons and select boxes are reacting correctly. (Simple TextArea element works without problems) Example tested on mobile devices: iPad, iPhone 4, Google Nexus S. --- Additional comment from oskutka on 2011-05-09 07:38:35 EDT --- Link: Added: This issue is incorporated by JBWFK-17 --- Additional comment from rebecca.jboss on 2011-05-23 02:03:36 EDT --- Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: iPad, iPhone 4, and Google Nexus S fail to activate and write text into RichTextArea element. The devices treated the text area as uneditable space. There are no reported problems with the element's toolbar, buttons, or select boxes. --- Additional comment from rnewton on 2012-03-09 01:07:14 EST --- Is this still relevant to WFK 2.0.0? --- Additional comment from kpiwko on 2012-03-15 11:34:51 EDT --- Pavol, can you verify if this is still present in WFK 2.0? I guess both RF 3.3 and 4.2 would be in place for verification. --- Additional comment from ppitonak on 2012-03-15 12:02:00 EDT --- This issue is not related to RichFaces.
Added RN text
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: iPad, iPhone 4, and Google Nexus S fail to activate and write text into RichTextArea element. The devices treated the text area as uneditable space. There are no reported problems with the element's toolbar, buttons, or select boxes.
Hi, WFK 2.0 has gone GA, can this bug now be closed? Thanks for your help, Isaac
I compiled the application with gwt-2.5 and the following issues have appeared: iPhone 4: The RichTextArea is still not responsive. Tapping on the screen in the text area does nothing. Buttons are resposive and works well but their functionality cannot be verified since I am not able to write anything. iPad: The RichTextArea *is* responsive and writing text is possible, however, I am not able to simulate picking different colors of background and foreground. When I tap on the button, menu with colors appears, color seems to be picked but text which is written afterwards has not changed its color properties. Google Nexus S: I am able to write something only when I do not pick any custom format of the text (buttons in the menu). When I pick some feature, e.g. bold text, I am not able to get virtual keyboard back after tapping on the screen. It is impossible to write into the text area afterwards. Please let me know if this can be marked as verified or any other steps are required in order to do so.
As the issue is still valid and we do not provide an GWT documentation, I'm bumping the issue to WFK 2.3.0, moving to ASSIGNED with updated RN verbiage and summary. We need to document this as a known issue.
Release note added, see https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/2.2/html-single/2.2.0_Release_Notes/index.html.
Moving state back to ASSIGNED. This issue was not fixed in WFK 2.2.0. Release note text is valid.
Migrated to JIRA
Marek Novotny <mnovotny> made a comment on jira WFK2-39 Clearing proposed Target Release value from 2.0.0.GA to Unknown
Rodney Russ <rruss> made a comment on jira WFK2-39 Move to Errai [~csa] [~jfuerth] ?
Jonathan Fuerth <jfuerth> made a comment on jira WFK2-39 This bug was filed against WFK's GWT component; although it affects Errai, it's not directly an Errai bug and it's not something we are likely to fix ourselves.