• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

Test Twizzle

For people having issues loading all the applets in this thread, I'd be curious how this page looks for you:
They all look fine. The 223 has a 221 square highlighted in a brighter color than the rest of the cubelets. Not sure if that is intentional.

(I reported earlier in the thread my problems viewing some of these applets in the OP.)

Oh, and I am using Chrome 93.0.4577.82.
 
This thread is fine for me on Firefox for Android.
This thread seems to crash the browser on mobile (tested Safari and Brave and both crash when opening this thread) - another user reported this as well.

Can def add more parameters or another tag. Let me know the suggestions and I'll add it.
 
  • Like
Reactions: qwr
I would like to discourage arguing about OS versions and such here.

cubing.js and Twizzle rely on somewhat recent web standards. We make sure to support the latest versions of all the major browsers, which will work on any OS that supports them. But if you're on an OS that does not support a current browser, we unfortunately can't offer full functionality.

However, accessibility is personally an important goal for me, and older browsers share similarities with situations where JavaScript can't run or the network is very slow. We have tested some workarounds for such situations (showing a static image, and/or a video animation), but they are not ready to use quite yet.
 
However, accessibility is personally an important goal for me, and older browsers share similarities with situations where JavaScript can't run or the network is very slow. We have tested some workarounds for such situations (showing a static image, and/or a video animation), but they are not ready to use quite yet.
Lucas, I appreciate your work and I did not complain. As mentioned above, I just gave feedback.

I have no problem at all, because there are programs for simulating cubes and solves working well on my machine.
 
I would like to discourage arguing about OS versions and such here.

cubing.js and Twizzle rely on somewhat recent web standards. We make sure to support the latest versions of all the major browsers, which will work on any OS that supports them. But if you're on an OS that does not support a current browser, we unfortunately can't offer full functionality.

However, accessibility is personally an important goal for me, and older browsers share similarities with situations where JavaScript can't run or the network is very slow. We have tested some workarounds for such situations (showing a static image, and/or a video animation), but they are not ready to use quite yet.
There exist many polyfills for newer EcmaScript features. However idk if the program uses WebGL and if there's an easy way around that.
 
There exist many polyfills for newer EcmaScript features. However idk if the program uses WebGL and if there's an easy way around that.

There's some nuance here.

Some browser APIs can definitely be polyfilled (although that can get expensive). However, language features generally *cannot* be polyfilled and some newer ones are not backwards-compatible enough to transpile for older browsers. We're going to be relying on more and more of those features — in particular, module workers are going to be really valuable for performance, debugging, and general maintainability.

I've spent a few hundred hours on compatibility issues already, and I'd like to avoid spending that much again. So I think I need to set the expectation that we will need to require reasonably up-to-date browsers for full functionality. That said, if you find particular compatibility issues you think are worth addressing, please do file an issue!
 
Just wanted to drop in here and let folks know that I haven't forgotten about this thread.

I've been trying to fix up some things to make the player work better in the forum and... let's just say the technical tradeoffs are significantly more difficult than you might expect.

However, you should now be able to load a large number of players on a page with reasonable (if not ideal) performance, and the player is now able to show error messages instead of blanking out for invalid input (although I'm still working on that).
 
Last edited:
Back
Top