OK, I have submitted a ticket:
Ticket ID: 13797 Subject: Forum login problems with Palemoon browser
Will see what happens if anything.
Thanks
davews for doing this.... That said, I'm personally not very hopeful. If you take a look at the Pale Moon thread on this topic (the link you previously posted) you'll see why.
It is surmised that the new combined login that Avast has released is likely coded using
Asynchronous Programming with the abstraction called "promises" (or sometimes deferreds) which is not really a good idea for a login interface actually (refer to link for details on this approach) and I would add that in so doing may very well be neglecting to check for their existence in browsers. It is pointed out in the Pale Moon topic that Avast may have actually taken the easy approach and used quote "... a cookie-cutter library" for their new "single sign-on" login procedure and because of this will most likely have "no way to troubleshoot or fix it as a result". It is advised that Avast should be using ".... any of the server-side shims available" which would go a long way toward helping improve browser compatibility.
I'm simply not convinced that Avast is going to really care enough to make the effort to do it right in order to fix the issue. I'm inclined to think that this problem ticket will simply not reach the level of priority at which point Avast would address this issue to be perfectly honest. I'd like to think otherwise, but I'm afraid this is perhaps just the way Avast does things.
But we'll see, I told
bob3160 that I would touch bases with him in another 90 days and see where we stand at that point. I'd certainly like to be wrong and instead be pleasantly surprised to find out
bob3160 is correct in the end, but I'm afraid I'll instead be asking
bob3160 to come up with another excuse and another dead-line date.
Prove me wrong Avast!!