ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2022 rebuild 3

[NotHereToPlayGames]

The problem is going to be in one of these scripts.

I can dig into it deeper over the weekend but I'd start with just blocking one at a time via uMatrix/uBlock and see if that restores website functionality.

[NotHereToPlayGames]

Could also be this script -

[NotHereToPlayGames]

Found the culprit.  It is this script - www.gwr.com/_next/static/chunks/main-a1ce463ca4bb7b12.js

Figures it had to be the "main" .js as the web site doesn't really "do" anything without it.

[Dave-H]

Thanks for the analysis!
What I'm seeing is this -

If I click on 'Go to the Home page' the page loads for an instant, and then goes back to the same error message.
Other parts of the site, such as the pages for booking tickets, still seem to work.

The problem with https://www.lner.co.uk/ is different, it's just not formatted properly, but I think this was a different problem.

If I go to the GWR site with Firefox 52.9, it does display, but completely mis-formatted too.

I guess these are unresolvable problems which will start to affect more and more sites as time goes on.
Whether it's due to the out of date Chromium version or JavaScript incompatibilities, it will only get worse.

[UCyborg]

Does no one read the console errors anymore? Object.hasOwn() is required, implemented since Chrome 93.

[Dave-H]

Thank you, that explains it.

[NotHereToPlayGames]

1 hour ago, UCyborg said:

Does no one read the console errors anymore? Object.hasOwn() is required, implemented since Chrome 93.

lol, a bad habit.  I generally jump straight to making a site "readable" and I can do that most of the time just by blocking scripts or letting a few in without letting all in.

I wonder of Object.hasOwn() can be injected the same way we inject structuredClone?

[UCyborg]

I don't know, it does exist on GitHub, but I'm not familiar with npm and whether compiling it would give an injectable version.

[NotHereToPlayGames]

This works at least in the case of https://www.gwr.com/

 

// ==UserScript==
// @name Inject Object.hasOwn Polyfill
// @version 0.0.1
// @match *://*/*
// @run-at document-start
// @grant none
// ==/UserScript==

if (!Object.hasOwn) {
  Object.defineProperty(Object, "hasOwn", {
    value: function (object, property) {
      if (object == null) {
        throw new TypeError("Cannot convert undefined or null to object")
      }
      return Object.prototype.hasOwnProperty.call(Object(object), property)
    },
    configurable: true,
    enumerable: false,
    writable: true
  })
}

 

Source:  https://github.com/tc39/proposal-accessible-object-hasownproperty/blob/main/polyfill.js

Another read:  https://stackoverflow.com/questions/69561596/object-hasown-vs-object-prototype-hasownproperty

Edited May 7 by NotHereToPlayGames

[Dave-H]

That's brilliant, thank you so much!