Android/ HT/ Ios

1. Android/ HT/ Ios 读取 png图片的限制：

  因为png图片能实现透明化，所以有些地方必须用到它。

 HT/ Android / Ios ：  2560 * 2048

2. Android / Ios 实现 图像扩大缩小， 不能按照预想实现动画效果：逐渐扩大，逐渐缩小。

3. While an animation created using webkit transitions is in progress, scale() transformations on non-animated objects are removed. This causes those objects to be scaled to their original sizes when any other object is animated.

Steps to reproduce:
- create several absolutely positioned elements and scale them using webkit transforms (e.g.: -webkit-transform: scale(2, 2);)
- animate one of them by setting its -webkit-transition properties and then changing its position

Please see the attached HTML file for details.

This happens on Android 2.2 only. Reproducible on HTC Desire and in emulator.

4. I encountered the same problem, to summarize :

 - works on Android 2.1 (Tests on HTC Desize 2.1, emulator)
 - no longer works from version 2.2 (Tests on HTC Desize 2.2, Samsung Galaxy S 2.2, emulator 2.2, emulator 2.3)
 - this concerns webkit transforms : "translate", "scale" and "rotate" works when used alone, but "translate scale" or "translate rotate" combinations fail when a transition occurs
 - also "translate3d" transformation doesn't work in combination with "scale" and "rotate" : only the "translate3d" is taken into account

The attachment allows to reproduce that and to see the two differents renderings, obtained between android 2.1 and android 2.2 : 
 - the green box is not scaled (translate3d + scale)
 - when you click on the blue box, the red box loses its scale (translate + scale + rotate) during the transition

I Would like to elaborate on the bug. 
First, it reproduces on Nexus One, w\ Android 2.3.3
Second, the bug occurs only when the transition is written where scale(A) comes after the translate(X,Y). when written in reverse order, this bug does not occur.

Second, this whole bug and writing should be avoided by using the matrix(x,y) syntax, but it is not supported by android at all at this point.

Third, I find people mistaking the phenomenon with a different bug, where during the animation the location of the transitioned element is incorrect if scale is also involved (even if scale not being animated)
I've setup a demo of this second issue here:
http://androidscalebug.appspot.com/

转载于:https://www.cnblogs.com/muzijia/archive/2012/11/23/2783894.html