Re: Browser no longer supported
Jan_Galt wrote: David E. Rossnobody@nowhere.invalid wrote : No, I was not asking for build:config. I want the user agent (UA) string that follows Build identifier when you select [Help About SeaMonkey] on the menu bar. No build identifier on mine. That's why I sent the other. Don't you see something like this? # Copyright © 1998-2011 by contributors to the Mozilla Project. # Read the licensing information for this product. # See the build configuration used for this version. # Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Region Blocking?
On Sat, 28 May 2011 09:14:57 -0400, in message mailman.1304.1306588726.9060.support-seamon...@lists.mozilla.org d...@kd4e.com wrote: So, other than some thuggish regime blocking free political speech the only reason an IP would be blocked by region would be to protect a copyright? No. 1. only reason ... would be to protect a copyright ... ? Please read my previous message where I also mention trademarks. Copyright is a major reason, but major is not the same as only. 2. blocking free political speech ... ? What is blocked can often be something else. 2.1 Family friendly ISPs block pornography. 2.2 The Protect IP bill before the US Congress would block sites which are dedicated to infringing activities. 3. regime blocking ... ? This case does not fit the facts you describe. 3.1 What you would see will not say not available in your region. 3.2 Such regimes do not care about your browser's IP address. COuld a poorly designed and/or implemented spam filter cause this as well? Email spam filtering will not cause this. A net nanny type web filter may block what you can see, but it will not say not available in your region. I have seen lists of countries that may be blocked in filters - based on a presumption of unusually high rates of spam - I think they were in filters designed for children where the children would be unlikely to have any need for access to those countries. The only spam I have received so far this week (phishing spam) has a bogus-Paypal URL which really goes to a Verizon customer in Dallas, Texas, USA. Filters to identify spam by URLs in the email, still filter only emails. They are not web browser filters; they do not prevent you pasting a BBC URL into your web browser. -- Kind regards Ralph ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Jan_Galt wrote: David E. Rossnobody@nowhere.invalid wrote : No, I was not asking for build:config. I want the user agent (UA) string that follows Build identifier when you select [Help About SeaMonkey] on the menu bar. No build identifier on mine. That's why I sent the other. anything when you enter about: typed into your navigation toolbar (without the inverted commas)? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: Paul B. Gallagher wrote: And of course a compliant site would get fewer calls, would it not? In a perfect world: Yes. In a world where M$ is in the browser market: Who knows? In the long term, if enough sites were compliant, M$ would have to shape up. In the real world, of course, the whip is in the other hand. :-( You're forgetting that not only is Internet Exploder not W3C- compliant, the various versions aren't even compatible with each other. What a steaming pile. Not forgetting, just choosing not to mention. Smart Web developers quote a base price for a W3C-compliant page and an additional charge for each version of M$'s crap that the client needs to support. Makes sense. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Need recommendations for Search Engines to be featured on Addons.Mozilla.Org (Bug 659088)
https://bugzilla.mozilla.org/show_bug.cgi?id=659088 https://addons.mozilla.org/en-US/seamonkey/search-tools/ looks empty because we have no featured search engines set. Someone needs to select those I went through the Sort by rating and sort by Downloads links and came up with a few: https://addons.mozilla.org/en-US/firefox/addon/wikilook/ (Extension) https://addons.mozilla.org/en-US/seamonkey/addon/youtube-10423/ (OpenSearch plugin) https://addons.mozilla.org/en-US/seamonkey/addon/mycroft-project/ (OpenSearch plugin) https://addons.mozilla.org/en-US/seamonkey/addon/longman-english-dictionary/ (OpenSearch plugin) Please report any problems with installing/using these addons in SeaMonkey 2.1pre. Also any additional suggestions welcome (must be listed on A.M.O. of course) Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Mime type of sent attachment
Hello, a colleague of mine has a problem with an attachment sent to certain addresses. The attachment is rejected because of a suspicious mime type. And I agree the the mime type is wrong. The document was first edited in MS word, then it was transfered to a linux machine and in OpenOffice.org, it was exported as PDF. When the message arrives to the remote machine, the attached PDF has the mime type application/x-msdownload. I tried to repeat the procedure and I sent the resulting PDF to myself, but the attachment got the correct mime type (application/pdf). I need to know who sets the mime type to the attachment. Is it SeaMonkey? Both of us are using the same version (2.0.14). Or the outgoing server? We both use the same machine. Or the receiving machine? How can I set the correct mime type? Hana ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
New version
Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? I feel that I would be quite happy to stay where I am. If it ain't broke . Just wondering Neil ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Missing messages
SeaMonkey 2.0.14 on Mandriva Linux 2009.0 on HP 6730 laptop. Latest problem has lasted for several weeks and concerns the display of previously read messages in the threads section of the Mail Newsgroups screen. See image:- http://www.albury.net.au/~dxmm/Uncounted_Unread.jpeg In the m.d.a.seamonkey group, as an example, I get some spam threads still showing up even months after I've read them. Here, you can see three threads (not bolded, so previously read) showing up, even thought I have the SM settings as:- Sort By, Order received, Ascending and Threaded Messages All, and, Threads with Unread Why do they persist?? How do I get rid of them?? -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
A new problem for me SM 2.0.14 WITH Windows 7
For some reason I have been having a problem sending emails. It will work for a while with no problem. I have zero problems receiving email, or newsgrops. But then all of a sudden I will not be able to send an email. Check to see if anything has changed in the newsgroups, mail setting for outgoing and nothing has changed. Funny thing is I can compare two computers side by side and one will send and the other one won't even though the setup for them are identical. Anyone else having this problem? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
Neil Winchurst wrote: Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? I feel that I would be quite happy to stay where I am. If it ain't broke . Just wondering Neil Neil, the only really good reason to buy a new car is that the old car is irrepairable broken. SM 2.0.14 is not brokenyet, but there will come a day that the small team of developers that work on SM will decide that SM 2.0.xx is not worth upgrading, so then you will have to move to SM 2.1.xx (or be unprotected from future problems). Or, as you've just moved to SM, you could start with SM 2.1 and not worry about having to learn the old SM 2.0.xx stuff!! -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
On 30/05/11 12:53, Neil Winchurst wrote: Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? I feel that I would be quite happy to stay where I am. If it ain't broke . Just wondering Neil You can still safely wait until the SeaMonkey 2.1 release is announced and maybe a little more, but not too long: once SeaMonkey 2.1 final gets released, support for SeaMonkey 2.0 won't last very long -- the (volunteer) SeaMonkey team just hasn't got enough resources to keep maintaining as many parallel versions of the software as does the Firefox team (many of whose members are paid employees of the Mozilla corporation). It is a testimony to the SeaMonkey community's enthusiasm that they are succeeding to maintain such a good-quality software product in spite of their relative lack of human and hardware resources. Once the users of SeaMonkey 2.0 start going over to SeaMonkey 2.1, there will be fewer and fewer people finding any possible remaining bugs in SeaMonkey 2.0 -- and fewer bugs found means fewer bugs fixed too. You can't prove that the software ain't broke, and any bug left in it is gonna bite you some day, maybe sooner -- maybe later. Currently, in addition to SeaMonkey 2.0 where AFAIK only severe security and stability bugs are still being fixed, the SeaMonkey team is maintaining two later code branches, namely SeaMonkey 2.1, which may be released any day now (the first release-candidate is already out and a second one is in the works), and SeaMonkey 2.2, which is still at the preliminary pre-alpha stage. IIUC, the underlying backend code is common between SeaMonkey 2.1 and Firefox 4.0.x, and between current builds of SeaMonkey 2.2a1pre and Firefox 7.0a1. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 101. U can read htis w/o ny porblm and cant figur eout Y its evn listd. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Need recommendations for Search Engines to be featured on Addons.Mozilla.Org (Bug 659088)
If I understood your request here are suggestions: The first two are privacy-respecting search engines. (Startpage uses Google searches but strips all user identifying data.) http://startpage.com or https://startpage.com Yippy is child-friendly and has lots of other resources. http://yippy.com -- Thanks! 73, KD4E David Colburn http://kd4e.com Have an http://ultrafidian.com day I don't google I SEARCH! STARTPAGE.com Shop Freedom-Friendly http://kd4e.com/of.html ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
Daniel wrote: Neil Winchurst wrote: Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? I feel that I would be quite happy to stay where I am. If it ain't broke . Just wondering Neil Neil, the only really good reason to buy a new car is that the old car is irrepairable broken. SM 2.0.14 is not brokenyet, but there will come a day that the small team of developers that work on SM will decide that SM 2.0.xx is not worth upgrading, so then you will have to move to SM 2.1.xx (or be unprotected from future problems). Or, as you've just moved to SM, you could start with SM 2.1 and not worry about having to learn the old SM 2.0.xx stuff!! I didn't mean that recently. I started with 2.0.13 and moved up from there when 2.0.14 came out. So I have been using SM for a while now. I understand that there will be no more development once 2.1 is the main version. But, as it is working fine for me, I feel that I should leave well alone. Thanks for the advice. Neil ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser History
On 5/29/11 9:58 PM, David E. Ross wrote: On 5/29/11 7:32 PM, David E. Ross wrote: On 5/15/11 8:01 AM, Robert Kaiser wrote: David E. Ross schrieb: The user interface to control the browser history has been removed from SeaMonkey 2.1RC1. Do any of the following preference variables still have any effect on controlling the history? No. We have been talking bout this multiple times here and there were blog posts about that automatic system that is in place there now, which we linked to. Robert Kaiser It would have been helpful if you had provided the URI to the blog post. In any case, this A Better Expiration Component Is Now Part of Places Module is really not better. It represents another situation in which a user control of the browsing experience has been eliminated. From comments on the blog post, I think other users are as upset as I am. See bug #660567 at https://bugzilla.mozilla.org/show_bug.cgi?id=660567. #660567 was closed as a duplicate of #643254. See https://bugzilla.mozilla.org/show_bug.cgi?id=643254. #643254 (initially a Firefox bug report) was closed as WontFix. I have submitted bug #660646. See https://bugzilla.mozilla.org/show_bug.cgi?id=660646. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
MCBastos schrieb: Interviewed by CNN on 29/05/2011 16:41, Robert Kaiser told the world: Paul B. Gallagher schrieb: For those few sites too stupid to sniff for Gecko, why not just lie to them and spoof FF? That's what 2.1 does. And it's not beta any more, it's RC, which means it's as good as release, with just minor adjustments to be made still. I sure hope that one of those adjustments is in the installer. Yes, the installer glitches are why it hasn't shipped as final yet. We fixed the default theme thing for the first build of RC2 but didn't even release that one as we found yet another problem with localizations and optional extensions that we need to do a second build for, and then RC2 should be there and hopefully will be converted to the actual final release a few days later. Robert Kaiser -- Note that any statements of mine - no matter how passionate - are never meant to be offensive but very often as food for thought or possible arguments that we as a community needs answers to. And most of the time, I even appreciate irony and fun! :) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SN 2.2a1pre and sharepoints
quick poll among nightlies users: Has anyone seen recently problems to perform changes on Windows SharePoints using SM2.2 ? I use at work Share Point 2007 and since about a week I can't anymore: - Add a new file into a sharepoint directory - add a new user into a sharepoint user group - etc... I use SM2.2a1pre as well as the FF nightlies (7.0a1). I tried with and without add-on, to the same result: Only SM 2.2a1pre is not able to upload a file to the sharepoints. I see a number of errors in the error console: here the two main ones: Error: Svc.Private is undefined Source File: resource://services-sync/engines/tabs.js Line: 336 (This is in the Seamonkey/omnijar directory) and: Error: WebForm_GetElementByTagName is not defined Source File: http://teams10.sharepoint.work-company.com/WebResource.axd?d=wKOvPAk4f8quUj2_8EtNSQ2t=634217698491748156 Line: 534 which is: var nodeTable = WebForm_GetElementByTagName(node, table); Thanks for anyone providing a hint at what to look for. Thanks ! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Interviewed by CNN on 30/05/2011 06:49, Paul B. Gallagher told the world: In the long term, if enough sites were compliant, M$ would have to shape up. In the real world, of course, the whip is in the other hand. :-( Actually, I understand that IE9 is reasonably compliant (not 100%, but near enough for most purposes), and the gap has been closing since IE7. IE6 and older are the really, really bad boys around, and even Microsoft is trying to make people switch: http://www.ie6countdown.com/ So it appears that they ARE shaping up. Unfortunately, there are still too many copies of IE6 in use. The reasons I still stay away from IE nowadays are not so much standards-compliance, but: 1- Security (MS has a dirt-poor track record in that) 2- IE is designed as a dumbest-user browser. I mean, they admitted that the IE9 layout assumes that very few users open more than 3 tabs. That's aiming for the low end of the market. Meanwhile, Mozilla was previewing a way to make it easier to manage dozens of tabs... 3- A general lack of trust in their design goals. Microsoft in the past tried to leverage IE into a MS-centric Web, and I have no doubts they will attempt to do that again as soon as they feel strong enough. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my orbital space station. *Added by TagZilla 0.066.2 running on Seamonkey 2.0.14 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
Interviewed by CNN on 30/05/2011 07:53, Neil Winchurst told the world: Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? Well, 2.1 will bring Seamonkey back to parity with Firefox, so roughly anything that Firefox now has and Seamonkey doesn't should come with 2.1. For instance: - Faster Javascript - Improved Video and Audio support (including WebM support) - Sync your bookmarks, history and such not only between different computers, but also with Mobile Firefox in your phone. (To myself, this is the most-eagerly-awaited new feature) - Improved standards-compliance in the rendering engine. and so forth. Of course, any major upgrade comes with a price. Many extensions will have to be re-tested and tagged as 2.1 compatible before most users will be able to use them again. Some might never be updated because the author abandoned the project. But OTOH, some extensions that depend on Firefox 4 stuff could now be ported to Seamonkey. Win some, lose some... -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Amstrad PCW. *Added by TagZilla 0.066.2 running on Seamonkey 2.0.14 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Need recommendations for Search Engines to be featured on Addons.Mozilla.Org (Bug 659088)
On Mon, 30 May 2011 10:04:59 -0400, d...@kd4e.com wrote: If I understood your request here are suggestions: The first two are privacy-respecting search engines. (Startpage uses Google searches but strips all user identifying data.) http://startpage.com or https://startpage.com Yippy is child-friendly and has lots of other resources. http://yippy.com In addition the search plugin has to be hosted on addons.mozilla.org as well. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
MCBastos wrote: Interviewed by CNN on 30/05/2011 06:49, Paul B. Gallagher told the world: In the long term, if enough sites were compliant, M$ would have to shape up. In the real world, of course, the whip is in the other hand. :-( Actually, I understand that IE9 is reasonably compliant (not 100%, but near enough for most purposes), and the gap has been closing since IE7. IE6 and older are the really, really bad boys around, and even Microsoft is trying to make people switch: http://www.ie6countdown.com/ So it appears that they ARE shaping up. Unfortunately, there are still too many copies of IE6 in use. Good to hear. The reasons I still stay away from IE nowadays are not so much standards-compliance, but: 1- Security (MS has a dirt-poor track record in that) Fair point. 2- IE is designed as a dumbest-user browser. I mean, they admitted that the IE9 layout assumes that very few users open more than 3 tabs. That's aiming for the low end of the market. Meanwhile, Mozilla was previewing a way to make it easier to manage dozens of tabs... Actually, they're right on this. There've been times when I had half-a-dozen tabs open, but those are rare, and I could live very easily without that capability. I have friends who say they have over a hundred tabs open routinely, but try as I may, I can't imagine a situation where I would want that, even if the browser supported it. I don't deny their taste, but it's not mine, and AFAIK it's not the taste of the vast majority of users. 3- A general lack of trust in their design goals. Microsoft in the past tried to leverage IE into a MS-centric Web, and I have no doubts they will attempt to do that again as soon as they feel strong enough. For me it's more a difference in taste than actual /distrust/ of their design goals. Sure, I distrust them on security, but that's a separate issue. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
Daniel wrote: Neil Winchurst wrote: Although not new to computers I am fairly new to SeaMonkey. I am using version 2.0.14. There has been a lot of chat about the new version 2.1. Since my version works just fine for me is there any real reason or advantage to moving up? I feel that I would be quite happy to stay where I am. If it ain't broke . Just wondering Neil Neil, the only really good reason to buy a new car is that the old car is irrepairable broken. Not so, there are lots of good reasons: 1) The old car costs more to maintain than it's worth, but the new car's maintenance will be free under warranty for years and years; 2) The old car is becoming too unreliable (can't depend on it to run without frequent repairs), but the new one will just run all day every day; 3) The new car has important features that the old car lacks (e.g., ABS brakes, better gas mileage); 4) The new car will help you score with the babes, but the old one just gets you laughed at; ;-) etc. For software, there are sometimes analogs to reasons 2) and 3) above. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Backups
What is json, how do I access it, and how do I use it? -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Jan_Galt wrote: JeffMjef...@email.com wrote : Jane_Galt wrote: I keep getting messages from Google search, Adwords and other places that my browser ( SM ) is no longer supported. When you encounter idiots who don't know how to build a website properly, you have options: 1) Avoid the idiots permanently 2) Complain to the idiots that they should learn how to do their jobs. 3) Spoof your browser's user agent. As has been said, the newest version of SeaMonkey does #3 by default. SeaMonkey users who *want* their browser to be counted accurately think that is a BAD idea and they will spoof **only** when absolutely necessary (allowing non-idiots to tally them properly). The choice is yours. You consider Google, one of the biggest sites in the world, to be idiots? not so much idiots, as foolish, Google is likely telling you your browser is not supported because Google wants to set all sorts of cookies and location awareness data in your browser, which SeaMonkey generally doesn't allow by default... someone w/more knowledge may back me up on this... sean i avoid google as much as humanly possible... ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: JeffM wrote : [...]idiots who don't know how to build a website properly[...] Jan_Galt wrote: You consider Google, one of the biggest sites in the world, to be idiots? Yup. This topic has been covered in this group innumerable times. YOU DON'T NEED TO SNIFF FOR BROWSERS. Just make your stupid pages W3C-compliant. If you are a pervert and insist on sniffing, DON'T then serve up a You-are-a-doodie-head page. Just serve up a standards-compliant page and let the chips fall where they may. (Frankly, if they are going to sniff then bitch, they should go ahead and flag M$'s crappy browsers as turds.) Disclaimer: Though I use Google all the time, the only time I see http://.google.com/ is after I have used their complaint form to bitch about something whereupon they use that URL as the landing page. I use a previously-visited Google numerical IP address already in my Address Bar and edit that URL to do a search.[1] As a rule, their JavaScript and other stupid improvements don't affect me. ...and I avoid DNS by going numeric. I hear that in your Goggle preferences you can also turn off much of the stupidity; again, I do it all manually and precisely. . . ...and corporate size doesn't seem to bring with it any particular smarts. Micros~1 is also a huge outfit, yet they are obviously too stupid to put out a product that doesn't suck. http://google.com/search?q=botnet+%22.13-million%22 . . [1] I also don't end up with a ridiculously long URL that I have to pare down anyway if I include it in a post. A keyboard macro app can then insert the text-address part back in. there was a popular tagline back in the day, still applies... -- The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
David E. Ross nobody@nowhere.invalid wrote : On 5/29/11 8:22 PM, Jan_Galt wrote: David E. Ross nobody@nowhere.invalid wrote : No, I was not asking for build:config. I want the user agent (UA) string that follows Build identifier when you select [Help About SeaMonkey] on the menu bar. No build identifier on mine. That's why I sent the other. No Build identifier could indicate you are sending a blank UA string to the Web server. If this is so, it might well be the cause of your problem. Well I didn't set it that way, it came with the browser. I have no idea how it gets set. -- - Jane Galt Without America there is no Free World. The reason that Progressivism-Socialism-Communism always fail, is that you eventually run out of other peoples' money. Obama and the Democrats: continuing the Cloward-Piven Progressive socialist agenda of borrowing, taxing and insanely spending the country into collapse and global socialism. To be a good democrat, you have to believe that businesses create oppression and governments create prosperity. The one thing that's being pushed in this country, is the motto: The harder I work, the more I owe society. The less I work, the more society owes me. We can't be a great country with that motto. - Charles Payne. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Paul B. Gallagher pau...@pbgdashtranslations.com wrote : Jan_Galt wrote: David E. Rossnobody@nowhere.invalid wrote : No, I was not asking for build:config. I want the user agent (UA) string that follows Build identifier when you select [Help About SeaMonkey] on the menu bar. No build identifier on mine. That's why I sent the other. Don't you see something like this? # Copyright © 1998-2011 by contributors to the Mozilla Project. # Read the licensing information for this product. # See the build configuration used for this version. # Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 OHH, ok, I thought it was a link. Well it's here today: SeaMonkey version 2.0.14 * Copyright © 1998-2011 by contributors to the Mozilla Project. * Read the licensing information for this product. * See the build configuration used for this version. * Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 I'm also having weird problems with Webshots. Every 2 days they tell me that I need to get the new version of Adobe Flash Player, I install it yet again, and it's fine until 2 days later. WTF?! -- - Jane Galt Without America there is no Free World. The reason that Progressivism-Socialism-Communism always fail, is that you eventually run out of other peoples' money. Obama and the Democrats: continuing the Cloward-Piven Progressive socialist agenda of borrowing, taxing and insanely spending the country into collapse and global socialism. To be a good democrat, you have to believe that businesses create oppression and governments create prosperity. The one thing that's being pushed in this country, is the motto: The harder I work, the more I owe society. The less I work, the more society owes me. We can't be a great country with that motto. - Charles Payne. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
I have a small business web site for my home business and make sure it's W3C. Doesn't seem to make a difference in the search results, but it's satisfying anyway. -- - Jane Galt Without America there is no Free World. The reason that Progressivism-Socialism-Communism always fail, is that you eventually run out of other peoples' money. Obama and the Democrats: continuing the Cloward-Piven Progressive socialist agenda of borrowing, taxing and insanely spending the country into collapse and global socialism. To be a good democrat, you have to believe that businesses create oppression and governments create prosperity. The one thing that's being pushed in this country, is the motto: The harder I work, the more I owe society. The less I work, the more society owes me. We can't be a great country with that motto. - Charles Payne. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Backups
David E. Ross wrote: What is json, how do I access it, and how do I use it? http://blog.mozilla.com/webdev/2009/02/12/native-json-in-firefox-31/ https://developer.mozilla.org/En/Using_JSON_in_Firefox http://kb.mozillazine.org/Bookmarks Hope those help. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Paul B. Gallagher wrote: Rick Merrill wrote: W3BNR wrote: On 5/29/2011 3:41 PM Robert Kaiser submitted the following: Paul B. Gallagher schrieb: For those few sites too stupid to sniff for Gecko, why not just lie to them and spoof FF? That's what 2.1 does. And it's not beta any more, it's RC, which means it's as good as release, with just minor adjustments to be made still. Robert Kaiser Personally I don't think we should have to lie about our browser. That said, I do use 'PrefBar' and spoof when I have to - but I still don't like to. I normally e-mail to whatever site it is that doesn't like SM (the webmaster or help desk) with the following text: == I think it is great that you encourage web sites to support SM! But think of all the mobile platforms that would also like support. Of course, the cheapest way to support all the browsers would be to write W3C compliant code, and pay one webmaster to do it instead of paying three or five or eight to write three or five or eight different versions. Most answers are: We only support the most common browsers. This is a necessary evil of support which means training expensive people to answer (ofteh silly) questions! And of course a compliant site would get fewer calls, would it not? Now if you could get Google and Microsoft on Board to do that, there would be no problem. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Jan_Galt wrote: JeffMjef...@email.com wrote : Jane_Galt wrote: I keep getting messages from Google search, Adwords and other places that my browser ( SM ) is no longer supported. When you encounter idiots who don't know how to build a website properly, you have options: 1) Avoid the idiots permanently 2) Complain to the idiots that they should learn how to do their jobs. 3) Spoof your browser's user agent. As has been said, the newest version of SeaMonkey does #3 by default. SeaMonkey users who *want* their browser to be counted accurately think that is a BAD idea and they will spoof **only** when absolutely necessary (allowing non-idiots to tally them properly). The choice is yours. You consider Google, one of the biggest sites in the world, to be idiots? Yes. They are using the same tactics Microsoft used Years ago did. Only thing they didn't sign on to W3C like MS did. They signed on so they could report back to headquarters so the could do everything to break the rules. So web designers would have to create two or mor sets of code. Google is out take all the bucks they can and kill of any other browser out there. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Recovery from lost mail and newsgroup accounts question
Dick Hoffman wrote: We are running SM 2.0.14 on a Windows XP-SP3 system. My wife rather casually advised my this morning that all our mail accounts were gone. When I tried to start SM Mail, I got the New Account Setup Wizard panel rather than the normal display of all our mail and newsgroup accounts. I tried using Mozbackup to save a copy of the profile but it said the profile was corrupted. So I manually copied the profile to a new folder and then restored the profile from a copy made a few days ago during our normal backup run. I started SM Mail and all our accounts were back. Some emails since the backup were, of course, lost but we can retrieve them if we need to. I have no idea what corrupted the profile. Since 2.1 is coming out next week I don't think I'll try to file a Bugzilla report. My question is was the action I took the best way to recover from the problem or was there some other, maybe simpler, action I should have taken? Dick dunno of any simpler method, good that you had a recent copy of your back up... most folks don't... sean ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Need recommendations for Search Engines to be featured on Addons.Mozilla.Org (Bug 659088)
Philip Chee wrote: https://bugzilla.mozilla.org/show_bug.cgi?id=659088 https://addons.mozilla.org/en-US/seamonkey/search-tools/ looks empty because we have no featured search engines set. Someone needs to select those I went through the Sort by rating and sort by Downloads links and came up with a few: https://addons.mozilla.org/en-US/firefox/addon/wikilook/ (Extension) https://addons.mozilla.org/en-US/seamonkey/addon/youtube-10423/ (OpenSearch plugin) https://addons.mozilla.org/en-US/seamonkey/addon/mycroft-project/ (OpenSearch plugin) https://addons.mozilla.org/en-US/seamonkey/addon/longman-english-dictionary/ (OpenSearch plugin) Please report any problems with installing/using these addons in SeaMonkey 2.1pre. Also any additional suggestions welcome (must be listed on A.M.O. of course) Phil how about Yahoo!, altavista to name a couple. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
sean bean wrote: Google is likely telling you your browser is not supported because Google wants to set all sorts of cookies and location awareness data in your browser, Nope. which SeaMonkey generally doesn't allow by default Nope. While I laud your suspicion of megacorporations, your accusations about Google are way off the mark. The truth is much simpler: 1) Google has embraced Web 2.0. 2) Google employees don't know the *basics* of what they are doing. Some time back, Google announced that their efforts going forward would require users to have a browser with good support for HTML 4, CSS, and JavaScript.[1] Most of the headlines of that time specifically mention Internet Exploder 6. Google is sniffing for browsers and blackballing those it deems unworthy of accessing its pages. Again, sniffing is a stupid practice; using it *incorrectly* is monumentally stupid. It is obvious that the Google employees who implemented this are unaware that the **proper** way to sniff is to look for **the HTML rendering engine** in the user agent string (Trident, WebKit, Gecko, Presto, etc.). They are instead showing their ignorance by looking for browser names. Again, this is WRONG WRONG WRONG WRONG WRONG. i avoid google as much as humanly possible... Mostly, I adore Google. Mostly, they get it and mostly they get it right (considering all the SEO asswipes who try to game the system). This instance is a failure of management to oversee workers; quite possibly a failure of managers to understand the job better than their underlings. . . [1] As I mentioned, to just do searches, you can turn off most of that stupid shit.[2][3] OTOH, Google Docs, viewing PDFs as Web pages, etc. requires the bells and whistles. [2] When I recently used a Web terminal at the library, I didn't remember any of Google's numerical IP addresses and couldn't access the Google preferences either. What an irritating experience. Using Windoze (with right-click totally disabled by the experts) gave me a rash as well. Using Internet Exploder also sucked. (M$ tried to imitate Mozilla's tabs--and failed.) [3] I haven't yet found a Userscript that gets rid of the wasted space on results pages down the left side of my narrow screen. 8-| ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: Google is sniffing for browsers and blackballing those it deems unworthy of accessing its pages. Again, sniffing is a stupid practice; using it *incorrectly* is monumentally stupid. It is obvious that the Google employees who implemented this are unaware that the **proper** way to sniff is to look for **the HTML rendering engine** in the user agent string (Trident, WebKit, Gecko, Presto, etc.). They are instead showing their ignorance by looking for browser names. Again, this is WRONG WRONG WRONG WRONG WRONG. Google(and some others also) don't care about your position - so - no way for a change ... ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: Google is sniffing for browsers and blackballing those it deems unworthy of accessing its pages. Again, sniffing is a stupid practice; using it *incorrectly* is monumentally stupid. It is obvious that the Google employees who implemented this are unaware that the **proper** way to sniff is to look for **the HTML rendering engine** in the user agent string (Trident, WebKit, Gecko, Presto, etc.). They are instead showing their ignorance by looking for browser names. Again, this is WRONG WRONG WRONG WRONG WRONG. Ray_Net wrote: Google(and some others also) don't care about your position - so - no way for a change ... My position is standard practice --for those who don't have their heads up their asses. As previously mentioned, you can contact the site/developer and discover exactly how far up there they have that. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: sean bean wrote: Google is likely telling you your browser is not supported because Google wants to set all sorts of cookies and location awareness data in your browser, Nope. which SeaMonkey generally doesn't allow by default Nope. While I laud your suspicion of megacorporations, your accusations about Google are way off the mark. The truth is much simpler: 1) Google has embraced Web 2.0. 2) Google employees don't know the *basics* of what they are doing. Some time back, Google announced that their efforts going forward would require users to have a browser with good support for HTML 4, CSS, and JavaScript.[1] Most of the headlines of that time specifically mention Internet Exploder 6. Google is sniffing for browsers and blackballing those it deems unworthy of accessing its pages. Again, sniffing is a stupid practice; using it *incorrectly* is monumentally stupid. It is obvious that the Google employees who implemented this are unaware that the **proper** way to sniff is to look for **the HTML rendering engine** in the user agent string (Trident, WebKit, Gecko, Presto, etc.). They are instead showing their ignorance by looking for browser names. Again, this is WRONG WRONG WRONG WRONG WRONG. i avoid google as much as humanly possible... Mostly, I adore Google. Mostly, they get it and mostly they get it right (considering all the SEO asswipes who try to game the system). This instance is a failure of management to oversee workers; quite possibly a failure of managers to understand the job better than their underlings. . . [1] As I mentioned, to just do searches, you can turn off most of that stupid shit.[2][3] OTOH, Google Docs, viewing PDFs as Web pages, etc. requires the bells and whistles. [2] When I recently used a Web terminal at the library, I didn't remember any of Google's numerical IP addresses and couldn't access the Google preferences either. What an irritating experience. Using Windoze (with right-click totally disabled by the experts) gave me a rash as well. Using Internet Exploder also sucked. (M$ tried to imitate Mozilla's tabs--and failed.) [3] I haven't yet found a Userscript that gets rid of the wasted space on results pages down the left side of my narrow screen.8-| google's corporate motto is don't be evil but this is now opposite land... they are 2011's version of 1984's ministry of truth... i refuse to use them, scroogle is my search engine of choice, i've opted out of analytics, don't use google docs or gmail, i don't store anything in the cloud and i've never ever used my real name anywhere on the internet since going online in 1994.. sean ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SN 2.2a1pre and sharepoints
Without giving you too much (directly) to go on, can you try with SeaMonkey, with the UA Switcher extension the following user agent strings: * Firefox 7a1 (the default Firefox UA) * SeaMonkey 2.2a1 (note without pre) * [something else than Gecko or IE, say chrome or Opera] I suspect its just a bad User Agent Sniffing in the webpage. But hard to tell when I don't know what sharepoint is in the first place. ~Justin Wood (Callek) On 5/30/2011 11:41 AM, dominique wrote: quick poll among nightlies users: Has anyone seen recently problems to perform changes on Windows SharePoints using SM2.2 ? I use at work Share Point 2007 and since about a week I can't anymore: - Add a new file into a sharepoint directory - add a new user into a sharepoint user group - etc... I use SM2.2a1pre as well as the FF nightlies (7.0a1). I tried with and without add-on, to the same result: Only SM 2.2a1pre is not able to upload a file to the sharepoints. I see a number of errors in the error console: here the two main ones: Error: Svc.Private is undefined Source File: resource://services-sync/engines/tabs.js Line: 336 (This is in the Seamonkey/omnijar directory) and: Error: WebForm_GetElementByTagName is not defined Source File: http://teams10.sharepoint.work-company.com/WebResource.axd?d=wKOvPAk4f8quUj2_8EtNSQ2t=634217698491748156 Line: 534 which is: var nodeTable = WebForm_GetElementByTagName(node, table); Thanks for anyone providing a hint at what to look for. Thanks ! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.1 RC
On 5/29/2011 10:59 PM, David E. Ross wrote: The major bug reports: #658936 athttps://bugzilla.mozilla.org/show_bug.cgi?id=658936 Fwiw, our handling here is all toolkit, but I don't know enough to delve deeply on this #659731 athttps://bugzilla.mozilla.org/show_bug.cgi?id=659731 As you cite in that bug, it could be a Core issue, but I would be interested if you (or anyone) can come up with more reliable proof of concepts and/or triage of that one. I somehow suspect we are saving this internally on a per-site basis since our change to newer Gecko. But I'm not sure, and I wouldn't know why the pref is not carried forward in future sessions. [I don't typically zoom webpages, unless its temporary anyway]. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: New version
On 5/30/2011 9:17 AM, Tony Mechelynck wrote: and between current builds of SeaMonkey 2.2a1pre and Firefox 7.0a1. Fwiw, SeaMonkey 2.2 will soon be only comprable to Firefox 5... we're just getting ready to bump version numbers there to reflect reality. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
On 5/29/2011 4:25 PM, W3BNR wrote: Personally I don't think we should have to lie about our browser. We (SeaMonkey Council) fully agree with you. That said, our users are higher priority. KaiRo (longtime project member, and Council member) has proposed, years ago, a theoretical solution to the issue (back when Firefox was not even recognized by websites, fwiw), the problem is we don't have the backend gecko support atm, and it would be A LOT of work to try and implement on our own. If the support is ever there, we'll gladly use it though. -- ~Justin Wood SeaMonkey Release Engineer, SeaMonkey Council. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
MCBastos wrote: Interviewed by CNN on 30/05/2011 06:49, Paul B. Gallagher told the world: That's cute. 8-) if enough sites were compliant, M$ would have to shape up. Actually, I understand that IE9 is reasonably compliant The phrase you seek is *inching upward* (after YEARS of hobbling the Web). the gap has been closing since IE7. ...mostly at a snail's pace. Internet Exploder didn't pass Acid TWO until IE EIGHT fercrisesake. IE7 and IE8 sucked at Acid3; IE9 was a quantum leap there. http://en.wikipedia.org/wiki/Acid3#Desktop_browsers_2 (not 100%, but near enough for most purposes), Grudgingly complying because they were facing death. The only place I'll give M$ any points is in the each-tab-is-a-separate-process thing. (Ancient) Mozilla is still playing catch-up there; having everything freeze when one tab craps out really sucks. So it appears that they ARE shaping up. You left out the phrase dragged kicking and screaming. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
JeffM wrote: The truth is much simpler: 1) Google has embraced Web 2.0. 2) Google employees don't know the *basics* of what they are doing. sean bean wrote: google's corporate motto is don't be evil but this is now opposite land... Web 2.0 is evil?? ...or have you wandered off-topic without leaving a trail of breadcrumbs for anyone to follow? I'll grant you that Web 2.0 is resource-intensive and it is often unnecessary to e.g. use JavaScript but you need to give some clue what you're talking about.. they are 2011's version of 1984's ministry of truth... You are going to have to be a lot more specific than that. I also suggest you see a psychiatrist about your paranoia. Don't want them to track you? Block their cookies. Done. Hand-waving averted. For my Google stuff that needs a cookie, I simply use a separate profile. i refuse to use them, scroogle is my search engine of choice, Heh. Disingenuous much? You *use* Google; you just go thru a proxy. I'm crazy about Google's Cached pages. You can't get those with going thru Google's site. If they want my (dynamic) IP address, they can have it. i've opted out of analytics, Y'mean there is someone somewhere who allows that junk on his box? don't use google docs or gmail, Gmail is pretty awesome. If I did collaborative document stuff, I'd probably use GDocs. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Browser no longer supported
Justin Wood (Callek) wrote: On 5/29/2011 4:25 PM, W3BNR wrote: Personally I don't think we should have to lie about our browser. We (SeaMonkey Council) fully agree with you. That said, our users are higher priority. KaiRo (longtime project member, and Council member) has proposed, years ago, a theoretical solution to the issue (back when Firefox was not even recognized by websites, fwiw), the problem is we don't have the backend gecko support atm, and it would be A LOT of work to try and implement on our own. If the support is ever there, we'll gladly use it though. FWIW, it would be a notational equivalent if all Gecko browsers identified themselves as Firefox instead of Gecko. Then the websites that sniff for Firefox would all get it right. I hate to punish the ones that have been getting it right all along by forcing them to adjust, but if we have to choose between hoping the stupid webmasters will adjust and hoping the smart webmasters will adjust, the smart money will be on the smart webmasters. Keep in mind that the current squabbling doesn't serve the end users, but resolving it will. It hardly matters what word we use in the UA string, as long as it's standardized. We could just as easily call the rendering engine Toaster, as long as everyone agrees on it. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.1 RC
On 5/30/11 7:26 PM, Justin Wood (Callek) wrote: On 5/29/2011 10:59 PM, David E. Ross wrote: The major bug reports: #658936 athttps://bugzilla.mozilla.org/show_bug.cgi?id=658936 Fwiw, our handling here is all toolkit, but I don't know enough to delve deeply on this I updated #658936 to Toolkit/Password Manager. #659731 athttps://bugzilla.mozilla.org/show_bug.cgi?id=659731 As you cite in that bug, it could be a Core issue, but I would be interested if you (or anyone) can come up with more reliable proof of concepts and/or triage of that one. I somehow suspect we are saving this internally on a per-site basis since our change to newer Gecko. But I'm not sure, and I wouldn't know why the pref is not carried forward in future sessions. [I don't typically zoom webpages, unless its temporary anyway]. Several things about zooming, not all merely affecting tabs -- 1. I can reliably recreate the problem with zooming a parent tab affecting its first child and vice versa. 2. I would expect that, when I close a tab, all zooming within that tab would be forgotten. This is not happening. 3. I would expect that, when I zoom a page and it is the ONLY tab, that the zooming would remain in effect until I either cancel the zooming or terminate SeaMonkey. Instead, zooming seems to follow the domain of the page to which it originally applied. If I select a link from a zoomed page to a Web page at another domain, zooming is not applied. If I then go to another page at the same domain as the originally zoomed page, zooming is again applied. Without keeping track of what domain I am about to visit, this is extremely annoying. (Actually, it is very annoying even if I keep track of the domains.) 4. I would expect that, when I terminate SeaMonkey (all instances), all zooming would be forgotten. This is not happening. Zooming is remembered (as in #3 above), for the domain in which it was applied during a previous session. In SeaMonkey 2.0.14, zooming applied in only one tab. It remained in effect for all pages viewed in that tab until cancelled. It also remained in effect until the tab was closed or the browser was terminated, after which zooming was forgotten. It appears that the zooming is applied to a domain and is remembered for that domain. This would explain the transfer of zooming from a parent tab to a child tab. I only tested with pages all from the same domain when I wrote the bug report. I am closing bug #658936 and submitting a new bug that better describes the problem and presents a less complicated test case. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.1 RC
David E. Ross wrote: On 5/30/11 7:26 PM, Justin Wood (Callek) wrote: On 5/29/2011 10:59 PM, David E. Ross wrote: The major bug reports: #658936 athttps://bugzilla.mozilla.org/show_bug.cgi?id=658936 Fwiw, our handling here is all toolkit, but I don't know enough to delve deeply on this I updated #658936 to Toolkit/Password Manager. #659731 athttps://bugzilla.mozilla.org/show_bug.cgi?id=659731 As you cite in that bug, it could be a Core issue, but I would be interested if you (or anyone) can come up with more reliable proof of concepts and/or triage of that one. I somehow suspect we are saving this internally on a per-site basis since our change to newer Gecko. But I'm not sure, and I wouldn't know why the pref is not carried forward in future sessions. [I don't typically zoom webpages, unless its temporary anyway]. Several things about zooming, not all merely affecting tabs -- 1. I can reliably recreate the problem with zooming a parent tab affecting its first child and vice versa. 2. I would expect that, when I close a tab, all zooming within that tab would be forgotten. This is not happening. 3. I would expect that, when I zoom a page and it is the ONLY tab, that the zooming would remain in effect until I either cancel the zooming or terminate SeaMonkey. Instead, zooming seems to follow the domain of the page to which it originally applied. If I select a link from a zoomed page to a Web page at another domain, zooming is not applied. If I then go to another page at the same domain as the originally zoomed page, zooming is again applied. Without keeping track of what domain I am about to visit, this is extremely annoying. (Actually, it is very annoying even if I keep track of the domains.) 4. I would expect that, when I terminate SeaMonkey (all instances), all zooming would be forgotten. This is not happening. Zooming is remembered (as in #3 above), for the domain in which it was applied during a previous session. In SeaMonkey 2.0.14, zooming applied in only one tab. It remained in effect for all pages viewed in that tab until cancelled. It also remained in effect until the tab was closed or the browser was terminated, after which zooming was forgotten. It appears that the zooming is applied to a domain and is remembered for that domain. This would explain the transfer of zooming from a parent tab to a child tab. I only tested with pages all from the same domain when I wrote the bug report. I am closing bug #658936 and submitting a new bug that better describes the problem and presents a less complicated test case. You not using an extension called NoSquint? In NoSquint you adjust zoom level of everything, and also fonts separately. once you set it. remembers setting for each website that are tweaked differently otherwise yo set in General. Usually the in General setting are enough. I couldn't read anything on websites without the aid of NoSquint. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.1 RC
On 5/30/11 8:34 PM, PhillipJones wrote: David E. Ross wrote: On 5/30/11 7:26 PM, Justin Wood (Callek) wrote: On 5/29/2011 10:59 PM, David E. Ross wrote: The major bug reports: #658936 athttps://bugzilla.mozilla.org/show_bug.cgi?id=658936 Fwiw, our handling here is all toolkit, but I don't know enough to delve deeply on this I updated #658936 to Toolkit/Password Manager. #659731 athttps://bugzilla.mozilla.org/show_bug.cgi?id=659731 As you cite in that bug, it could be a Core issue, but I would be interested if you (or anyone) can come up with more reliable proof of concepts and/or triage of that one. I somehow suspect we are saving this internally on a per-site basis since our change to newer Gecko. But I'm not sure, and I wouldn't know why the pref is not carried forward in future sessions. [I don't typically zoom webpages, unless its temporary anyway]. Several things about zooming, not all merely affecting tabs -- 1. I can reliably recreate the problem with zooming a parent tab affecting its first child and vice versa. 2. I would expect that, when I close a tab, all zooming within that tab would be forgotten. This is not happening. 3. I would expect that, when I zoom a page and it is the ONLY tab, that the zooming would remain in effect until I either cancel the zooming or terminate SeaMonkey. Instead, zooming seems to follow the domain of the page to which it originally applied. If I select a link from a zoomed page to a Web page at another domain, zooming is not applied. If I then go to another page at the same domain as the originally zoomed page, zooming is again applied. Without keeping track of what domain I am about to visit, this is extremely annoying. (Actually, it is very annoying even if I keep track of the domains.) 4. I would expect that, when I terminate SeaMonkey (all instances), all zooming would be forgotten. This is not happening. Zooming is remembered (as in #3 above), for the domain in which it was applied during a previous session. In SeaMonkey 2.0.14, zooming applied in only one tab. It remained in effect for all pages viewed in that tab until cancelled. It also remained in effect until the tab was closed or the browser was terminated, after which zooming was forgotten. It appears that the zooming is applied to a domain and is remembered for that domain. This would explain the transfer of zooming from a parent tab to a child tab. I only tested with pages all from the same domain when I wrote the bug report. I am closing bug #658936 and submitting a new bug that better describes the problem and presents a less complicated test case. You not using an extension called NoSquint? In NoSquint you adjust zoom level of everything, and also fonts separately. once you set it. remembers setting for each website that are tweaked differently otherwise yo set in General. Usually the in General setting are enough. I couldn't read anything on websites without the aid of NoSquint. No, I'm not using NoSquint. I use PrefBar and its basic Font- and Font+ buttons (with the space between the word Font and the signs removed). I also installed the Font= button, which unzooms when I forget how many times I have selected Font+ or Font-. However, I have replicated the problem just by going to the menu bar and selecting [View Text Zoom etc]. I have also replicated the problem in Safe Mode. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Zooming Problem Resolved [was Re: SeaMonkey 2.1 RC]
On 5/30/11 8:53 PM, David E. Ross wrote: On 5/30/11 8:10 PM, I previously wrote in part: It appears that the zooming is applied to a domain and is remembered for that domain. This would explain the transfer of zooming from a parent tab to a child tab. I only tested with pages all from the same domain when I wrote the bug report. I am closing bug #658936 and submitting a new bug that better describes the problem and presents a less complicated test case. I have closed bug #659731 and submitted bug #660735. See https://bugzilla.mozilla.org/show_bug.cgi?id=660735. The problem cited in bug #659731 was caused when the default value of hidden preference browser.zoom.siteSpecific changed from false to true with SeaMonkey 2.1. I have closed the bug report. How many other problems that I am seeing are caused by changed default values of preference variables? -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
