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;
})();
Fusion
