Discuss and evaluate feedback coming from the Florence removal
Pablo wrote somewhere else (#14675-note_16):
But I think the important points for accessibility are:
# The user’s ability to keep the keyboard visible at any time not only in programs and specific times.
# Ability to place and move the keyboard at any location on the screen as in Florence using a button.
# Ability to adjust the keyboard size.
# (Dispensable point but I think important) a beautiful keyboard not with old-looking buttons.As a user I prefer option 1. (I’m sorry for your sadness Intrigeri)
Follow my personal reasons for use. I few times use the tails on a computer 2 in 1 (HP Pavillion), ie sometimes I double the screen and use the tails as a “tablet”, something that brings a bad experience But that worked since using with mouse and touch, and then with the end of the keyboard Florence I can not have any autonomy, for example I had before, trying to enter an address in the browser or a simple search, did this using the virtual keyboard (Florence) and the mouse , and just now I can’t do it anymore because the keyboard doesn’t show up at all the locations I want, it appeared to me just in the text editors, well another change and now I can no longer put the keyboard in place of the screen where I want , it (when it pops up) just gets stuck down by occupying the entire screen at the bottom, in the spaces of the sidelines totally useless and paralyzed, well the improvement was design, because on the keyboard Florence, was in a very “old” way, anyway, the functionality of having the virtual keyboard in Time and place of the screen I want was important, because so I could use, although in a rustic way to combine Florence-mouse-touch of the tails, the keyboard property and not always available does not seem to be accessible.
Subtasks
Related issues
- Related to #8281 (closed)
- Related to #16182 (closed)
Original created by @intrigeri on 14713 (Redmine)