8000 translateX and translateY should accept Size Percentage as well as Size LengthUnit argument · Issue #218 · sebastiaanvisser/clay · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

translateX and translateY should accept Size Percentage as well as Size LengthUnit argument #218

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.

Sign up for GitHub

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

Jump to bottom
Open
ddssff opened this issue Jun 18, 2021 · 8 comments
Open

translateX and translateY should accept Size Percentage as well as Size LengthUnit argument #218

ddssff opened this issue Jun 18, 2021 · 8 comments

Comments

@ddssff
Copy link
Contributor
ddssff commented Jun 18, 2021 •
edited
Loading

Currently I have to say

transform $ translateX (other "-50%")
transform $ translateY (other "-50%")

On the other hand, transform $ translate (pct (- 50)) (pct (- 50)) works and is what you actually want, the two transforms above interfere with each other.
@hsyl20
Copy link
Contributor
hsyl20 commented Sep 7, 2023

+1 for this

@turion
Copy link
Collaborator
turion commented Jan 5, 2024

Currently I have to say

transform $ translateX (other "-50%")
transform $ translateY (other "-50%")

Instead of what do you have to say this?

@ddssff
Copy link
Contributor Author
ddssff commented Jan 5, 2024

I'm not sure I understand the question.

@turion
Copy link
Collaborator
turion commented Jan 5, 2024

You wrote "Currently I have to say", but I'm not sure what the problem with the code transform $ translateX (other "-50%") is. Is the problem that you have to use other instead of pct?

@ddssff
Copy link
Contributor Author
ddssff commented Jan 5, 2024

Yes that's it. other is unsafe.

@github-actions GitHub Actions
Copy link
github-actions bot commented Feb 9, 2025

This issue has not seen any activity in a long time. If no further activity occurs, it will be closed after ten weeks.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 20, 2025
@ddssff
Copy link
Contributor Author
ddssff commented Apr 21, 2025

Closing issues because they are old makes no sense to me.

@turion
Copy link
Collaborator
turion commented Apr 29, 2025

Fair enough. It's been closed though because there wasn't any activity for over a year. I'll assume you want this issue to stay open.

What we need to drive the issue forward is a concrete proposal how to change the API (bonus points for a sketch how to change the implementation).

@turion turion reopened this Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hsyl20 @turion @ddssff
0