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

Strange Autolayout rendering #588

Closed
17 tasks
iurycarlos opened this issue Jun 2, 2023 · 3 comments · Fixed by #590
Closed
17 tasks

Strange Autolayout rendering #588

iurycarlos opened this issue Jun 2, 2023 · 3 comments · Fixed by #590
Labels
control/auto-layout kind/bug Something isn't working

Comments

@iurycarlos
Copy link
Contributor

Current behavior

With Uno.Toolkit 2.6.0-dev-68
This is the result for a Figma Plugin ListItem:

image

https://playgroundcanary.z19.web.core.windows.net/#d6391005
image

Expected behavior

However, with previous version, we have this:

image
https://playground.platform.uno/#0889c51d

How to reproduce it (as minimally and precisely as possible)

Just use the code at the playground links.

Nuget Package:

Package Version(s):

Affected platform(s):

  • WebAssembly
  • Android
  • iOS
  • macOS (AppKit)
  • Mac Catalyst
  • Skia
    • WPF
    • GTK (Linux)
    • Linux Framebuffer
    • Tizen
  • Windows

IDE:

  • Visual Studio 2022
  • Visual Studio 2019
  • Visual Studio Code
  • Visual Studio for Mac
  • Rider Windows
  • Rider macOS

Relevant plugins:

Anything else we need to know?

@iurycarlos iurycarlos added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification. labels Jun 2, 2023
@kazo0
Copy link
Contributor

kazo0 commented Jun 2, 2023

cc @carldebilly / @Robert-Louis

@kazo0 kazo0 added control/auto-layout and removed triage/untriaged Indicates an issue requires triaging or verification. labels Jun 2, 2023
@iurycarlos
Copy link
Contributor Author

iurycarlos commented Jun 5, 2023

Another interesting found:
As Agnes discovered, changing the Alignment from stretch to Auto results in a better view, it seams we have a deeper point:

Seams that the generated result has a different positioning for its content, comparing to the original version in Figma.
Probably something related to its Padding.
We can observe that at the following image:

image

So, since the available space for all content seams smaller than the original, we receive the cropped result.


Original, without optimizer:

image

@iurycarlos
Copy link
Contributor Author

iurycarlos commented Jun 5, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
control/auto-layout kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants