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

[Bug]: Ellipse stroke gets clipped #9409

Closed
7 tasks done
Nosferatu31 opened this issue Oct 11, 2023 · 8 comments
Closed
7 tasks done

[Bug]: Ellipse stroke gets clipped #9409

Nosferatu31 opened this issue Oct 11, 2023 · 8 comments

Comments

@Nosferatu31
Copy link

CheckList

  • I agree to follow this project's Code of Conduct
  • I have read and followed the Contributing Guide
  • I have read and followed the Issue Tracker Guide
  • I have searched and referenced existing issues and discussions
  • I am filing a BUG report.
  • I have managed to reproduce the bug after upgrading to the latest version
  • I have created an accurate and minimal reproduction

Version

5.3.0

In What environments are you experiencing the problem?

Firefox

Node Version (if applicable)

16.14.2

Link To Reproduction

https://codesandbox.io/p/sandbox/fabric-nextjs-sandbox-forked-r6zrsd?file=%2Fpages%2Findex.tsx%3A19%2C23

Steps To Reproduce

  1. Create a very large ellipse with a very large stroke

Expected Behavior

The ellipse stroke is not clipped on the render

Actual Behavior

  1. Ellipse stroke/border gets clipped on the first render
  2. Ellipse stroke/border gets fixed after scaling horizontally or vertically
  3. Diagonal scaling does not fix its border

Error Message & Stack Trace

No response

@Nosferatu31
Copy link
Author

Expected ellipse:
image

Actual ellipse (check right-side border/stroke):
image

@ShaMan123
Copy link
Contributor

I did not manage to reproduce on firefox 117.0.1 for windowns 64-bit
looks like something on their side
closing for now - If you disagree keep the thread alive

@ShaMan123
Copy link
Contributor

a very good ticket BTW, thanks

@Nosferatu31
Copy link
Author

I'll add that the "bug" appears on Firefox + Ubuntu but it does not on Chrome + Ubuntu.
@ShaMan123 Thank you for your response, and yes, the issue may be closed 😃

@ShaMan123
Copy link
Contributor

I recommend you report it to them

@ShaMan123
Copy link
Contributor

I also wonder if playwright tests will show this

@ShaMan123
Copy link
Contributor

I can create a test and see what ci produces, it runs on ubuntu chromium. I will try to add firefox and mention you

@asturur
Copy link
Member

asturur commented Oct 26, 2023

Does it change anything by disabling or enabling hardware acceleration on the affected browser?
Also what is the hardware that this computer has?
(videocard model/vendor/generation)

ShaMan123 pushed a commit that referenced this issue Oct 26, 2023
Update CHANGELOG.md

Merge branch 'master' into test-#9409
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants