On 6/13/2020 8:34 AM, Frank-Rainer Grahl wrote:
Hawker wrote:
On 6/12/2020 6:39 PM, Frank-Rainer Grahl wrote:
I have yet see a site that fails in 2.53.x and works in 2.49 but
there may be some. On the other hand there are a lot of sites no
longer working in 2.49.
Home Depot,
Not accessible geo blocking
Ali Baba
Can browse fine. Where is the problem? Login related?
Redit,
Fixed in 2.53.3. Recent breakage.
WLOS
Works fine including video player. Where is the problem login related?
Needed to whitelist a bunch of sites in NoScript.
Facebook (locks up and crashes in 2.53 not in 2.49)
Don't use is. Not aware of problems.
The Onion
Gave up. Sh*t site. Probably needs event features or new image formats
ported but not sure.
Also SM 2.53 crashes or locks up multiple times a day for me, 2.49
crashed maybe once every other week for me.
2.53 almost never crashes for me. The one crash I have now and then on
shutdown is because of a work in prograss patch not in the tree. Without
a crash id I just say you have hardware or other problems. You can prove
me wrong by providing a crash id.
All these sites work in fine 2.49 but have serious issues in 2.53
If they crash you have a different problem.
Cool if you want to blame the site rather than Seamonkey when these
sites work on every other browser I tried. But since the other
browsers work I ain't buying it.
Me neither. I know that SM is missing features and has problems. But I
also know that 2.53 is better than 2.49 and that is what I said. Reddit
is fixed in 2.53.3. Without a crash id nothing can be fixed or verified.
And yes I blame sites like the onion because they are bloatad sh*t. And
if you suppot these sites it is your choice and you might need a
different browser. As you said. We can't keep up with a 100 people
effitively working against you and turning out half baked specs and
features just to support the latest Chrome.
What I am sick of is general reports liks yours. Nothing works; Always
crashes; Writing is on the wall; blablabla.
This can not be fixed. There is the error log which should show
javascript and other errors. There is the crash reporter. And there is
bugzilla where problems can be reported at a last resort but need clear
instructions to reproduce including urls not "I am running SeaMonkey for
a day and then nothing works; it crashes daily without a reason; memory
goes up by magic or whatever.
FRG
Frank. I don't even know where to start with a messed up response like
yours. I don't use it, or I don't like that site is not a valid reason
to dismiss a problem. All the sites I listed have serious functionality
issues in 2.53 that they do not in 2.49. Many of the issues are buried
beyond the home screen and unless you are a user it is lost to even try
to explain.
Your response to much of this reminds me of what activists call victim
blaming. IE if you didn't wear that sexy outfit you wouldn't have gotten
raped so it's your fault. If you didn't use that site that I don't like
that works in every other browser you tried you wouldn't have problems
so it's your fault, just don't use those sites.
The bottom line is users are experiencing problems that we are not with
other sites. We are, mostly not programmers, the things you ask for are
beyond our time and/or technical ability. When I look at Bugzilla I am
lost as it isn't readable or usable to a non programmer. Java console?
Same thing. I'm an EE not a programmer.
Look I get it. Y'all are over worked, under staffed, under funded. You
are working with both hands tied behind your back and it is a losing
battle for an obscure bowers that most people have never heard of. Kudos
to you. I appreciate you keeping the abandoned Mozilla sweat going all
these years but it clearly is getting to the end of it's acceptance and
usability due to a lack of greater public interst. Reminds me of when I
had to finally abandon my beloved Netscape 4.8. I feel for you. I don't
want to dump on you or blame you for the problems. But the fact is that
SM is many many revisions of the engine behind and there are more and
more sites everyday that are breaking due to this. I started with
Netscape 1.0 (yes I go back that far). I like SM, I want to continue
with SM but at the point where I have to maintain two or three different
browsers just to do do.
Yes it sucks that Sites have to "turning out half baked specs and
features just to support the latest Chrome." but that is the state and
reality of the internet today and people need to use those "half baked
and bad coded sites". We don't often have the option to just ignore a
site as you seem to. If Digikey (another site I use daily that has some
functional issues around refreshes in 2.53 that were not in 2.49) has
issues it cost me and my clients time and money. I can't deal with
that. I don't have the luxury to say "crappy site" and move on. that
isn't reality. The reality is that SM has functionality issues with
websites that other sites don't and people will use those sites. If SM
can't do it we will need other browsers and that is a royal PITA.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
