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]: Google Chrome (v122) draws Patterns wrong #9638

Closed
7 tasks done
NamVTran opened this issue Jan 30, 2024 · 7 comments
Closed
7 tasks done

[Bug]: Google Chrome (v122) draws Patterns wrong #9638

NamVTran opened this issue Jan 30, 2024 · 7 comments

Comments

@NamVTran
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.0.0

In What environments are you experiencing the problem?

Chrome

Node Version (if applicable)

None

Link To Reproduction

http://fabricjs.com/patterns

Steps To Reproduce

Chrome version 122 draws rect Pattern of demo http://fabricjs.com/patterns wrong.
Likely relate to combination of translate, rotate, beginPath, closePath, and clip APIs of CanvasRenderingContext2d.
https://bugs.chromium.org/p/chromium/issues/detail?id=1520871#c3

Expected Behavior

In Chrome 121:
image

Actual Behavior

In Chrome 122:
image

Error Message & Stack Trace

No response

@ShaMan123
Copy link
Contributor

probably related to #9414

@NamVTran
Copy link
Author

probably related to #9414

Bug #9414 works well on Chrome 121 MacOS.

@asturur
Copy link
Member

asturur commented Jan 31, 2024

if you disable hardware acceleration for a moment, does it work?

@NamVTran
Copy link
Author

NamVTran commented Feb 5, 2024

if you disable hardware acceleration for a moment, does it work?

No, it still bug like that.

@ShaMan123
Copy link
Contributor

Our tests should pick this up if we run on the specified version I believe

@ShaMan123
Copy link
Contributor

maybe we should add a weekly trigger to test, not that it will give us anything actionable apart from the ability to file bugs in browser trackers

@NamVTran
Copy link
Author

NamVTran commented Feb 8, 2024

Cause this bug was fixed on the latest build of Chrome 122, so I close this issue now.

Thank you for your kind attentions.

image image

@NamVTran NamVTran closed this as completed Feb 8, 2024
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