| Summary: | GWT: Unable to edit text inside of RichTextArea element on mobile devices | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | GWT | Assignee: | Petr Penicka <ppenicka> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Stefan Miklosovic <smikloso> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | jfuerth, misty, myarboro, oskutka, ppenicka |
| Target Milestone: | --- | ||
| Target Release: | 2.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBWFK-55 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Some iOS and Android devices treat RichTextArea as a read-only HTML element. Consequently, the devices fail to activate the RichTextArea and write text into it. The workaround is to avoid using RichTextArea elements in applications accessed by mobile devices. Other HTML elements are not affected by this issue.
|
Story Points: | --- |
| Clone Of: | JBWFK-55 | Environment: |
GWT 2.5.0
|
| Last Closed: | 2013-07-16 19:21:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 724673 | ||
| Bug Blocks: | |||
|
Description
Karel Piwko
2012-03-15 16:05:08 UTC
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. |