On 7/15/14, 1:06 PM, [email protected] wrote:
So if this comes down to terrible driver, what happens? Is that in
the hands of ZTE/Alcatel to fix, or what?
Usability suffers very much with this bug IMO.
At this point, all bugs are features; Hamachi is abandonware: neither
the manufacturer (not Alcatel, which is just a licensed name) nor
Mozilla are going to move the user experience forwards on the device.
ZTE might have a different policy.
The only way to code around this would be to write a touch handling
library which could handle bad input. It would have to either be robust
and unresponsive to problematic input or very smart and guess correctly
as to what is really going on when getting bad input. (This is where I
got stuck.)
Otherwise, we can wait until the hardware improves. (I'm working these
days with my web app bundled into an .apk and deployed onto a good
android device). For FirefoxOS, since the current plan is to race to the
price bottom, the majority of upcoming phones may have equally bad
hardware/drivers for multi-touch input so waiting for better hardware
might be a losing proposition---time will tell.
The easy solution for now is 'Don't rely on good multitouch input!' in
your apps. :~/
~adrian
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
