If you recently upgraded to a Windows 10 computer, then it might be that the video driver isn't supported and you might need to upgrade your driver.
Otherwise consider following these checks: http://superuser.com/questions/836832/how-can-i-enable-webgl-in-my-browser

I have found that at least one other has the same problem:

https://productforums.google.com/forum/#!topic/chrome/XIy6dtJY4uo

Hello.
I might not be able to do too much for this one. Besides I don't have access to any computers with windows 10.
Are other websites using webgl not working either?

I've just tested on my laptop with the last updates for windows 10 installed and with Chrome v54.0.2840.59 m and there isn't any compatibility issues.
Did you try the solutions suggested by Sim?

Unfortunately Sim's link doesn't contain any suggestions that fix the problem - I have tried them all.

As I wrote in the Google Forum thread, I'm out of ideas. Fortunately, WebGL still works in FIrefox, so I'll stick to that browser instead of Chrome. Thanks for your input.

You're not alone with the bug. I've watched the bug board of google chrome and it's been reported. Hopefully it gets fixed soon.

Thanks, Sim. Do you have a link so I can follow development as well? 😄

https://bugs.chromium.org/p/chromium/issues/detail?id=653135
I'm not entirely sure that this will be your issue as well, but it really looks like to be this.

Thanks. This was exactly what I needed, because now I found logs in about:gpu that may be usable to fix the bug.

It would be nice to identify the gpu concerned by this bug.
Hopefully this bug will be fixed in the next release.
Maybe you could use temporarily a previous version of Chrome Portable.

If anyone else has this problem, the current workaround is to start Chrome from a command prompt with this option:

chrome.exe --disable_chromium_framebuffer_multisample

or creating a shortcut with this option added.

Thanks for your feedback.

The forum seems to remove all backslashes. That can't be right.

Use the code tag to put code stuff in the forum to ensure it is not parsed.
code here...

This is happening to me on mac osx with the lastest couple of chrome releases... the latest being 55.0.2883.95. I hope it resolved soon.

The bug I was experiencing was a DirectX related problem, so it relates to Microsoft Windows only. So if you're experiencing problems with WebGL on MacOS, you'll need to file a bug report or wait for others to report it.

I updated Chrome for MacOs (10.10) and everything is still working fine.

I'm now experiencing the same issue (except on a Mac) except not only with Chrome, but Firefox and Safari as well. Firefox doesn't even give the warning message, it simply will not load the workshop (or the models in the library). If anyone knows of a fix for this I'd be thankful. 😃

Nothing has changed.
On which system/browser doesn't it work?
Workshop is now coded using ECMASript6 so your browser has to be a little bit recent. However it has been the case for the past 2 months.