Re: king soopers not compatible with sm

2014-12-20 Thread Daniel

On 20/12/14 03:14, WaltS48 wrote:

On 12/19/2014 04:20 AM, Daniel wrote:

On 19/12/14 02:41, WaltS48 wrote:

On 12/18/2014 09:52 AM, Jim wrote:

Paul B. Gallagher wrote:

Jim wrote:


Yesterday, when I went on the King Soopers web site
(www.kingsoopers.com) I kept getting the message that my browser is
out of date (it isn't).


You can browse the site normally if you click the link, To continue
without upgrading, click here.

They set a cookie called bypassUnsupportedBrowser so you won't be
nagged on every click -- until, of course, you clear the cookie.


I did that yesterday (continue without upgrading), but I received
that
same warning about 3 times total while on that site.

My browser is set to Accept all cookies, and under retention, Accept
cookies normally.

Will see if it continues to do it today.



Switch to Firefox.


But Jim is showing FF34 in his User Agent!!




He has Advertise Firefox compatibility checked as you do, I do, and
probably most of the ~120,000 SeaMonkey users.


I don't normally have Advertise Ff enabled, just turned it on to test 
for this problem, I think!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 
SeaMonkey/2.29 Build identifier: 20140829003846

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 
SeaMonkey/2.31 Build identifier: 20141020202138

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


Re: king soopers not compatible with sm

2014-12-20 Thread David E. Ross
On 12/19/2014 9:51 PM, Paul B. Gallagher wrote:
 NoOp wrote:
 
 I believe what David is pointing out is that the issue king soopers
 not compatible with sm is a browser sniffing issue. I'm currently
 spoofing: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
 Trident/5.0) and the site doesn't even blink - it loads  keeps on
 going. Ditto if I spoof as Chrome or Safari. However, without
 spoofing I get the update browser issue... really? I'm spoofing IE
 9.
 
 I'm sure you're right, and the webmaster knows it too and has provided 
 user-operated error handling: if we got it wrong, click here and we'll 
 quit nagging you. They set a cookie so they don't forget your choice, 
 and that's the end of it (until the user clears the cookie).
 
 As far as I'm concerned, it's trivially easy to click one link and move 
 on, though I do find it offensive that they don't think it's important 
 enough to write W3C compatible code. But if I got upset every time I 
 browsed to a noncompliant site I'd never get out of bed.
 
 If someone prefers to change their UA string back and forth as they 
 browse from site to site, they're welcome, but to my mind that's more 
 effort than a click and an eye roll, even if I throw in a sigh.
 

It is no effort at all if you have the PrefBar extension and use its
User Agent selection list (extlist, in PrefBar's terminology).

-- 
David E. Ross

I am sticking with SeaMonkey 2.26.1 until saved passwords can
be used when autocomplete=off.  See
https://bugzilla.mozilla.org/show_bug.cgi?id=1064639.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: king soopers not compatible with sm

2014-12-20 Thread WaltS48

On 12/20/2014 10:48 AM, David E. Ross wrote:

On 12/19/2014 9:51 PM, Paul B. Gallagher wrote:

NoOp wrote:


I believe what David is pointing out is that the issue king soopers
not compatible with sm is a browser sniffing issue. I'm currently
spoofing: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
Trident/5.0) and the site doesn't even blink - it loads  keeps on
going. Ditto if I spoof as Chrome or Safari. However, without
spoofing I get the update browser issue... really? I'm spoofing IE
9.


I'm sure you're right, and the webmaster knows it too and has provided
user-operated error handling: if we got it wrong, click here and we'll
quit nagging you. They set a cookie so they don't forget your choice,
and that's the end of it (until the user clears the cookie).

As far as I'm concerned, it's trivially easy to click one link and move
on, though I do find it offensive that they don't think it's important
enough to write W3C compatible code. But if I got upset every time I
browsed to a noncompliant site I'd never get out of bed.

If someone prefers to change their UA string back and forth as they
browse from site to site, they're welcome, but to my mind that's more
effort than a click and an eye roll, even if I throw in a sigh.



It is no effort at all if you have the PrefBar extension and use its
User Agent selection list (extlist, in PrefBar's terminology).




Haven't come across anything where I need that extension.

--
One of the millions of Firefox makes me happy users
https://input.mozilla.org/en-US/feedback/firefox/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


SM 2.31 unhappy, Firefox happy.

2014-12-20 Thread A Williams
One of the websites I use a lot misbehaves with SM 2.31.  The Error 
Console shows an insane number of errors/warnings (starting from the 
oldest):


Timestamp: 20.12.2014 19:48:15
Warning: window.controllers is deprecated. Do not use it for UA detection.
Source File: chrome://editor/content/ComposerCommands.js
Line: 198

Timestamp: 20.12.2014 19:46:53
Error: TypeError: browsers[i] is undefined
Source File: chrome://navigator/content/tabbrowser.xml
Line: 331
(7 of those)

Timestamp: 20.12.2014 19:43:10
Error: SyntaxError: illegal character
Source File: 
https://pixel.quantserve.com/pixel/p-mBVrc_qCgY3g5.gif?media=adlabels=_imp.adserver.doubleclick,_imp.publisher.75295,_imp.placement.284192221,_imp.creative.55719018

Line: 1, Column: 6
Source Code:
GIF89a
followed by 0001 in a box

Timestamp: 20.12.2014 19:43:09
Error: pixel.rubiconproject.com : server does not support RFC 5746, see 
CVE-2009-3555

(3 of these)

Timestamp: 20.12.2014 19:43:10
Warning: Unknown property '-moz-background-clip'.  Declaration dropped.
Source File: http://i.r1-cdn.net/static/css/ilike.css
Line: 423, Column: 22
Source Code:
  -moz-background-clip: padding;

Timestamp: 20.12.2014 19:43:10
Warning: Unknown property '-moz-border-radius'.  Declaration dropped.
Source File: http://i.r1-cdn.net/static/css/ilike.css
Line: 421, Column: 20
Source Code:
  -moz-border-radius: 0 0 0 3px;
(** a large number of the previous 2 errors **)

Timestamp: 20.12.2014 19:43:04
Warning: Unknown property '-moz-box-shadow'.  Declaration dropped.
Followed by an incredibly long string

Warning: Unknown property '-moz-background-size'.  Declaration dropped.
(lots of these)

Timestamp: 20.12.2014 19:43:04
Warning: Error in parsing value for 'display'.  Declaration dropped.
Followed by another very long string

Warning: Unknown property '-moz-flex-basis'.  Declaration dropped.
(hundreds of the last two errors)

complaints about column-rule, column-gap, column-count (unknown 
properties, Declaration dropped)


Warning: Unknown property '-moz-background-size'.  Declaration dropped.
(lots of these)

The full list would blow any size restrictions on this Newsgroup.
SM 2.30 and the current Firefox can both handle the page.
This affects Linux and Windows 7.

Should I be looking for 2.32 beta versions?  Or should I fallback to 2.30?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: New Win32 builds! Onna stick! Geddit while they're hot!

2014-12-20 Thread Ruediger Lahl
*Philip Chee* schrieb:

 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/?C=M;O=D

It ran only for 3 Builds(Days).  :-(
-- 
best regards
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM 2.31 unhappy, Firefox happy.

2014-12-20 Thread WaltS48

On 12/20/2014 02:13 PM, A Williams wrote:

One of the websites I use a lot misbehaves with SM 2.31.  The Error
Console shows an insane number of errors/warnings (starting from the
oldest):

Timestamp: 20.12.2014 19:48:15
Warning: window.controllers is deprecated. Do not use it for UA detection.
Source File: chrome://editor/content/ComposerCommands.js
Line: 198

Timestamp: 20.12.2014 19:46:53
Error: TypeError: browsers[i] is undefined
Source File: chrome://navigator/content/tabbrowser.xml
Line: 331
(7 of those)



These two appear to be errors with SeaMonkey, not the site.

snip



Should I be looking for 2.32 beta versions?  Or should I fallback to 2.30?



December 16, 2014

SeaMonkey 2.32 Beta 1

SeaMonkey 2.32 Beta 1 is now available for free download on the 
SeaMonkey website. We encourage testers to get involved in discussing 
and reporting problems as well as further improving the product.


[SeaMonkey 2.32 Beta 1](http://www.seamonkey-project.org/releases/2.32b1)

Switch to Firefox.


--
One of the millions of Firefox makes me happy users
https://input.mozilla.org/en-US/feedback/firefox/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Meanwhile, on the good news part of the news...

2014-12-20 Thread Geoff Welsh

Geoff Welsh wrote:

Philip Chee wrote:

On 28/11/2014 07:42, Geoff Welsh wrote:


This addressing bug fix has landed;

https://bugzilla.mozilla.org/show_bug.cgi?id=970456

and is fixed in nightlies of TB they say.

Not sure if/how/when that would/might drift over to SM.


https://hg.mozilla.org/comm-central/rev/98414962486a

All the changes are in /mailnews/ this part of the comm-central source
tree is shared between Thunderbird and SeaMonkey so normally will not
need any further action by the SeaMonkey team.



That's great!

Thanks for the clarification, Phil.

GW



Responding to myself here, but as of right now, running SM 2.34a1, 
because the bug for TBird addressing #970456 is FIXED. the related SM bug


https://bugzilla.mozilla.org/show_bug.cgi?id=972690

is Fixed.

Maybe 2.33b has it implemented too IDK, but it's definitely fixed in SM 
2.34a1.


The latest official release did not have the fix when I tried it.

GW
on many a different Mac,

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


general.autoScroll in SM 2.32

2014-12-20 Thread Petr Voralek
   Hello!

  In seamonkey 2.32b1 (and 2.32b2 candidate build) stopped working
option general.autoScroll for me.
It seems that this option is still functional in seamonkey versions 2.31
(release) and 2.34a1 (trunk).
Does anyone also have a similar problem?

-- 
Petr Voralek(JabberID: na...@jabber.cz)

... What an excellent day for an exorcism.  (Regan MacNeil, The Exorcist)



signature.asc
Description: OpenPGP digital signature
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Silverlight not working with Flashblock 1.3.21 either

2014-12-20 Thread EE
Flashblock 1.3.21 was fixed up for SeaMonkey 2.31 as far as Flash and 
HTML5 are concerned, but it is completely disabling Silverlight, just as 
Flashblock 1.5.18 was doing.  There must be some other way to prevent 
HTML5 from starting automatically if it has no play button.  The 
question - what is that other way?

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


Re: SM 2.31 unhappy, Firefox happy.

2014-12-20 Thread PhillipJones

A Williams wrote:

One of the websites I use a lot misbehaves with SM 2.31.  The Error
Console shows an insane number of errors/warnings (starting from the
oldest):

Timestamp: 20.12.2014 19:48:15
Warning: window.controllers is deprecated. Do not use it for UA detection.
Source File: chrome://editor/content/ComposerCommands.js
Line: 198

Timestamp: 20.12.2014 19:46:53
Error: TypeError: browsers[i] is undefined
Source File: chrome://navigator/content/tabbrowser.xml
Line: 331
(7 of those)

Timestamp: 20.12.2014 19:43:10
Error: SyntaxError: illegal character
Source File:
https://pixel.quantserve.com/pixel/p-mBVrc_qCgY3g5.gif?media=adlabels=_imp.adserver.doubleclick,_imp.publisher.75295,_imp.placement.284192221,_imp.creative.55719018

Line: 1, Column: 6
Source Code:
GIF89a
followed by 0001 in a box

Timestamp: 20.12.2014 19:43:09
Error: pixel.rubiconproject.com : server does not support RFC 5746, see
CVE-2009-3555
(3 of these)

Timestamp: 20.12.2014 19:43:10
Warning: Unknown property '-moz-background-clip'.  Declaration dropped.
Source File: http://i.r1-cdn.net/static/css/ilike.css
Line: 423, Column: 22
Source Code:
   -moz-background-clip: padding;

Timestamp: 20.12.2014 19:43:10
Warning: Unknown property '-moz-border-radius'.  Declaration dropped.
Source File: http://i.r1-cdn.net/static/css/ilike.css
Line: 421, Column: 20
Source Code:
   -moz-border-radius: 0 0 0 3px;
(** a large number of the previous 2 errors **)

Timestamp: 20.12.2014 19:43:04
Warning: Unknown property '-moz-box-shadow'.  Declaration dropped.
Followed by an incredibly long string

Warning: Unknown property '-moz-background-size'.  Declaration dropped.
(lots of these)

Timestamp: 20.12.2014 19:43:04
Warning: Error in parsing value for 'display'.  Declaration dropped.
Followed by another very long string

Warning: Unknown property '-moz-flex-basis'.  Declaration dropped.
(hundreds of the last two errors)

complaints about column-rule, column-gap, column-count (unknown
properties, Declaration dropped)

Warning: Unknown property '-moz-background-size'.  Declaration dropped.
(lots of these)

The full list would blow any size restrictions on this Newsgroup.
SM 2.30 and the current Firefox can both handle the page.
This affects Linux and Windows 7.

Should I be looking for 2.32 beta versions?  Or should I fallback to 2.30?
If its like usually what happens things get worse, than better. So go 
back to a none beta version and stay there. Developers now are more 
interested in getting out a new version as fast as they can and 
reliability goes out the window. Quality control no longer exist. 
Thankfully he SeaMonkey, usually try to do a better job. I use to use 
beta versions. But go tired of when send feedback or post bug reports 
not being listened to. So I just go with latest working version of 
SeaMonkey and hope for the best.


--
Phillip M. Jones, C.E.T.  If it's Fixed, Don't Break it
http://www.phillipmjones.netmailto:pjones...@comcast.net
http://phillipjones-cet.net/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: places.sqlite

2014-12-20 Thread Ant

On 12/19/2014 10:07 PM PT, NoOp typed:


I used to be able to copy my bookmarks from one PC to another by
simply
copying this file, but as of two releases ago this no longer works.
Any
idea why?


I was having problems with my places.sqlite in v2.29 after I upgraded
from v2.26.1. I manually share, like you, my file between Debian
stable's 64-bit SM and two Windows machines (XP Pro SP3 and 64-bit
7 EE
SP1). I noticed my histories got corrupted like missing events. I
had to
export my bookmarks and reimport as a new one/1. :(

Is this what you were having problems with? I am still with v2.26.1
and
afraid to upgrade. :/


That's the problem, yes.  I have to use the bookmarks.html file now to
import the bookmarks rather than places.sqlite.


Interesting. I wonder what happened after v2.26.1. This why I downgraded
and never went back up. :(


Eureka!  I found it!  There were FOUR files all prefixed by
places.sqlite including the original file.  If I delete all four and
copy in the places.sqlite from my Windows system to my Linux system,
it works!  I only have to copy that one file.

Again, this wasn't necessary until 2.29 came along, so I wonder what
changed??



Probably turned on temp files to speed-up the database:

https://www.sqlite.org/tempfiles.html


Hmm, I always copy with SM exited. Maybe I should try again after I make 
a SM backup! ;)

--
An anthill increases by accumulation. / Medicine is consumed by 
distribution. / That which is feared lessens by association. / This is 
the thing to understand. --Siddha Nagarjuna

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( ) If e-mailing, then axe ANT from its address if needed.
A song (i/wa)s playing on this computer: Trans-X - Living on Video 
(Re-Recorded)

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


Re: places.sqlite

2014-12-20 Thread Ed Mullen

Cruz, Jaime wrote on 12/19/2014 8:11 PM:

Ant wrote:

On 12/18/2014 3:36 AM PT, Cruz, Jaime typed:


I used to be able to copy my bookmarks from one PC to another by
simply
copying this file, but as of two releases ago this no longer works.
Any
idea why?


I was having problems with my places.sqlite in v2.29 after I upgraded
from v2.26.1. I manually share, like you, my file between Debian
stable's 64-bit SM and two Windows machines (XP Pro SP3 and 64-bit 7 EE
SP1). I noticed my histories got corrupted like missing events. I
had to
export my bookmarks and reimport as a new one/1. :(

Is this what you were having problems with? I am still with v2.26.1 and
afraid to upgrade. :/


That's the problem, yes.  I have to use the bookmarks.html file now to
import the bookmarks rather than places.sqlite.


Interesting. I wonder what happened after v2.26.1. This why I downgraded
and never went back up. :(


Eureka!  I found it!  There were FOUR files all prefixed by
places.sqlite including the original file.  If I delete all four and
copy in the places.sqlite from my Windows system to my Linux system,
it works!  I only have to copy that one file.

Again, this wasn't necessary until 2.29 came along, so I wonder what
changed??



Do not understand.  I don't care how many files contain places.sqlite in 
their filenames, copying the specific fiel places.sqlite should do the 
trick.


--
Ed Mullen
http://edmullen.net/
That's a hell of an ambition, to be mellow. It's like wanting to be 
senile. -  Randy Newman

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


Re: places.sqlite

2014-12-20 Thread Ant

On 12/20/2014 6:57 PM PT, Ed Mullen typed:

Do not understand.  I don't care how many files contain places.sqlite in
their filenames, copying the specific fiel places.sqlite should do the
trick.


Yeah, that is how I always did it on mine. Obviously, when SM is not 
running unless I forgot to do that. I think I get denied if I try to 
copy it if it was in used.

--
I'm not a worker ant. I'm like a queen. Or maybe a king. But you never 
hear of king ants. --Sean Bentley

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( ) If e-mailing, then axe ANT from its address if needed.
A song (i/wa)s playing on this computer: Teeel - Disk Go
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Silverlight not working with Flashblock 1.3.21 either

2014-12-20 Thread NoOp
On 12/20/2014 03:11 PM, EE wrote:
 Flashblock 1.3.21 was fixed up for SeaMonkey 2.31 as far as Flash and 
 HTML5 are concerned, but it is completely disabling Silverlight, just as 
 Flashblock 1.5.18 was doing.  There must be some other way to prevent 
 HTML5 from starting automatically if it has no play button.  The 
 question - what is that other way?
 

You can use prefbar to turn it (and flash) on  off with a single click.
I created a WebM (it is WebM ot HTML5) button:

{
  prefbar:info: {
formatversion: 3
  },
  prefbar:menu:enabled: {
items: [
  prefbar:button:webm
]
  },
  prefbar:button:webm: {
type: check,
label: WebM,
prefstring: media.webm.enabled,
topref: value,
frompref: value
  }
}

Save that to a text file  'import' into prefbar. You can then click to
enable/disable WebM.

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