EE wrote:
flyguy wrote:
EE wrote on 10/7/2020 11:40 AM:
flyguy wrote:
SM 2.53.4 won't load https://www.bissell.com/ - the status message
is Read www.bissell.com
Chrome loads it immediately. What could the problem be?
Here's another one that won't load, yet works properly in Chrome:
https://wingsandwheels.com/
Instead of the website, "403 Forbidden nginx" is displayed. The
website worked in SM a couple months ago, but hasn't recently, with
either 2.53.4 or 2.49.3
That first item is not even a web page. It is a script.
The second one gives me the same result: forbidden.
Chrome and Edge both load a website for the first, so it seems to be
real.
I suspected the second one (wingsandwheels) was ignoring SM, and that
appears to be the case.
The bissel.com item is not regular HTML. The first tag was a script
tag, and the last line had an end script tag. It was not proper HTML code.
It seems to depend on whether JavaScript is enabled. With NoScript
blocking all scripts on the page, at least some content shows up (but no
images). Although there is a lot of scripting on the page, it's got the
usual general structure:
<!DOCTYPE html>
<html lang="en">
<head>
...
</head>
<body class="">
...
</body>
</html>
However, if I enable scripting for bissell.com and adobedtm.com, it
fails to complete loading. Viewing the source at that point does just
show one big <script>...</script> element, as you describe. Strangely,
if I close the source view and reopen it, it's then blank.
Looking at the "Network" tab of developer tools while loading the page,
it seems to first load the same main page as I see without scripting
enabled (though I never see it actually appear in the browser) and then
a load of script and CSS files. That's only visible briefly (unless I
quickly cancel loading the page), and then the network log is cleared as
if it's redirected to another page, but nothing else shows up.
It seems to redirect to a wyciwyg:// URL, which fails to load. I have
vague recollection of some discussion about those causing issues some
time ago (or at least showing up as a side-effect of issues; from what I
recall they might exist internally but shouldn't generally be actually
seen?) Perhaps one of those newer things that's been refined in newer
versions of Firefox, but the version SeaMonkey is based on doesn't
handle particularly well.
As well as that site being completely overkill on JavaScript! After
all, why just use an HTML tag to include an image when you can use 500
lines of JavaScript to do it...
--
Mark.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
