We have moved to a new Sailfish OS Forum. Please start new discussions there.
![]() | 1 | initial version | posted 2014-04-13 01:19:01 +0200 |
If you write a long string/message into the input field of the native Messageing app this message won't fit into the text area and will be overlapping the time and get under the keyboard after beeing in the third line until you type a space character or minimize the app to the homescreen [happened only two times while testing: or type a string of the length of two and a half lines].
![]() | 2 | No.2 Revision |
If you write a long string/message into the input field of the native Messageing app this message won't fit into the text area and will be overlapping the time and get under the keyboard after beeing in the third line until you type a space character or minimize the app to the homescreen [happened only two times while testing: or type a string of the length of two and a half lines].
Edit: Still not fixed on latest v. 1.1.1.27
![]() | 3 | No.3 Revision |
If you write a long string/message into the input field of the native Messageing app this message won't fit into the text area and will be overlapping the time and get under the keyboard after beeing in the third line until you type a space character or minimize the app to the homescreen [happened only two times while testing: or type a string of the length of two and a half lines].
Edit: Edit: Still not fixed on latest v. 1.1.1.27
Edit2: Still reproduceable on 1.1.9.28
![]() | 4 | No.4 Revision |
If you write a long string/message
The native messages application is unable to handle long strings and such long strings won't 'fit'
into the inputFirst I reported this issue with the Sailfish OS version 1.1.0.38 and I am still able to reproduce this on my Jolla 1 Phone running on Sailfish OS 2.0.5.6.
Type the following text into the
ThisIsJustALongStringForDemonstrationOfThisBug
Results:
A long string
will be.
) or adding a space characterEdit: Still not fixed on latest v. 1.1.1.27
Edit2: Still reproduceable on 1.1.9.28
The following screeenshot demonstrates this bug.