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

Use translateX instead of translate3d #154

Merged
merged 1 commit into from
Jun 14, 2016

Conversation

MartinMoizard
Copy link
Contributor

Use translateX instead of translated3d to move the selection bar. This is preferable to avoid some bugs present in Chrome (such as https://bugs.chromium.org/p/chromium/issues/detail?id=449107).

@MartinMoizard
Copy link
Contributor Author

The tests failed due to a selenium issue. How to trigger them again?

@bicknellr bicknellr self-assigned this Apr 18, 2016
@bicknellr
Copy link
Contributor

Yeah, Selenium has been flaky recently. I've restarted them a couple times but it keeps failing... Anyways, this change shouldn't have any actual effect (famous last words). Is this a general workaround for the border-radius + transform issue? If so, you'll have made some iron-image users happy. :)

@MartinMoizard
Copy link
Contributor Author

MartinMoizard commented Apr 18, 2016

It solves the border-radius issue only when the selectionBar is not being animated.

@NicolasRannou
Copy link

up?

@bicknellr
Copy link
Contributor

Yeah, seems like this is just a problem with Firefox + our CI setup; we're working on this and it should be fixed soon. Anyways, this is a noop change that makes the code slightly cleaner, so I'll go ahead and merge it.

@bicknellr bicknellr merged commit cf354bb into PolymerElements:master Jun 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants