-
Notifications
You must be signed in to change notification settings - Fork 387
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
Transformation via style attribute possibly causing performance issues in iOS #224
Comments
Have not had time to try, but perhaps try using translate3d with webkit to force hardware acceleration. See comments and code block on e1239d4 |
Hi @davidrapson Would be best to find a way to keep current functionality while providing good performance on all supported browsers. |
I'm pretty sure you're right, @davidrapson, that what you're seeing is the @bumbu, could the solution be as simple as detecting whether environment On Oct 23, 2016 4:23 AM, "bumbu" notifications@github.com wrote:
|
@bumbu Thanks, I'll try and pull together a jsfiddle within the next few days. |
Maybe instead of |
@bumbu is more familiar with this issue than I am, but the biggest thing is On Nov 10, 2016 1:05 AM, "Vidril César" notifications@github.com wrote:
|
By the way, it look like
|
@Yimiprod nice catch. Does it work like that in all supported browsers? |
Expected behaviour
Smooth panning on iOS
Actual behaviour
Noticeable lag when panning on iOS
Description
I've been experiencing some issues with performance when panning large SVGs in iOS since the switch to applying transforms via the style attribute
This issue sounds like it could be (possibly) related to #223.
Steps to reproduce the behaviour
3.2.7
and above panning becomes laggyConfiguration
3.2.9
Safari
iOS 10
Current Solution
I've currently resolved this by downgrading to
3.2.6
.It's worth noting that this is most noticeable for large SVGs so a possible solution could be a flag to opt-out of style attribute transforms.
Next steps
I can create a reduced test case to demonstrate this. Would you prefer that I close this issue and re-open when I'm able to provide a demo of the issue? Whatever is best for you.
The text was updated successfully, but these errors were encountered: