BMO and Tim Hortons sites Failures

General project discussion.
Use this as a last resort if your topic does not fit in any of the other boards but it still on-topic.
Forum rules
This General Discussion board is meant for topics that are still relevant to Pale Moon, web browsers, browser tech, UXP applications, and related, but don't have a more fitting board available.

Please stick to the relevance of this forum here, which focuses on everything around the Pale Moon project and its user community. "Random" subjects don't belong here, and should be posted in the Off-Topic board.
User avatar
davesnothere
Hobby Astronomer
Hobby Astronomer
Posts: 21
Joined: 2019-05-01, 12:23

BMO and Tim Hortons sites Failures

Unread post by davesnothere » 2022-10-18, 16:36

These two sites used to work in most of my browser installs including Pale Moon, but have been updated sometime this year, and now do not, except in FireFox 68 or higher, and I do not use non-Mozilla-based browsers.

https://www.bmo.com/main/personal

https://www.timhortons.ca

In the case of BMO, the main page is there, but when I try to log into their online banking [dropdown menu near top right of page : Login > Online Banking], the address bar of the browser indicates that I have reached the login page, but the content of the window becomes blank white instead of presenting a form for me to fill with my creds.

At the Tim Hortons site, same symptoms, with even the front page now only showing blank white as content, as of a few days ago.

Please can anyone shed light as to the underlying problem, and whether I can do anything to resolve it, other than using an alternate browser ?

We have tested and confirmed that this issue exists with Pale Moon 31 and several earlier versions.

Thanks.

User avatar
Wrolf
Hobby Astronomer
Hobby Astronomer
Posts: 28
Joined: 2022-05-25, 19:22

Re: BMO and Tim Hortons sites Failures

Unread post by Wrolf » 2022-10-18, 21:01

Hi. Quick look at BMO.

Console says:
Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.
(unknown)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://bankofmontreal.us-1.evergage.co ... _anon=true. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’).
(unknown)
And then:
TypeError: di.attachShadow is not a function
Stack trace: (and then a lot of stuff, among that a lot of polyfill stuff)
Is this of any help to you guys?

ps: I suppose this topic should be posted in "Web Compatibility Support" subforum?

cheers/Wrolf

User avatar
davesnothere
Hobby Astronomer
Hobby Astronomer
Posts: 21
Joined: 2019-05-01, 12:23

Re: BMO and Tim Hortons sites Failures

Unread post by davesnothere » 2022-10-18, 23:55

Wrolf wrote:
2022-10-18, 21:01
Hi. Quick look at BMO.

Console says:
Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.
(unknown)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://bankofmontreal.us-1.evergage.co ... _anon=true. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’).
(unknown)
And then:
TypeError: di.attachShadow is not a function
Stack trace: (and then a lot of stuff, among that a lot of polyfill stuff)
Is this of any help to you guys?

ps: I suppose this topic should be posted in "Web Compatibility Support" subforum?

cheers/Wrolf
It is beyond my full understanding, though I take it that the term 'deprecated' is a way of saying that an error occurred.

As for moving this topic to the subforum, maybe appropriate, but I posted it here because the topics about the GMX webmail site had remained here as long as they have, and I followed in their footsteps. ;)

User avatar
davesnothere
Hobby Astronomer
Hobby Astronomer
Posts: 21
Joined: 2019-05-01, 12:23

Re: BMO and Tim Hortons sites Failures

Unread post by davesnothere » 2022-10-19, 01:36

davesnothere wrote:
2022-10-18, 23:55
Wrolf wrote:
2022-10-18, 21:01
....ps: I suppose this topic should be posted in "Web Compatibility Support" subforum?
....As for moving this topic to the subforum, maybe appropriate, but I posted it here because the topics about the GMX webmail site had remained here as long as they have, and I followed in their footsteps. ;)
I have found and looked at the 'Web Compatibility Support' subforum, and agree that this topic should be there rather than here.

Is it possible to ask a Mod or Admin to move the topic ?

If yes, then please, I am asking.

Thanks. :)

User avatar
FranklinDM
Add-ons Team
Add-ons Team
Posts: 575
Joined: 2017-01-14, 02:40
Location: Philippines
Contact:

Re: BMO and Tim Hortons sites Failures

Unread post by FranklinDM » 2022-10-19, 08:43

I'm getting a different error. I'm assuming that this is the usage of global window event, but the sources are obfuscated so I can't say for sure:

Code: Select all

ReferenceError: event is not defined
Stack trace:
value/<@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64364
value@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64296
Us/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:95480
+wdc/t.unstable_runWithPriority@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:9:4099
fo@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:41868
Us@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:91559
Es@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:79160
uu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:105942
lu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:106017
yu/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107211
Hs@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:80693
yu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107197
render@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:110461
bSTp@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:376790
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
[0]@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:19802
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
a@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:430
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:1498
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:2
  
vendors.bundle.0b4dcd57502607113618.js:129:72336
ReferenceError: event is not defined
Stack trace:
value/<@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64364
value@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64296
Us/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:95480
+wdc/t.unstable_runWithPriority@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:9:4099
fo@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:41868
Us@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:91559
Es@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:79160
uu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:105942
lu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:106017
yu/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107211
Hs@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:80693
yu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107197
render@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:110461
bSTp@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:376790
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
[0]@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:19802
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
a@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:430
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:1498
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:2
  
vendors.bundle.0b4dcd57502607113618.js:129:72336
ReferenceError: event is not defined[Learn More]  
app.9153-20221018184123.js:1:64364
davesnothere wrote:
2022-10-18, 16:36
https://www.timhortons.ca

Code: Select all

ReferenceError: customElements is not defined vendor.788985a1.chunk.js:2:3669350
Likely Issue #1344 (UXP).

User avatar
Wrolf
Hobby Astronomer
Hobby Astronomer
Posts: 28
Joined: 2022-05-25, 19:22

Re: BMO and Tim Hortons sites Failures

Unread post by Wrolf » 2022-10-19, 09:47

davesnothere wrote:
2022-10-18, 23:55
I take it that the term 'deprecated' is a way of saying that an error occurred.
If a programming construct has been ruled "deprecated" it means that a standards building body has ruled that it is old and shouldn't be used anymore. Might be because of bugs, security risks, or whatever.
This, however, does not mean that people have to stop using it. Many happily go on using deprecated stuff, which sometimes leads to problems. :crazy: :mrgreen: :wave:

cheers!
/Wrolf

User avatar
davesnothere
Hobby Astronomer
Hobby Astronomer
Posts: 21
Joined: 2019-05-01, 12:23

Re: BMO and Tim Hortons sites Failures

Unread post by davesnothere » 2022-10-19, 17:03

FranklinDM wrote:
2022-10-19, 08:43
I'm getting a different error. I'm assuming that this is the usage of global window event, but the sources are obfuscated so I can't say for sure:

Code: Select all

ReferenceError: event is not defined
Stack trace:
value/<@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64364
value@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64296
Us/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:95480
+wdc/t.unstable_runWithPriority@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:9:4099
fo@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:41868
Us@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:91559
Es@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:79160
uu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:105942
lu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:106017
yu/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107211
Hs@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:80693
yu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107197
render@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:110461
bSTp@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:376790
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
[0]@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:19802
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
a@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:430
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:1498
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:2
  
vendors.bundle.0b4dcd57502607113618.js:129:72336
ReferenceError: event is not defined
Stack trace:
value/<@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64364
value@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:64296
Us/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:95480
+wdc/t.unstable_runWithPriority@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:9:4099
fo@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:41868
Us@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:91559
Es@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:79160
uu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:105942
lu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:106017
yu/<@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107211
Hs@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:80693
yu@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:107197
render@https://www.bmo.com/dist/scripts/vendors.bundle.0b4dcd57502607113618.js:129:110461
bSTp@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:376790
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
[0]@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:19802
i@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:556
a@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:430
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:1498
@https://www.bmo.com/dist/scripts/main/personal/app.9153-20221018184123.js:1:2
  
vendors.bundle.0b4dcd57502607113618.js:129:72336
ReferenceError: event is not defined[Learn More]  
app.9153-20221018184123.js:1:64364
davesnothere wrote:
2022-10-18, 16:36
https://www.timhortons.ca

Code: Select all

ReferenceError: customElements is not defined vendor.788985a1.chunk.js:2:3669350
Likely Issue #1344 (UXP).
I do not know whether both of these sites are failing for the same reason, but the ongoing lack of support of 'customElements' by Pale Moon is making it progressively harder for some of us to continue to use it as our primary browser.

I still like Pale moon for plenty of other reasons, but when websites which I use every day/week/month stop working because they chose to invoke this class of code [for example], it has forced me to use other browsers just to access an increasing number of those sites, even though I may dislike the UI of the other browsers, and/or cannot use certain extensions with them which I have grown to know, like, and trust over the years.

So I must ask the now notorious question :

Please, will Pale Moon be supporting 'customElements' any time soon ?

Last year, it seemed that it would not be, from what I read in other topics here at the time.

As time passes, more and more sites are being broken for Pale Moon [and its forks] because of the non-support.

Locked