Borked Chrome 64



  • Just updated Chrome to 64 and it is not happy about unresponsive.

    
    2unresponsive.js:378 Uncaught DOMException: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules
        at D (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:470765)
        at L (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:471567)
        at https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:471628
        at dispatch (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:46929)
        at g.handle (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:44850)
        at Object.trigger (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:76249)
        at https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:76882
        at Function.each (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:5718)
        at x.fn.init.each (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:4308)
        at x.fn.init.trigger (https://what.thedailywtf.com/assets/nodebb.min.js?v=dlc812ek17i:1:76858)
    

    It's this line:
    if(sheet!=null && sheet.cssRules != null && sheet.cssRules.length > 0){

    Yowza.



  • I disabled it, but chrome is still showing errors. Oh, and hangouts doesn't want to make calls any more because it doesn't have access to my microphone. "See the popup to correct." The popup is blank. undefined



  • Huh. Was the selector for "responsive" vs "desktop mode" taken out of the user-icon-menu thing? I just noticed that here at work, I don't have those options that I remember seeing people reference a while ago.

    0_1516909927895_ac992663-52cf-42f8-99ce-07f23cae2408-image.png



  • @e4tmyl33t Yes, I disabled the extension.



  • @boomzilla That would do it. I hadn't taken your last comment to mean "disabled server-side" for some reason, possibly because I just got off a conference call about user satisfaction surveys that made me want to hurt people.



  • @e4tmyl33t said in Borked Chrome 64:

    possibly because I just got off a conference call about user satisfaction surveys that made me want to hurt people.

    I'm on a similar call right now, though the subject is different.



  • @boomzilla is it the stylesheet with the fonts?



  • @ben_lubar Dunno. I didn't investigate too closely.



  • I don't understand this error:

    resize.js?v=1qfiupjdbfk:1 Uncaught TypeError: Cannot read property 'responsive' of null
        at resize.js?v=1qfiupjdbfk:1
        at Object.execCb (require.js:29)
        at w.check (require.js:18)
        at w.enable (require.js:23)
        at w.init (require.js:16)
        at h (require.js:13)
        at Object.completeLoad (require.js:28)
        at HTMLScriptElement.onScriptLoad (require.js:29)
    

    Which takes me to this bit of code:

    var n=!window.localStorage["unresponsive-settings"] || 
       JSON.parse(window.localStorage["unresponsive-settings"]).responsive?992:0
    

    undefined I disabled the extension and rebuilt (from the ACP) but unresponsive code is still sneaking in (and I had set my settings to null in the console before I did this).



  • @boomzilla That's in the composer, right? That part of the code is added by the Dockerfile.



  • @boomzilla I don't think the plugin ever sets the key to null, so try delete window.localStorage["unresponsive-settings"]



  • @ben_lubar Ah, right. That seems to have done it.

    @ben_lubar said in Borked Chrome 64:

    That's in the composer, right? That part of the code is added by the Dockerfile.

    Yes, it seems to be the composer. But...why would any references to unresponsive-settins be in the composer? Did we put something in there?Oh, I understand now.
    undefined


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.