[Interest] TextArea read-only non parity with Android

Nevala Samuel samuel.nevala at theqtcompany.com
Mon Dec 8 06:29:47 CET 2014

Can you write bud report to https://bugreports.qt-project.org about the TextArea issue on Android, please.

Senior Consultant | The Qt Company
The Qt Company Oy, Hatanpään valtatie 30, 33100 Tampere, Finland
​Email: samuel.nevala at theqtcompany.com | Mobile: +358 40 86 85 458
Qt Blog: http://blog.qt.digia.com/ | Twitter: @QtbyDigia, @Qtproject Facebook: www.facebook.com/qt​

From: interest-bounces+samuel.nevala=theqtcompany.com at qt-project.org <interest-bounces+samuel.nevala=theqtcompany.com at qt-project.org> on behalf of Jason H <jhihn at gmx.com>
Sent: Saturday, December 06, 2014 4:51 PM
To: interest at qt-project.org
Subject: [Interest] TextArea read-only non parity with Android

I have a TextArea { readOnly: true }. On Linux proper, this flag works as expected,. It can be scrolled but not changed, white background black text. On android, it is effectively "disabled" and CANNOT be scrolled, the appearance is gray background, dark gray text. I need something that works properly on Android and iOS. I came up with a Text in a Flickable, but the lack of feature parity is an issue.

Qt 5.3.0
Interest mailing list
Interest at qt-project.org

More information about the Interest mailing list