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.

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

bug: inner shadow is on top of frame border, despite "Clip Content" being on #5058

Closed
rangelovd opened this issue Sep 4, 2024 · 2 comments · Fixed by #5157
Closed

bug: inner shadow is on top of frame border, despite "Clip Content" being on #5058

rangelovd opened this issue Sep 4, 2024 · 2 comments · Fixed by #5157
Assignees
@Alotor
Labels
bug managed on taiga This issue has been moved to our project at Taiga.io
Milestone
2.3.0

Comments

@rangelovd
Copy link

rangelovd commented Sep 4, 2024 •
edited
Loading

Steps To Reproduce

Steps to reproduce the behavior:

  1. Create a frame
  2. Add Border (inner)
  3. Add Inner Shadow (0% blur, 2px Y, 0% Spread, 100% transparency)

Expected behavior

Inner Shadow is behind the border

Actual behavior

Inner Shadow is on top of the border

Screenshots or video

image

Also notice how shadow on the right is growing incorrectly, though this is another bug

Desktop (please complete the following information)

Windows 10, Google Chrome

Smartphone (please complete the following information)

No response

Environment (please complete the following information)

design.penpot.app

Frontend Stack Trace

No response

Backend Stack Trace

No response

Additional context

Figma shows inner shadows on top if content is not clipped, and behind if it's cilpped.
@rangelovd rangelovd added the bug label Sep 4, 2024
@rangelovd
Copy link
Author

image
image

This is the element I want to create. If the behavior is expected, please share how should this be achieved.

@myfunnyandy myfunnyandy added the managed on taiga This issue has been moved to our project at Taiga.io label Sep 6, 2024
@madalenapmelo-kp
Copy link
Contributor

Hi @rangelovd,

Thanks for reporting this! We've added this to our backlog on Taiga so that we can look further into it, you can find the details here: https://tree.taiga.io/project/penpot/issue/8700

@Alotor Alotor self-assigned this Oct 9, 2024
@Alotor Alotor added this to the 2.3.0 milestone Oct 9, 2024
@Alotor Alotor mentioned this issue Oct 10, 2024
Merged
@Alotor Alotor linked a pull request Oct 11, 2024 that will close this issue
Alotor bugfixing 2 #5157
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Alotor Alotor

Labels
bug managed on taiga This issue has been moved to our project at Taiga.io
Projects
None yet
Milestone
2.3.0
Development

Successfully merging a pull request may close this issue.

Alotor bugfixing 2 penpot/penpot
4 participants
@myfunnyandy @Alotor @rangelovd @madalenapmelo-kp