Skip to content

CSS bug: short form of "transform: translate" is incorrectly applied #5202

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

Closed
sserdyuk opened this issue Dec 22, 2017 · 1 comment · Fixed by #9481
Closed

CSS bug: short form of "transform: translate" is incorrectly applied #5202

sserdyuk opened this issue Dec 22, 2017 · 1 comment · Fixed by #9481

Comments

@sserdyuk
Copy link

sserdyuk commented Dec 22, 2017

According mozilla, short notation translate(-50) can be used, and should applied as translate(-50, 0). NS incorrectly interprets it as translate(-50, -50).

I came across this issue due to how webpack and uglifier now rewrite CSS rules to shortest possible form, and it causes UI to break.

See related webpack ticket.

$ tns create cssTranslateTest --tsc
$ cd cssTranslateTest/
$ echo 'button.btn {transform: translate(-50);}' >> app/app.css
$ tns run android

image


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@NickIliev
Copy link
Contributor

Confirming this one as a bug - the short property for translate is not rendering the recommended result
Also related to NativeScript/nativescript-dev-webpack#377

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants