Validate current support for Android 2.3

[vaadin-bot]

Originally by @mstahv

---

TouchKit 3-V7 combo seems to be hardly usable on slow Android devices. Client side rendering is so slow that even small UI's are practically unusable.

Also some screens probably throw client side exceptions (several empty screens in our test and demo apps).

Various component tests and tests apps should be systematically tried out with our older Android test devices and all issues should be identified so we can decide if it will be sane try supporting old Android devices.

---

Imported from https://dev.vaadin.com/ issue #11198

[vaadin-bot]

Originally by @zch

---

Some notes:

• Vaadin core seems to have problems giving components the correct height in android 2.x browsers
• NativeSelects (and probably password fields, perhaps other text fields) in NavigationManagers don't work. This is due to elements animated with translate3d(x,y,z) don't update the hit box correctly.

[vaadin-bot]

Originally by @zch

---

Just went through our demos and tests with the Galaxy Tab (Android 2.3.3) and here are my notes:

Vornitologist

• The map view is blank for some reason. Refreshing the view makes the map visible.
• The table in the observations view does not display correctly. Only the header is visible. Refreshing the browser makes everything visible again.
• The birds view is blank. Refreshing makes it visible.
  • Each drilldown needs to be refreshed to be visible
• pressing the + button on the observations view and then scrolling the add observation view causes the underlying view to flash through in the lower left corner
• only some strings are translated (not really an android thing)

MobileMail

• the reply icon looks weird
• the mailboxes popover content is too narrow while the popover background covers the entire window width
• The refresh button in the mailboxes popover looks weird
• refreshing while the mailboxes popover is open causes the popover contents to take the whole window
• The compose message view doesn't show the on-screen keyboard, but after a refresh it does
• when opening a mailbox (vmail) the refresh button is on top of the "< Mailboxes" button
• a newly opened mailbox (vmail) is empty (shows nothing, content height 0?) and refreshing goes back to the Mailboxes view
• Cancelling a message in the compose view leaves the on-screen keyboard open
• It was impossible to reach the message list and message views, so these are untested.

navigationmanager.SimpleTest

• blank screen (0 height component) navigationmanager.SimpleTestWithNavigationButtons
• blank screen (0 height component) oldtests.ButtonsInComponentGroups
• Renders too wide (button next to Up is cut off)
• Height of window wrong, cuts off at half height
  • corrects after toggling keyboard on/off
• scrolling causes hitboxes to move to the wrong places
  • scrolling a little and then pressing the button above the text field highlights the text field oldtests.ContextMenu
• everything renders, but nothing happens when touched in any kind of way oldtests.MoreButtonsInComponentGroups
• Renders too wide (button next to Up is cut off)
• Height of window wrong, cuts off at half height
  • corrects after toggling keyboard on/off
• scrolling causes hitboxes to move to the wrong places
  • scrolling a little and then pressing the button above the text field highlights the text field oldtests.NavigationManagerView
• renders too wide oldtests.NavPanelTest
• The buttons (back/forward) do nothing oldtests.NavPanelTestWithNavButtons
• Works, but navigation sometimes moves two screens at a time (e.g. clicking "nav view 1" on "nav view 0" moves from 0 to 2) oldtests.NavPanelTestWithViews
• The height of the window is wrong, cuts off half way oldtests.NavViewWithButtons
• The < and > buttons are placed below the header oldtests.PersonView
• Renders too wide oldtests.Selects
• The height is wrong oldtests.Tabsheet
• Renders too high == tabs not visible
• Renders too wide (visible on the last tab) DatePickerTEst
• Fallback datepicker:
  • The content of the VOverlay doesn't render until touched on an element inside it
  • TIME resolution: The keyboard overlaps the time field when editing it and it is impossible to scroll into view EmailFieldTest
• The keyboard layout doesn't change, but that's probably due to the lack of support for email fields in android 2.3 NavigationBarTest
• renders too wide NavigationViewBarTest
• navigating forward doesn't animate
• navigating backward from 4 goes all the way back to 1
  • Views 3 and 4 are empty
  • when navigating back to view 1, it is empty PopoverTest
• "Contains a NavigationManager":
  • Content disappears when navigating forward and back SwipeViewTest
• Scrolling is slow in the view with all the labels.
• The native select doesn't show the selected value TabBarTest
• First starting scrolling on "Tab 1" renders text on top of the scrolling text for a second, which makes it very messy TreeTableTest
• It's very hard to get the nodes to open, which makes it seem broken TreeTest
• I couldn't get the nodes to close, maybe it's possible, but it feels broken
• Renders half height VerticalComponentGroupTest
• The "Simple" button only reacts when touching the "Simple" label, not anywhere else

[vaadin-bot]

Originally by @mstahv

---

Some of our css rules seem to use just the unprefixed box-sizing rule. This might cause some of the issues:

http://caniuse.com/#search=box-sizing

[vaadin-bot]

Originally by @zch

---

New test results

General

• Having the KB open and then closing it seems to get the app stuck at the wrong height some times
• The browser sometimes crashes while rotating the screen
• After using different touchkit software for a while, the browser stops responding. A reboot helps.
• Sometimes the browser crashes

Vornitologist

- The map view is blank for some reason. Refreshing the view makes the map visible.
- keeps going offline
- only some strings are translated (not really an android thing)
- Too slow to be usable
- The chart over observations for the last 6h never got visible (too slow?)

MobileMail

• Showing the details for a message causes the "Mark as unread" link to overlap the subject label.
• After navigating between messages using the up/down buttons, the "Details" button/link cannot be hit any longer (sometimes)
• Sending a message doesn't dismiss the keyboard
• Cancelling a message in the compose view leaves the on-screen keyboard open
• Sometimes the compose view doesn't show the keyboard at all, not even a refresh seems to help any more

DatePickerTest

• Native mode is enabled by default (as support exists, although pretty unusable)
• TIME resolution in the fallback isn't themed yet

SimpleTestWithNavigationButtons

• Throws a class cast exception client side when navigating

ButtonsInComponentGroups & MoreButtonsInComponentGroups

• Could not scroll all the way down
• When rotating to landscape view, I could scroll (almost) all the way down and up
• Rotating back to portrait mode, I could scroll all the way down, but the NavigationBar disappears.
• scrolling causes hitboxes to move to the wrong places
  • scrolling a little and then pressing the button above the text field highlights the text field

ContextMenu

• nothing happens

NavigationManagerView

• I have to scroll to see the tabbar

NavViewWithButtons

• The < & > buttons drop down below the "No deco" label (partially overlapping the navigationbar and the content)
• The < & > buttons don't react to touches
• Touching where the < & > buttons ought to be triggers their click listeners

Selects

• Throws an exception

TabSheetTest

• Tab 4 ("Option"): Backward navigation dies at some point (e.g. first view -> test me -> test me -> me too -> me too -> back -> back no longer works)

PopoverTest

• Contains NavigationView: choosing something in the "nativeselect" causes the width of the popover to change and look strange
• No way to dismiss the popover when covering the entire viewport
• Contains NavigationManager: navigating forward causes the width of the popover to change and look strange

TabBarTest & TabBarInNavigationViewTest

• Tab 1 contains lots of labels with multiple ones on the same "row". On the desktop each label is on a row of its own

TreeTableTest

• Impossible to expand nodes

TreeTest

• Impossible to collapse (and probably expand) nodes

EmailFieldTest, UrlFieldTest

• No keyboard layout change (probably no support in Android 2.3)

[vaadin-bot]

Originally by @mstahv

---

Went through the issues list. Fixed some, ticketed and "wontfixed" some and can't fix (at least easily) these:

• The browser sometimes crashes while rotating the screen
• After using different touchkit software for a while, the browser stops responding. A reboot helps.
• Sometimes the browser crashes
• Too slow to be usable. Especially if one has used some better touch devices at some point. V7 client side optimisations could improve situation, but there is no way we can make ancient Android browsers/devices work as fast as ios or newer androids.
• Browser issues with keyboard:
  • Having the KB open and then closing it seems to get the app stuck at the wrong height some times
  • Examples from Mobile mail:
  • Virtual keyboard goes over the viewport -> text inputs/areas may be hidden below keyboard
  • Sending a message doesn't dismiss the keyboard automatically
  • Cancelling a message in the compose view leaves the on-screen keyboard open
  • Sometimes browsers gets to state where the virtual keyboard is no more showed at all. Repeatable in compose view. Not even a refresh seems to help any more. Solvable by focusing first the location bar and then back to browser area (tip from pro Android user).
• Tree is broken: core issue: #11566

Generally: Webapps can never be as good on Android 2 as in ios or new modern android devices. Android 2 "support" can't be made much better in TouchKit add-on itself, most significant enhancements could be done in V core. If rendering performance is not taken into account TouchKit 3 has better support for Android 2 than older versions. Our readme and product page should emphasis that one cannot expect equal UX on 99€ devices as on 700€ iPad.