The Atlantic doesn't display bottom of Web pages Topic is solved

[zzz242]

On the website The Atlantic, when stories are clicked on, the entire story is loaded. When you get to the bottom of the story, additional material is loaded. This material consists mostly of additional numbered, ranked stories from The Atlantic. In PM, this second load never happens.

For example, here is the output of the end of a story in PM:



Here is the end of the same story in another browser (Edge, in this case), after it has done the second load:



The display goes down to 10 stories, and then shows a useful site directory after that.

PM exhibited the proper behavior until sometime in the last few weeks or so; then it broke. Apparently The Atlantic changed something on their website.

Meanwhile, The Atlantic does not display many pictures (possibly most pictures) properly when using PM. For example, here's a picture from the story What Do Dogs Know About Us? displayed in PM:



And here's the same image displayed in Edge:



In the PM image, although the image itself is blank, all the standard right-click context menus are present and do the right thing. For example, if you click on "View Image" in the right click context menu, PM loads a page consisting of the proper image on a dark background.

Please note that The Atlantic is a subscription website that allows a few free articles per month. As a result, nonsubscribers have to be careful with the number of articles they load.

[Moonchild]

Please try and include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:

Clear any current output
Navigate or refresh the page in question
Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.

[zzz242]

When I load the page, before I even move to the bottom where the second load should occur, the following appears in the Web Console:

Code: Select all

SyntaxError: invalid regular expression flag s
Stack trace:
[90753]@https://cdn.theatlantic.com/_next/static/chunks/983-f9eed06655f9a546.js:1:8700
n@https://cdn.theatlantic.com/_next/static/chunks/webpack-8ed0c4d07996ce5a.js:1:144
[58787]@https://cdn.theatlantic.com/_next/static/chunks/983-f9eed06655f9a546.js:1:3584
n@https://cdn.theatlantic.com/_next/static/chunks/webpack-8ed0c4d07996ce5a.js:1:144
[64312]@https://cdn.theatlantic.com/_next/static/chunks/7985-0e9406a389809f2e.js:1:9154
n@https://cdn.theatlantic.com/_next/static/chunks/webpack-8ed0c4d07996ce5a.js:1:144
[88247]@https://cdn.theatlantic.com/_next/static/chunks/5670-7f8ae293bfed3a27.js:1:1084
n@https://cdn.theatlantic.com/_next/static/chunks/webpack-8ed0c4d07996ce5a.js:1:144
[76930]@https://cdn.theatlantic.com/_next/static/chunks/5670-7f8ae293bfed3a27.js:1:8497
n@https://cdn.theatlantic.com/_next/static/chunks/webpack-8ed0c4d07996ce5a.js:1:144
[70061]/<@https://cdn.theatlantic.com/_next/static/chunks/pages/%5Bchannel%5D/archive/%5B...article%5D-461bbeef6e66c7a7.js:1:183
onEntrypoint/<@https://cdn.theatlantic.com/_next/static/chunks/main-2233d15bfdc8156d.js:1:31020
  
main-2233d15bfdc8156d.js:1:17920
"A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred"  
main-2233d15bfdc8156d.js:1:17937
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://cdn.theatlantic.com/_next/static/css/6c5de8462a62fdeb.css. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).  
(unknown)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://cdn.theatlantic.com/_next/static/css/399907c1d27245b7.css. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).  
(unknown)
TypeError: NetworkError when attempting to fetch resource.  
(unknown)

And here is the output from the Error Console:

Code: Select all

Timestamp: 9/17/2022 8:06:35 PM
Error: TypeError: NetworkError when attempting to fetch resource.

The page I am attempting to load here contains no images, so these errors are likely related to the failure of the second load. The page in question is https://www.theatlantic.com/ideas/archi ... ar/671464/.

When attempting to load the web page I mentioned in my first message, which has an undisplayed picture, I get no additional error messages.

[Moonchild]

Hmm.. We did implement the dotall flag for regex (/s) so it's unclear why it throws an error here... I guess I'll have to look into that a bit deeper.
Of course it's a minified mess so I'm not sure what exactly the calling code is or what it's trying to do.

[Moonchild]

I figured out the issue (actually 2 of them). Filed as Issue #2008 (UXP).
It's funny that this implementation has been as-is in our regex parser for 3 years, but not reported to be problematic all this time

[zzz242]

I just wanted to say "Thanks!" for fixing this issue in the latest release of PM. It's really nice to see the entire pages on The Atlantic website display properly again.