Daily Beast stories don't load

[lampshade]

Hi,

I've noticed that links to regular free stories on the Daily Beast don't load for me in Pale Moon.

For example this link loads in Firefox:

https://www.thedailybeast.com/when-it-w ... ived-in-it

But when I try to view it in Pale Moon it loads briefly, then resets to a blank white page. Is it just me? Thanks.

[Blacklab]

@lampshade: No, I don't think its just you... but it is an odd one... at least IMHO

Agree that with a 'normal' PM setup your link to 'thedailybeast' page (below) flickers open and then goes to a blank white page.
(that page is trying to load all sorts of things... 'Accept Cookies' opt-in, a Registration pop-up, an embedded YouTube clip, etc.)

Curiosity is that using the NoScript Addon to block 'thedailybeast' page's JavaScript (JS)... the page opens normally. (Blocking only the 'thedailybeast.com' script does the trick... no need to block anything else.)

(I appreciate NoScript is not an approved or favoured PM Addon due to its inherent 'website breaking' abilities... and breaking things is exactly what blocking JS is going to do most of the time... this being an unusual case! For me, I've used NoScript for years and am quite happy to play around with blocking/unblocking scripts on each page or site as required. You can always turn off NoScript on individual sites or everywhere with 'Allow Scripts Globally' switch if you want to see a page/site in its full unblocked glory )

Tried playing around with all manner of PM preferences and options but couldn't replicate what that simple NoScript block achieves...

...other than by the slightly crazed suggestion in this 2018 Mozilla Support Q&A: https://support.mozilla.org/gl/questions/1242031... which suggests the rather hit and miss method of clicking on your 'thedailybeast' page link (below)... then immediately hitting the 'Stop' button (the 'X') on the PM toolbar/urlbar... and if you get the timing right... the page opens!

I'm sure someone smart will know what's up!

[New Tobin Paradigm]

Mutters something about the Error Console...

Code: Select all

Timestamp: 7/3/2021 2:26:45 PM
Error: Error: TypeError: Network request failed
Source File: https://05f14972-530d-4235-a941-d79be44f229b.edge.permutive.app/05f14972-530d-4235-a941-d79be44f229b-web.js
Line: 1
Timestamp: 7/3/2021 2:26:46 PM
Error: TypeError: this.fetchQuery(...).finally is not a function
Source File: https://assets.thedailybeast.com/static/js/story.9f2903881bbeea2a8a30.js
Line: 1
Timestamp: 7/3/2021 2:26:49 PM
Error: XML Parsing Error: no root element found
Location: https://id.thedailybeast.com/?maxAge=2628000
Line Number 1, Column 1:
Source File: https://id.thedailybeast.com/?maxAge=2628000
Line: 1

[Blacklab]

Thanks... Nice... I think?

Er... scratches head... wonders if there might be a plain English translation for those unskilled in matters Error Console?

[Moonchild]

Seems fetchQuery() is part of the relay library/framework.
It should return a promise according to https://relay.dev/docs/api-reference/fetch-query/ if .toPromise() is used but they seem to strongly discourage that as async means data can be lost.

Not much we can do here.

[lampshade]

OK, thanks for looking into it Blacklab, New Tobin Paradigm, and Moonchild. Ultimately it's not super-important.

[vannilla]

You might still want to contact the site admins.
It might not be super important, but it will never be fixed if you don't tell them there's a problem.

[lampshade]

You might still want to contact the site admins.
It might not be super important, but it will never be fixed if you don't tell them there's a problem.

OK, email sent to DailyBeast tech support.