After I realized that the event.preventDefault() has been cancelled by the browser devs, along with all the relevant books and articles on the web, I stumbled upon a couple of three.js websites that have arrived to at least some decent workarounds - if not satisfying solutions.
My guess is that they provide an HTML layer and three.js is running in the background.
When the user zooms in or out, the three.js rendering is not affected, only the HTML elements are affected.
Am I right? Are there any further hints about that kind of workaround, or other solutions?
For example see:
On the following example the website also makes an actual controlled zooming on the scene.
BTW,
- Underestimating the developers’ ability to make a usable interface
- Canceling developers’ intelligent strategies and forcing a dumb “zoom on anything” approach
- Raw (dumb) image zooming in a 3D CGI environment that usually leads to either a decreased resolution, and a messed-up scene, or to an increased offscreen resolution that will consume the devices’ resources,
- Not taking into account the possibility of an accidental Ctrl+Wheel that will destroy the 3D scene and the user will end up being confused and disappointed, most likely not knowing how to fix it
Not very bright decisions by the browser-devs right?
It reminds me the era of HTML and JS browser wars -the era of horrible protocols, arbitrary decisions and unbelievable inconsistencies.