[Bug]: Google Chrome (v118) no longer supports Pattern features

[xiaowangsmile]

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?

Chrome

Node Version (if applicable)

None

Link To Reproduction

http://fabricjs.com/patterns

Steps To Reproduce

The new version of Google Chrome (v118) no longer supports the Patterns feature, and the demos on the official website are no longer viewable properly.
http://fabricjs.com/patterns

Expected Behavior

Actual Behavior

Error Message & Stack Trace

No response

[asturur]

Do you have a link to a changelog? could be a temporary bug as many others

[laurentdiazfr]

I have the same issue on several Windows machines using the latest Chrome.

I have found a bug report about this :
https://bugs.chromium.org/p/chromium/issues/detail?id=1480200&q=canvas%20pattern&can=2

[ShaMan123]

maybe we should pin this

[carior]

not support version

[asturur]

pinned

[carior]

Enter in the problematic browser chrome://flags/ Or edge://flags/
Then search for Accelerated 2D canvas, set it to disabled, restart it, and give it a try.
https://stackoverflow.com/questions/73585046/mac-m1-processor-chrome-browser-v105-inconsistent-html5-canvas-element

[carior]

[rafipatel93]

same problem my website

[salehfasih]

Same problem on my website.

[sk65cool]

willReadFrequently: true dosent work in Chrome Version 119.0.6045.106
Is there another way to make Text with a pattern fill appear?

[sjoerdvanBommel]

This issue appeared for me as well, but is resolved now, maybe because I've upgraded to Chrome v119? :) It occurred on v118.

[Tomasgb97]

is there a solution for this yet, or it has been completely relegated as a chrome issue?