Ant wrote:
https://www.rottentomatoes.com takes me to
https://www.rottentomatoes.com/unsupported-browser?err=custom-elements,shadow-dom
that says "To enjoy RottenTomatoes.com, try using a newer browser like
Google Chrome, or Mozilla Firefox." I tried changing SeaMonkey v2.53.3's
UA to Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:80.0) Gecko/20100101
Firefox/80.0, but that didn't work. :(
What else to try? Thank you for reading and hopefully answering. :)
Check the recent thread "More and more sites don't accept Seamonkey".
That was a discussion that focused on issues with Rottentomatoes.
I did some testing there, and I found that there's no capacity of
browser spoofing that will get you past their demands for current
Firefox or Chrome, although I did find that if using NoScript to block
scripting, I can get through to their content.
I believe that what's happening is that their scripting is explicitly
checking for the capabilities of the browser itself, rather than simply
sniffing the UA string.
I know also that I've seen posts from FRG (one of the developers) that
indicate that there's a lot of stuff that Google is doing with YouTube,
and where it's becoming increasingly difficult for browsers that are not
Chrome (or even not Chromium) to keep up, even if Firefox versions at 78
and later are apparently not a problem.
I don't normally interact with that site, but given that its focus is
movie reviews, I presume that there's a lot of interaction with YouTube
streaming, and that's probably the reason for the objection.
Moving forward, it seems that you have two choices:
- If you're just interested in reading the static content (reviews and
commentary, although probably not the ability to contribute to
discussion), you can find most of that, if you use NoScript to block the
site's scripting host, so that it can't query your browser.
- If you want the full capacity of the site, including streaming from
YouTube, it's not going to be possible in Seamonkey. That doesn't
require you to abandon Seamonkey generally, but to interact with that
particular site, you will need to use a browser that they will accept.
As a general aside, I've seen a number of threads in this newsgroup
recently that note that people are abandoning Seamonkey, and sometimes,
the issue is conflict with sites that don't like Seamonkey. Although
there are issues there (and sometimes, spoofing is a work-around),
there's definitely a few sites (as you're seeing with Rotten Tomatoes)
that it's beyond anything you can do.
However, it doesn't mean that you have to abandon Seamonkey, even if you
do need to be prepared to make occasional use of another browser. For
me, I make extensive use of NoScript, as well as blocking of third-party
cookies, and there are times when I simply can't tweak settings enough
to get the site to behave. I find this to be especially the case with
some e-commerce sites.
To get around this issue, I keep a Firefox profile that is pretty much
default settings -- the only tweaks that I have there is to flush all
user data, cache, history and cookies at the end of a session. Thus, if
I can't get a site to work, I'll launch Firefox with that profile to
facilitate the transaction, and then close out, and resume my regular
work in Seamonkey.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
