Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TIMOB-8930] MobileWeb: Ti.UI.View.rect not updated after animation #5375

Closed
wants to merge 1 commit into from
Closed

[TIMOB-8930] MobileWeb: Ti.UI.View.rect not updated after animation #5375

wants to merge 1 commit into from

Conversation

gstreetmedia
Copy link
Contributor

Needed to read and parse the current translation.

@@ -423,6 +423,7 @@ define(['Ti/_/declare', 'Ti/_/Evented', 'Ti/_/style', 'Ti/UI'], function(declare

promise.pause = function() {
var a = findAnimation();
updateRect(a.elem);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We notice updateRect() is called multiple times. Is there a reason it can't be called once?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do recall there being some reason for this. However, I made this modification over a year ago, so I'm not quite sure what the reason was. I know at least one reason was that KineticScroll views are completely broken without this fix. Stopping a scrollview mid scroll, lead to that scroll view reverting to it's original position.

Everytime I look at Animation.js I want to start from scratch, letting the browser (and thus the GPU) do all the heavy lifting. It seems like we could eliminate more than 50% of the code and get a huge performance boost by using CSS-based animation rather than tweening the transform property.

Does Appcelerator by chance maintain any kind of documentation regarding the inner workings of mobile web?

@ingo
Copy link
Contributor

ingo commented Mar 13, 2015

If you are still interested in this addition, please let us know and we'd be happy to work with you on updating it.

@hansemannn
Copy link
Collaborator

Closing this PR, since we couldn't get a response on the code review.

@hansemannn hansemannn closed this Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants