Hi Dylan, sorry for the delay Our experimental workaround was very short-lived and should no longer be active (https://bugzilla.mozilla.org/show_bug.cgi?id=1536898#c2). When I make a new profile, I can still reproduce this bug. I'm really not sure why, but in Chrome the smartlock.google.com is loaded directly, without re-routing through accounts.google.com. Quite mysterious. In any case, the fix to this should probably be clearing the disabled attribute independent of whether that script load successfully or not.
Bug 1531818 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Dylan, sorry for the delay Our experimental workaround was very short-lived and should no longer be active (https://bugzilla.mozilla.org/show_bug.cgi?id=1536898#c2). When I make a new profile, I can still reproduce this bug. I'm really not sure why, but in Chrome smartlock.google.com is loaded directly, without re-routing through accounts.google.com. Quite mysterious. In any case, the fix to this should probably be clearing the disabled attribute independent of whether that script load successfully or not.
Hi Dylan, sorry for the delay Our experimental workaround was very short-lived and should no longer be active (https://bugzilla.mozilla.org/show_bug.cgi?id=1536898#c2). When I make a new profile, I can still reproduce this bug. I'm really not sure why, but in Chrome smartlock.google.com is loaded directly, without re-routing through accounts.google.com. Quite mysterious. In any case, the fix to this should probably be clearing the disabled attribute independent of whether that script loaded successfully or not.