New Problem With restoreprivacy.com

[van p]

This problem appeared in the last 2-3 days.

Chredge displays the top of the home page correctly:

Edge Capture.PNG

Pale Moon now looks like this:

Pale Moon Capture.png

Web Console shows nothing.

Browser Console shows:

Screenshot (84).png

Error Console shows:

Screenshot (85).png

Expanding Error Console shows:

Screenshot (86).png

Screenshot (87).png

Wassup?

[Moonchild]

Your errors point at a problem in the OpenDownload extension. try disabling that.

[van p]

After restarting the browser, no effect. Same with the other 2 browsers I use. Actually, the top half of the page is different. Normally, there's some text and graphics right below the banner I show, then, below that, there are 6 graphics with underlying text spread across the page in 2 rows. Now, they're all down the left side of the page, one below the other. You're the expert, but I don't see how a small program that's not even in use at the time could have an effect on anything.

I will attempt to contact the site owner and see if he made any change recently.

[moonbat]

I don't see

Exactly, you don't see and just post about it. If you did actually see what the error messages are, you would note that they originate in a javascript file that is part of your extension as can plainly be seen in the error console right below the error message. If you're going to take the trouble of documenting the error, at least read it properly, and test your broken website on a separate factory fresh profile before reporting it as a browser problem. You've been around here long enough to know that's what you do first.

[van p]

moonbat, I don't know javascript from yo mama. I just know that the "consoles" are mentioned sometimes in the forum; I'll let those more knowledgeable than myself, such as, apparently, you interpret what they see there. I did mention in a follow-up post that 2 other browsers were affected also, so it's not likely anything related to my Pale Moon profile. The fact they affect 3 Firefox-related browsers and not Chromium might tell somebody here something, but not I.

Now, on to some substance. I contacted the site honcho who stated that formatting changes had in fact been made. However, he seems to think there's something wrong on his end and is looking into it.

[moonbat]

Like I said, best way to test is on a fresh, unmodified profile to rule out anything due to extensions or changed settings on your end. Use about:profiles(*) to create an empty profile, and simply launch that when you want to see if a website works properly or not before reporting it here.


(*) - Inb4 'about:profiles is a hack job' etc - it does the job and is easier for people who get scared off by a commandline.

[Moonchild]

I don't know javascript from yo mama.

But you know how to read, right? You can string a sequence of characters together and see what they refer to.
If a "source" of an error points to "chrome://opendownload/((something))" then how difficult is it to understand it's caused by something in "opendownload"?

Use your brain for something else than generating output for a change. Learn something.

[van p]

how difficult is it to understand it's caused by something in "opendownload"?

Except, apparently, it isn't.

[moonbat]

how difficult is it to understand it's caused by something in "opendownload"?

Except, apparently, it isn't.

Like he said, read the damn error message, use some common sense, and don't hide behind the 'I'm not a programmer' excuse. It's in English, not ancient Egyptian hieroglyphics.

[Moonraker]

how difficult is it to understand it's caused by something in "opendownload"?

Except, apparently, it isn't.

How have you ascertained it isn't.?

[vannilla]

To be fair, the error on the website might be unrelated to the extension.
The messages on the console are about Open Download, though, but that's it.
It would be helpful if the OP could test the site on a new clean profile, as that would give a definitive answer.

[van p]

Moonraker, as Moonchild suggested, I disabled the extension (in all 3 browsers), and that had no effect.

moonbat, one of us needs to calm down; I know it isn't me. And for the record, I did see "opendownload" when I perused the console info, but it didn't register with me at the time.

[Moonchild]

as Moonchild suggested, I disabled the extension (in all 3 browsers), and that had no effect.

Then you have 2 problems to look at. one being opendownload, the other an issue with this website.

I had a brief look at the way they want to construct their "menu" and it's simply broken as designed. They have buttons that are apparently supposed to be styled but there are no styling rules for it. they have fontawesome classes on elements as well but no fontawesome css. Someone really needs to have a look at it on the server side.

[Moonchild]

Looks like css is simply missing because they are using "link rel=preload" which is an experimental feature that isn't supported by us (even Firefox only JUST has it since 85, according to MDN, but of course it's a long-since implemented Chrome feature where this originated), so that explains all the missing styling on the page (not just the menu, but the rest of the page too) when comparing.

[van p]

Moonchild, I sent your comments to the site developer. Thanks.

[van p]

I got this response from the website: "Thank you very much! Dang, I've been working with a developer in the UK for a few years now to do basic work and website tweaks, but he's getting slower with everything, and now it looks like he's getting sloppy. I'm going to need to look for a new Wordpress developer who can help with some of these backend coding issues that are over my head. Looks like it's time to search Upwork or perhaps Fiverr.

I appreciate your help and will keep you posted!"

Later, he said: "[W]e're working on it. My back-end developer guy in the UK is slow as molasses right now, but he said he's going to check browser compatibility and fix the issues. I think I need to find some new help.
I'll keep you posted..."

In Moonchild's down time, he could earn some spare krona.

[Moonchild]

In Moonchild's down time, he could earn some spare krona.

I know very little about dealing with WordPress though.
The fix is simple though, just use rel="stylesheet" instead of "rel="preload", remove the onload handler from the <link> elements (which requires JS for it to work, as well, by the way, which isn't good or necessary to just load stylesheets!), and done. But I don't know how to do that in Wordpress.

[van p]

Still, apparently you know more than the person who performed that abortion.