Latest stable Google Chrome 68+, latest beta 69+ tested.
Open document and get a white blank page.
Chrome console throws an exception:
Uncaught TypeError: document.fullscreenEnabled is not a function at Object.get [as fullscreenEnabled] (fusion_web_bundle_20180809~171411.js:126) at new t (fusion_web_bundle_20180809~171411.js:126) at fusion_web_bundle_20180809~171411.js:126 at Object.<anonymous> (fusion_web_bundle_20180809~171411.js:126) at n (fusion_web_bundle_20180809~171411.js:1) at Object.<anonymous> (fusion_web_bundle_20180809~171411.js:126) at n (fusion_web_bundle_20180809~171411.js:1) at Object.<anonymous> (fusion_web_bundle_20180809~171411.js:65) at n (fusion_web_bundle_20180809~171411.js:1) at Object.<anonymous> (fusion_web_bundle_20180809~171411.js:65)
Works for me using 68.033440.106 on windows 8.1.
Mark
Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Yea, forgot to mention that I am using Ubuntu Linux. I'll check if it works on Windows in my case and investigate a bit more if it does.
Ok, so I was a bit wrong. It works in Chrome 68, but it does not work in Chrome 69.
I looked into Fusion 360 JS code, particularly fullscreen.js.
There is a method check:
// TBD: Opera, Microsoft support? if (document.body.requestFullscreen) { // This is the W3C's standard. As far as I know, nobody implements it // with this name.
This method (document.body.requestFullscreen) does not exist in Chrome 68 but it does exist in Chrome 69. So this check pass and there comes an issue.
Close by is a culprit code:
Object.defineProperty(fullscreenNative, 'fullscreenEnabled', { get: function() { return document.fullscreenEnabled(); }, enumerable: true });
That "return document.fullscreenEnabled();" is were it ends. There is no such method. Even if w3schools has defined it as an actual method (https://www.w3schools.com/jsref/met_document_fullscreenenabled.asp), it still does not exist. You can see at the same page on w3schools that they used it as a property in every example. Documentation error?
So that line of code should be "return document.fullscreenEnabled" and it will work.
Meanwhile I had to use a Tampermonkey script to undefine "document.body.requestFullscreen" before fullscreen.js kicks in and then next check of "document.body.webkitRequestFullscreen" method passes and everything works again.
Tampermonkey script for those Chrome beta users:
// ==UserScript== // @name Fusion 360 fullscreen bodge // @namespace http://veretenenko.ru/ // @version 0.1 // @description Fusion 360 fullscreen bodge // @author Anton Veretenenko // @match https://web.fusion.autodesk.com/* // @grant none // ==/UserScript== (function() { 'use strict'; console.log('Tampered!'); document.body.requestFullscreen = undefined; })();
Hi
Thank you for this detailed analysis.
I could not reproduce the issue.
I have done some smoke tests on
- Window 10, Chrome BETA 69.0.3497.57 : OK
- macOS Sierra, Chrome Canary 70.0.3535.0 : OK
On which OS are you facing this issue when creating a new design with Chrome Beta 69?
Thanks
Okay, thanks for clarifying.
We only support stable versions of Chrome but we keep close watch on this.
Regards
The issue is reproduced on MacOS with current google chrome Canary (71.0.3554.0).
We are working on it.
Thanks for sharing this information.
Hi
Web Fusion 360 should now work on all Chrome Browser (Stable, Beta, Canary).
Please let us know if you are still experiencing issues.
Regards
Hi
Web Fusion 360 should now work on all Chrome Browsers (Stable, Beta, Canary).
Please let us know if you are still experiencing issues.
Regards
Can't find what you're looking for? Ask the community or share your knowledge.