Re: Setting up an out-going filter

2020-01-13 Thread Ray Davison

Daniel wrote:

On my UseNet server, I monitor about 75 groups, Sure, most of them 
have very little to nil action, but some newsgroups are still 
reasonably active.


So, what I would like to do (at the start of this new year) is to set 
up outgoing filters so, say, all the replies to Operating Systems 
(Win7 & Linux) type newsgroups automatically go into one folder, all 
the replies to T.V. show type newsgroups go into a second folder and 
all the rest go into a third folder.


What is your current setup in SM mail regarding UseNet?

Do you have 75 newsgroups set up in SM mail?

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


Re: Setting up an out-going filter

2020-01-13 Thread Ray Davison

Daniel wrote:

If I were really worried, yes, I could do that, but ... hey, you guys 
can see my OP, so, IMHO, not worth the worry/trouble!!



Do you have View > Sort by > Date, Threaded and Descending?

If you do, then SM mail looks like an ongoing conversation.

https://photos.app.goo.gl/9JfpgptGSAn3ED4M9

Ray

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


Re: Images using data-src tag?

2020-01-13 Thread Nuno Silva
On 2020-01-13, Gerry Hickman wrote:

> Browsing to this page, with SeaMonkey/2.49.4, the images seem to be
> missing? I think they're using a "data-src" tag.
>
> https://developer.ibm.com/tutorials/l-virtual-filesystem-switch/

Those are "lazy-loaded" images, handled by javascript code.

>From a quick glance at the page source, the image loading code uses
IntersectionObserver, which was introduced in Firefox 55 [1].

As Seamonkey 2.49 is "based on" Firefox 52, the lack of
IntersectionObserver is likely the problem. But it will probably work
with Seamonkey 2.53 ("based on" Firefox 56).

[1] 
https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#Browser_compatibility

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


Request received: Images using data-src tag? ref:_00DU0Lfqj._5001v1Dwq32:ref

2020-01-13 Thread Support TheFork via support-seamonkey
Hello ,

Thanks for your email. We have received your request 04042865 and it is being 
processed by our Support team.

To leave additional comments, please reply to this email.

Best,

TheFork team


TheFork, a TripAdvisor Company
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Images using data-src tag?

2020-01-13 Thread Gerry Hickman via support-seamonkey



Browsing to this page, with SeaMonkey/2.49.4, the images seem to be 
missing? I think they're using a "data-src" tag.


https://developer.ibm.com/tutorials/l-virtual-filesystem-switch/

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


Re: Problem following links if JavaScript enabled

2020-01-13 Thread Richard Owlett

On 01/12/2020 11:11 AM, Dirk Fieldhouse wrote:

On 12/01/20 12:38, Richard Owlett wrote:

I'm running SeaMonkey version 2.49.4 [Build identifier: 20180711182954]
under Debian 9.8 [Stretch]

I routinely surf with JavaScript disabled without problems.

I have problems following *ANY* link from https://manpages.debian.org/
*IF AND ONLY IF* JavaScript is enabled.

The symptoms are:
   1. Destination link is promptly displayed in URL bar.
   2. The page never loads/displays.


Confirmed in SM 2.49.5 LXLE based on Lubuntu 16.04/32-bit for 'Open in 
New Tab', except that with the dev tools pane displayed the new tab may 
eventually display.


But the site doesn't lose any functionality without JS as far as I can 
see -- it's just stuff like lazy-loading fonts.



Is this a:
  1. site problem?
  2. SeaMonkey failure?
  3. an unidentified local problem?


Difficult to tell. I have a fair few extensions loaded. You could test 
SM with a new profile, and if that fails try FF 52 ESR, and if that 
fails, other versions and browsers.




I have no extensions loaded. I'll try later with a default profile.
Thanks.



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


Re: Problem following links if JavaScript enabled

2020-01-13 Thread Richard Owlett

On 01/12/2020 08:38 AM, mozilla-lists.mbou...@spamgourmet.com wrote:

Richard Owlett wrote:

I'm running SeaMonkey version 2.49.4 [Build identifier: 20180711182954]
under Debian 9.8 [Stretch]

I routinely surf with JavaScript disabled without problems.

I have problems following *ANY* link from https://manpages.debian.org/
*IF AND ONLY IF* JavaScript is enabled.

The symptoms are:
   1. Destination link is promptly displayed in URL bar.
   2. The page never loads/displays.


I see the same, but only if the link is opened in a new tab.


I see the same. I had been investigating a vendor provided script and 
had been opening a series of man pages in multiple tabs.


  Just 
clicking the link (to open in the same tab) or opening in a new window 
works.  Opening in a new tab (either via context menu, Ctrl+click or 
middle-click) behaves as you describe.  Attempting to reload the page 
doesn't help, but clicking in the address bar and pressing "Enter" does 
load the page.


That was part of what prompted me to post.



Having opened in a new tab, attempting to view the page source has 
"Source of: wyciwyg://14/https://manpages.debian.org/...; in the title 
bar - truncation is mine, but the "wyciwyg://14/" looks odd.


I see similar. In a test just now, instead of '14' I see '48' or '49' 
depending on link clicked. I'll investigate further.




Viewing source of a successfully loaded page shows "Source of: 
https://manpages.debian.org/...; as would be expected.



Is this a:
  1. site problem?
  2. SeaMonkey failure?
  3. an unidentified local problem?

Suggestions?


Not sure.  The presence of "wyciwyg" in the page source when it's 
failing to load looks like it could be some interaction between caching 
and something JavaScript is doing on those pages.


I'm using SeaMonkey 2.49.5 on Linux Mint.



Thank you



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