Re: Problem with Twitter in SeaMonkey

[Jonathan Wilson]

I tried another profile, that didn't help.
And I have referrers turned on.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Problem with Twitter in SeaMonkey

[Ant]

On 1/16/2021 5:37 PM, Jonathan Wilson wrote:
When I visit Twitter with SeaMonkey (latest version on Windows) I get 
"Something went wrong." with a "try again" button that does nothing.

It works fine on other browsers on the same machine.

I have tried deleting all the Twitter related cookies and logging in 
again fresh and that didn't work.


Anyone else seen this or got any suggestions?


I noticed Twitter wants send referers to work. Do you have that 
disabled? Also, have you tried a new SM profile yet?

--
2021 isn't any better so far. :( Note: A fixed width font (Courier, 
Monospace, etc.) is required to see this signature correctly.

   /\___/\http://aqfl.net & http://antfarm.home.dhs.org
  / /\ /\ \
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Problem with Twitter in SeaMonkey

[Jonathan Wilson]

When I visit Twitter with SeaMonkey (latest version on Windows) I get 
"Something went wrong." with a "try again" button that does nothing.

It works fine on other browsers on the same machine.

I have tried deleting all the Twitter related cookies and logging in again 
fresh and that didn't work.


Anyone else seen this or got any suggestions?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Site that doesn't work since upgrading to 2.53.5.1

[Dirk Fieldhouse]

On 16/01/2021 17:37, Philip Gladstone wrote:


I'm the author of pskreporter.info and I'm trying to work out why it doesn't 
work in seamonkey. The root cause appears to be that pointermove events are not 
being delivered to the application.

In particular, the following test demonstrates the difference between firefox 
and seamonkey

* Go to https://pskreporter.info/pskmapn?
* After the page loads, open the developer tools and set in the console 
'disable_timers = 1' and then wait a couple of seconds.
* Now press break in the source debugger. It should break on the next event
* Now move the mouse into the map area and observe that it does not break.
* Clicking on the + or - in the top left corner will trigger a break.


SM 2.53.5.1 Linux x86; NoScript 5.1.9.

I loaded the site and enabled JS for pskreporter.info, cdn.polyfill.io, 
cdn.jsdelivr.net, unpkg.com, ajax.googleapis.com, and bootstrapcdn.com. 
Now there's a world map with day/night overlay and lots of pins. In the 
map area, only the +/- and the copyright links are abinding gives this
ctive. The count of reception records at the bottom of the page 
increments continually.


Following steps 2-4, I get a break on step 3 at map_control_oln.js:4363 
(repeatably). Step 4 is as you say. Step 5: no break.



In Chrome, you can figure out that it is this element that has the pointermove 
event handler:
...

However I can't tell where the event handler is in seamonkey.
...


In the Inspector tab of the SM dev tools, you should see a little "ev" 
in a black-filled box after each element that has any attached event 
handler.


For me, the same element shows the pointermove event handler as

function(t) {
  this.originalPointerMoveEvent_ = t;
  var e = !(!this.down_ || !this.isMoving_(t));
  this.dispatchEvent(new Da(t.type, this.map_, t, e))
}

If I run the minified ol.js through beautifier.io I find this at line 14776:
}, e.prototype.relayEvent_ = function(t) {
this.originalPointerMoveEvent_ = t;
...

As you say, the event is obviously not being delivered: maybe some this 
is not being bound as expected or some issue with preventDefault?


HTH

/df

--
London
UK
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Site that doesn't work since upgrading to 2.53.5.1

[Philip Gladstone]

I'm the author of pskreporter.info and I'm trying to work out why it doesn't 
work in seamonkey. The root cause appears to be that pointermove events are not 
being delivered to the application.

In particular, the following test demonstrates the difference between firefox 
and seamonkey

* Go to https://pskreporter.info/pskmapn?
* After the page loads, open the developer tools and set in the console 
'disable_timers = 1' and then wait a couple of seconds.
* Now press break in the source debugger. It should break on the next event
* Now move the mouse into the map area and observe that it does not break. 
* Clicking on the + or - in the top left corner will trigger a break.

In Chrome, you can figure out that it is this element that has the pointermove 
event handler: 
+−⇧© https://openmaptiles.org/";>OpenMapTiles © https://www.openstreetmap.org/copyright";>OpenStreetMap 
contributorsi

However I can't tell where the event handler is in seamonkey. 

I'm running seamonkey 2.53.5.1 and a reasonably current firefox.  

Maybe what caused the problem was the update of openlayers to v6. I tried 
moving to the current version (6.5) but it didn't help. 

Actually, I think that that is the problem. If I use v6.1.1 of ol, then it 
works, v6.5 it doesn't. It seems that I need to spend a few hours with git 
bisect to find what changed.

I can't actually use v6.1.1 as it has issues with certain projections and it 
triggers canvas rendering bugs that I fixed in later versions.

Philip



On Saturday, January 16, 2021 at 3:27:26 AM UTC-5, meagain wrote:
>  Original Message  
> > On 14/01/2021 22:01, no...@nonospam.org wrote: 
> >> 
> >> ... 
> >> I installed SM v2.53.5.1 on this laptop and confirmed that the problem 
> >> with https://pskreporter.info/pskmap.html was present. I then 
> >> uninstalled that version of SM and installed v2.49.4. The problem was 
> >> still present! I repeated this several times, going back as far as 
> >> v2.30, and all of them had the same problem with this site. 
> > 
> > Your observation makes it all the more relevant to try older Firefox 
> > versions with the site. I think I tried SM 5.3.5.1 spoofing the user 
> > agent as Firefox without success, which makes it likely that some site 
> > JS is testing for a feature that isn't present in SM. As it works with 
> > the latest ESR, one could try each previous ESR until it doesn't, and 
> > that might offer a good hint as to what's missing with SM. 
> > 
> >> I am extremely embarrassed to have made this error in diagnosing the 
> >> situation and I apologize to everyone who has spent time looking into it. 
> > > ... 
> > 
> > Very generously put, but who could cast the first stone? 
> > 
> > /df 
> >
> The site passes the W3C Validator, which always makes me happy :-) 
> WAG: Could the site be oriented to touch screen use?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Possible Flash issue on Mac?

[Dirk Fieldhouse]

On 13/01/2021 16:56, Dirk Fieldhouse wrote:

...>

A recent non-timebombed version of Flash, as I understand it:


WARNING: 425MB zip archive! You have to extract the appropriate Flash 
player for your platform from the archive and install it in the 
appropriate way.


For Debian/Ubuntu Linux users, the Flash package was just a script that 
downloaded the player from Adobe, and the most recent version simply 
deleted the player's files and the script. Obviously rolling back 
wouldn't be useful, so manual installation from the archive is required, 
and "worked for me", at least as far as listing Flash in Tools>Add-ons 
Manager>Extensions.


You can get a later version (34.x) at  (JS 
required) 
, 
but there may be licensing issues, and who knows what Great Internet 
Firewall "compatibility" features. See 



/df

--
London
UK
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Site that doesn't work since upgrading to 2.53.5.1

[meagain]

 Original Message 

On 14/01/2021 22:01, no...@nonospam.org wrote:


...
I installed SM v2.53.5.1 on this laptop and confirmed that the problem 
with https://pskreporter.info/pskmap.html was present. I then 
uninstalled that version of SM and installed v2.49.4. The problem was 
still present! I repeated this several times, going back as far as 
v2.30, and all of them had the same problem with this site.


Your observation makes it all the more relevant to try older Firefox 
versions with the site. I think I tried SM 5.3.5.1 spoofing the user 
agent as Firefox without success, which makes it likely that some site 
JS is testing for a feature that isn't present in SM. As it works with 
the latest ESR, one could try each previous ESR until it doesn't, and 
that might offer a good hint as to what's missing with SM.


I am extremely embarrassed to have made this error in diagnosing the 
situation and I apologize to everyone who has spent time looking into it.

 > ...

Very generously put, but who could cast the first stone?

/df



The site passes the W3C Validator, which always makes me happy :-)
WAG: Could the site be oriented to touch screen use?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey