PDA

View Full Version : Known Issues 0.92



Jamie Avins
16 May 2010, 12:50 PM
Form entry on Android does not operate correctly. Element positions are not reported correctly back to the OS and leads to unexpected behaviors.

The API for Sortable list views will change before release. If you are using this API heavily, you should anticipate that your code will break with each beta update.

Picker API and behavior will change before release. At the moment it's possible to give it parameters that result in incorrect behavior.

The Maps and Carousel components both respond to swipe events resulting in a carousel transition and a map drag at the same time. These will be disambiguated in the final release.

While HTML5 video and audio operate correctly in basic use, when HTML5 video is combined with touch events or transitions, there is a likelihood of browser crashes. These are known WebKit issues.

The video component on Android works correctly only with Google sourced videos (YouTube etc.). This appears to be an issue with Android video decoding.

Maps have occasional rendering issues.

Swappable list headers are hidden during fast scrolls. This will be changed for final release.

Android occasionally drops the initial drag event for draggable components.

Fields in toolbar require restyling.

watrboy00
22 Jun 2010, 1:00 PM
Jamie - Is this thread going to be updated as each release comes out? Or would the change log be a better place for that?

Jamie Avins
22 Jun 2010, 1:23 PM
We plan on including it in both the distribution and on the forum.

srininara
1 Jul 2010, 12:48 AM
The form entry on Android issue - Is it something which is going to get fixed soon? Or is it a problem with the underlying browser? Any reasons for why such behavior is happening? Please let us know.

Thanks,

Best Regards,
Srini


Form entry on Android does not operate correctly. Element positions are not reported correctly back to the OS and leads to unexpected behaviors.

The API for Sortable list views will change before release. If you are using this API heavily, you should anticipate that your code will break with each beta update.

Nested Lists are not based on the List component in beta, but will be for final Release.

Picker API and behavior will change before release. At the moment it's possible to give it parameters that result in incorrect behavior.

The Maps and Carousel components both respond to swipe events resulting in a carousel transition and a map drag at the same time. These will be disambiguated in the final release.

While HTML5 video and audio operate correctly in basic use, when HTML5 video is combined with touch events or transitions, there is a likelihood of browser crashes. These are known WebKit issues.

The video component on Android works correctly only with Google sourced videos (YouTube etc.). This appears to be an issue with Android video decoding.

Maps have occasional rendering issues.

Swappable list headers are hidden during fast scrolls. This will be changed for final release.

Android occasionally drops the initial drag event for draggable components.

Fields in toolbar require restyling.

TommyMaintz
1 Jul 2010, 11:26 AM
Getting the forms to work on Android is very high on our priority list. Actually we are working on it right now. It is an underlying issue with the browser. Unfortunately form controls on all mobile browsers are quite unstable. The reason is that every device uses it's native form controls and bridges them to webkit. By doing so they introduce many bugs. (This is the case with both iOS and Android).

On Android there is one major issue though. It seems that in some weird cases a webkit transform on the page (in our case there are many), it somehow affects the location of all form controls. The location that they are shown is still correct, but if you try to focus them you have to tap above or below the actual field.

stranded
2 Jul 2010, 1:34 AM
Hi,

Testing the example http://www.sencha.com/deploy/touch/examples/nestedlist/ on iPhone then on Andoid yield different result when it comes to scrolling. (Yes, I know that the list is not long enough to warrant scrolling .. i'll get to that) On the iPhone you get the bouncy scroll as expected. What promted me to test this example on both is that my own app used this example as a baseline. It works flawlessly on iPhone, with a long list while does not want to scroll on Android. On Android you DO get the scrollbar indicator on the right edge, but no actual scrolling.

Android spec
Model: HTC Hero
Firm ware: 1.5
Software version: 1.0.0.A6288
Kernel version: 2.6.27

Is this a know issue or something I might have done or not done?

Cheers,
Tommy

onlinedegree
2 Jul 2010, 7:15 AM
I am having the similar problem as Stranded has...Please give your feedback with the solution.

TommyMaintz
2 Jul 2010, 12:06 PM
Well, one thing we do (for performance reasons) is to turn off bouncing on Android devices. So if the list is not long enough to be scrolled, it wont scroll at all.

Do lists that are long enough to be scrolled not scroll either? If so, could you provide us with source code or point us to the example that has this behavior? Also, does the HTC Hero run Android 2+?

stranded
3 Jul 2010, 12:59 AM
The Andoid runs on 1.5 and I plan to keep it on 1.5 for now. An Android version 2.x is in the works, probably arrive this week so we can test on multiple versions.

Example examples/list/index.html has the same issue. Works well on iOS 4 Safari Mobile and Safari but on Android 1.5 it does not scroll. Even the index does not work. Touching it makes it dark as on the iPhone, but no letter is selected and the list does not jump to the touched letter.

My source deviate little from this example in regards to the scrolling of lists.

TommyMaintz
5 Jul 2010, 1:38 PM
Unfortunately Android 1.5 lacks the support for some features that we need in order to get the library to work properly. Thats why we only support Android 2+.

stranded
5 Jul 2010, 2:19 PM
Ok. Atleast I know that it it is not supposed to work =) .. It is easier that way to be able to write it off and then to move on with other issues..

Jamie Avins
26 Jul 2010, 4:06 PM
The download links should be set up shortly. Quick note: someone forgot to update the Ext.version to .92 in this release. We'll try to make sure it's updated next time.

timsMyth
28 Jul 2010, 8:27 AM
version numbers in ext-touch.js don't seem to have been updated from 0.9.1