Re: seamonkey UI
On 12/20/2015 11:34 AM, Paul Gheno wrote: > Hello everybody and thank you for your (interesting) answers. > > 10-15 years ago, users had to deal with UI and adapt theirs habits to it. > Nowadays, UIs fit to people habits... this is such a huge difference. > > What I love with SeaMonkey is the merging with both a web browser and an > email client. So clever ... > > Well, in my opinion, something wich is dedicated to deal with a lot of > users have to stick to the rule of the 90-90, that means suitable for > 90% of the population enven a 90yo grandma ! > (the 90-90 is a personal rule, not a covention) > > A great exemple of 90-90 is an ATM interface. > > Designing something, even a chair, is not about drawing something, this > happens at the last stage. > Designing something is asking questions and collecting answers first. > > Who the users are ? > Which is the program's interest ? > Which problems are intended to be solved ? > Which are the user's issues ? > What do they like or dislike in a such program ? > Are the users ready to "learn" something new (a really love this one !) > > As you understand, the main goal is to understand the "User" > > At stage two there is others (technicals) questions : > what about accessibility ? > what about colors, elements place, elements size ? > How to reduce the number of clicks/actions to the strictly minimum > How to collect stats and datas ? > > Dealing with a 90-90 interface means find a balance between all thoses > parameters and of course ... is a tricky game ... but a game I love :) > > I do not want to be rude, to be critical, but the actual seamonkey UI is > far away from the 90-90 rule and I let you check why. > As a web navigator, I believe that is a good idea to stick as close as > possible to this kind of rule. > > To conclude, I would make saemonkey my favorite web browser and not > switching from Chrome to FF to SM, using best tools of each... > > I would like to help the seamonkey team to think, develop, and implement > thoses questions, to make an even better SM. > > -> How to ? > -> Who could I contact ? > > Thank you very much for reading guys, indeed. > Thank you for your next messages... > > Paul > Paul, I think it is excellent that you have an interest in the software, the skillset, and a willingness contribute to its development. In addition to this list you might try contacting several of the mailing lists involved with the development of Mozilla projects. https://lists.mozilla.org/listinfo Don't give up on this list. Developers do keep track of the traffic here, but it may not be their main focus. Also, given the year-end holidays, it may take a while for you to get the response you are looking for. Best wishes, Kevin __ > support-seamonkey mailing list > support-seamonkey@lists.mozilla.org > https://lists.mozilla.org/listinfo/support-seamonkey > ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Cookie or sniffing issue:?
On 11/23/2015 05:12 AM, Arnie Goetchius wrote: > Paul B. Gallagher wrote: >> Mason83 wrote: >> >>> On 23/11/2015 04:34, Paul B. Gallagher wrote: >>> Wish I knew how your configuration differed from mine. But with hundreds of user-configurable prefs, where to look? >>> >>> Does it work with a fresh profile with no add-ons? >>> >>> If so, then you can use diff to locate the differences. >> >> A quick test in Safe Mode with all add-ons disabled and cookie prefs set to >> slut >> mode (accept everything from everyone) was unhelpful -- same issue. >> >> Are there other things in the profile that could be relevant? >> >> Just because the error message blames cookie handling I'm not assuming it's a >> cookie issue. Lots of programmers write error-handling routines that blame >> the >> wrong party. >> > FWIW, I can access that website without the error message using my regular > profile. However, if use the Default Seamonkey profile, I get the same problem > you get. I have no idea what I might have added or changed in my regular > profile > to make it work okay. > ___ Because I am one of those who can access the site without errors, I'll document the cookie entries in config. Under "about:config" and searching for 'cookie' I have the following: extensions.proxytool.clear_cookies_on_new_proxy;false extensions.proxytool.clear_cookies_on_new_window;false network.cookie.alwaysAcceptSessionCookies;false network.cookie.cookieBehavior;1 network.cookie.lifetime.days;90 network.cookie.lifetimePolicy;2 network.cookie.prefsMigrated;true network.cookie.thirdparty.sessionOnly;false pref.advanced.cookies.disable_button.view_cookies;false privacy.item.cookies;true services.sync.prefs.sync.network.cookie.cookieBehavior;true services.sync.prefs.sync.network.cookie.lifetimePolicy;true services.sync.prefs.sync.privacy.item.cookies;true None of those are changed in my user.js file. Kevin ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Cookie or sniffing issue:?
On 11/22/2015 06:55 PM, Paul B. Gallagher wrote: > 1) Has the webmaster miscoded his cookie-setting/reading routine, > causing it to fail? This doesn't happen with Internet Exploiter 11. > > 2) Could the webmaster be using a bad sniffer that rejects SM out of hand? > > 3) Is there an issue with SeaMonkey's processing of cookies, such that > it doesn't handle some cookies even though it says it will? > > Thanks. > I'm using: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38. Cookie Acceptance Policy: Allow cookies for the originating website only (no third-party cookies) Cookie Retention Policy: Accept for the current session only I have two cookies for: www.dot3.state.pa.us and two cookies for: www.dmv.pa.gov The site is also happy with me entering from Los Angeles. Obviously, I haven't put is a title # or plate # etc. Anthing else I can try for you? Kevin ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey obsolete?
On 06/19/2015 01:56 PM, Paul B. Gallagher wrote: Kevin L. Hill wrote: On 06/18/2015 10:31 PM, Paul B. Gallagher wrote: Steps to reproduce? Thank you Paul, Start Seamonkey 2.33.1 in safe mode with addons disabled. mega.co.nz I'm using 2.33.1 and don't need to rule out add-ons as suspects since I don't have the issue (no crime therefore no culprit). I contacted Mega (since they asked so nicely in the error message) and in their reply, they asked me to ...check whether SeaMonkey disables localStorage by default? Open the JavaScript console and type localStorage.length If you get 0 as a result, it is enabled, and the bug is on our side. I get 0. But I also get a prompt from SeaMonkey saying the page (http://jsconsole.com/) is asking to store data locally, and offering the options [Always Allow], [Never for This Site], and [Not Now]. I ignored it. Using Tools - Web Development - Error Console, I typed in localStorage.length and I get an error message TypeError: localStorage is null exactly as Mega reports in their error message. Thanks again for your help. OK, I opened the Error Console and cleared the listing, then loaded mega.co.nz, which generated dozens of errors and warnings (I didn't bother counting, but I'd guess it was over 100). I filtered on localStorage.length and they all vanished -- there were no messages containing that string. Have you checked your permissions for mega.co.nz? In the Data Manager, enter that string in the search window at upper left. I see only one cookie that they saved, geoip, and no restrictions on what they can do other than my general policies. This ended up at the bottom of my email but I know better than to bury the lede. SOLVED (I think) !! Searching about:config for 'storage' in both Seamonkey and Firefox I found that 'dom.storage.enabled' was set to True in Firefox and False in Seamonkey. Setting Seamonkey to match Firefox, I am able to load Mega.co.nz in both browsers. Found this after the fact: http://www.techsupportalert.com/content/how-disable-new-kind-cookie-called-dom-storage.htm Apparently this setting cannot be changed from the GUI (hope I'm wrong about this). My original response to your email: Starting with the error console open and cleared the listing and loaded mega.co.nz. The browser displays the error which I have listed earlier about not being able to initialize local storage. I cleared the error message The the error console adds the error: TypeError: localStorage is null https://mega.co.nz/secureboot.js?r=1434585458 followed by 7 warning messages. Like you the only permission entry is in Data Manager for geoip. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey obsolete?
On 06/18/2015 05:26 PM, Rinaldi wrote: Richard Owlett decreed, Read These Runes!: Kevin L. Hill wrote: On 06/18/2015 03:59 PM, Paul in Houston, TX wrote: Bill DeCoster wrote: I find myself needing to use IE other programs more and more because of issues with it. What's the point if nothing works? ?? Mine works perfectly. I never have a problem with it. SM 2.26.1 I encountered a site today that may serve as one 'real world' example. Mega.co.nz offers end-to-end encryption for data, claiming that all encryption/decryption is done on the local computer, not by their servers, and that they do not possess the keys needed to decrypt the data. On Seamonkey: Mega.co.nz gives me the following error: Sorry, we were unable to initialize the browser's local storage, either you're using an outdated browser or it's something from our side. If you think it's our fault, please report the issue back to us. Reason: localStorage is null Browser: mozilla/5.0 (x11; linux x86_64; rv:36.0) gecko/20100101 firefox/36.0 seamonkey/2.33.1 More info on local storage in the browser is here: http://www.infoworld.com/article/2625216/web-browsers/html5-in-the-browser--local-data-storage.html The page loads perfectly in Firefox: 38.0.5 Kevin Hill Long Beach, CA https://validator.w3.org/ reports 6 errors ;/ 'nuff said? But it loads perfectly here: User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/2015061208 Firefox/41.0 SeaMonkey/2.38a1-rjm Thank you. If nothing breaks between now and the release of SeaMonkey 2.38 then this issue will be resolved. I appreciate the feedback. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey obsolete?
On 06/18/2015 10:31 PM, Paul B. Gallagher wrote: Kevin L. Hill wrote: I encountered a site today that may serve as one 'real world' example. Mega.co.nz offers end-to-end encryption for data, claiming that all encryption/decryption is done on the local computer, not by their servers, and that they do not possess the keys needed to decrypt the data. On Seamonkey: Mega.co.nz gives me the following error: Sorry, we were unable to initialize the browser's local storage, either you're using an outdated browser or it's something from our side. If you think it's our fault, please report the issue back to us. Reason: localStorage is null Browser: mozilla/5.0 (x11; linux x86_64; rv:36.0) gecko/20100101 firefox/36.0 seamonkey/2.33.1 More info on local storage in the browser is here: http://www.infoworld.com/article/2625216/web-browsers/html5-in-the-browser--local-data-storage.html The page loads perfectly in Firefox: 38.0.5 Which page? I went to their home page and it loaded perfectly. I also clicked the link at bottom to learn more, and that loaded perfectly. Steps to reproduce? Thank you Paul, Start Seamonkey 2.33.1 in safe mode with addons disabled. mega.co.nz Error: Sorry, we were unable to initialize the browser's local storage, either you're using an outdated browser or it's something from our side. If you think it's our fault, please report the issue back to us. Reason: localStorage is null Browser: mozilla/5.0 (x11; linux x86_64; rv:36.0) gecko/20100101 firefox/36.0 seamonkey/2.33.1 The current version of Firefox (38.0.5) loads the page without error. Seamonkey 2.38a1 loads the page perfectly (See Rinaldi's post on 6/18) so I assume that this is part of current development effort. I contacted Mega (since they asked so nicely in the error message) and in their reply, they asked me to ...check whether SeaMonkey disables localStorage by default? Open the JavaScript console and type localStorage.length If you get 0 as a result, it is enabled, and the bug is on our side. If you get an error, it is disabled, an the error is with SeaMonkey. Thanks also for your w3.org validator link, we will fix those errors soon. Using Tools - Web Development - Error Console, I typed in localStorage.length and I get an error message TypeError: localStorage is null exactly as Mega reports in their error message. Thanks again for your help. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey obsolete?
On 06/18/2015 04:26 PM, Richard Owlett wrote: Kevin L. Hill wrote: On 06/18/2015 03:59 PM, Paul in Houston, TX wrote: Bill DeCoster wrote: I find myself needing to use IE other programs more and more because of issues with it. What's the point if nothing works? ?? Mine works perfectly. I never have a problem with it. SM 2.26.1 I encountered a site today that may serve as one 'real world' example. Mega.co.nz offers end-to-end encryption for data, claiming that all encryption/decryption is done on the local computer, not by their servers, and that they do not possess the keys needed to decrypt the data. On Seamonkey: Mega.co.nz gives me the following error: Sorry, we were unable to initialize the browser's local storage, either you're using an outdated browser or it's something from our side. If you think it's our fault, please report the issue back to us. Reason: localStorage is null Browser: mozilla/5.0 (x11; linux x86_64; rv:36.0) gecko/20100101 firefox/36.0 seamonkey/2.33.1 More info on local storage in the browser is here: http://www.infoworld.com/article/2625216/web-browsers/html5-in-the-browser--local-data-storage.html The page loads perfectly in Firefox: 38.0.5 Kevin Hill Long Beach, CA https://validator.w3.org/ reports 6 errors ;/ 'nuff said? I can appreciate the utility of the validator site for coders. As a user the validator site is intimidating. There are two options (1) Character Encoding with approx 30 options and (2) Document Type with nearly as many. I can probably make a reasonable guess about Character Encoding but Document type - one looks as good as any other. As a user, do I really care that the validator site found 6 errors, when it is more useful to me to load the page in Firefox and move on - just one more site along with my bank and others that don't play nice with Seamonkey. The Mega site is unique in that it specifically uses the term 'outdated' and asks for feedback. I will report back to them the results of the 'validator' site and see if anything happens. Thanks for the reply. Kevin Hill Long Beach, CA ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey obsolete?
On 06/18/2015 03:59 PM, Paul in Houston, TX wrote: Bill DeCoster wrote: I find myself needing to use IE other programs more and more because of issues with it. What's the point if nothing works? ?? Mine works perfectly. I never have a problem with it. SM 2.26.1 I encountered a site today that may serve as one 'real world' example. Mega.co.nz offers end-to-end encryption for data, claiming that all encryption/decryption is done on the local computer, not by their servers, and that they do not possess the keys needed to decrypt the data. On Seamonkey: Mega.co.nz gives me the following error: Sorry, we were unable to initialize the browser's local storage, either you're using an outdated browser or it's something from our side. If you think it's our fault, please report the issue back to us. Reason: localStorage is null Browser: mozilla/5.0 (x11; linux x86_64; rv:36.0) gecko/20100101 firefox/36.0 seamonkey/2.33.1 More info on local storage in the browser is here: http://www.infoworld.com/article/2625216/web-browsers/html5-in-the-browser--local-data-storage.html The page loads perfectly in Firefox: 38.0.5 Kevin Hill Long Beach, CA ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Restarting SeaMonkey After a Crash
On Sun, 16 Dec 2012 12:57:56 -0800, David E. Ross wrote: Usually, when I restart SeaMonkey, it's back at the same point -- the same Web page and all the other tabs I might have opened -- where the problem occurred. This means I have the same problem again. Is there some way to restart SeaMonkey as if none of this happened, with a single tab at my specified home page? Edit -- Preferences -- Browser If Display on Browser Startup is set to Restore Previous Session, you might try one of the other options. Hopefully this is all it takes. Kevin L. Hill Long Beach, CA ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Only check for new mail after opening Mail Newsgroups
On Fri, 20 Apr 2012 11:45:16 -0400, BIll Spikowski wrote: My only problem occurs when I leave my office and for some reason need to leave a SM browser window open; in that case, I've closed the SM mail window because I do not want email downloaded from the server when I'm out of the office (I need to monitor it on my Blackberry or on my laptop or at home). It seems that the setting in the subject line of this thread was created for people in my exact situation, if I'm understanding it correctly. If I could make it work, I'd be even more deliriously happy with Seamonkey! Have you experimented with the options to Leave the messages on the server also located in the tab for Server Settings? If that box is checked on your office machine, then all emails will remain on the server and can be downloaded by your Blackberry and/or home computer. If you check the sub-option Until I delete them, then deleting the local copy in SeaMonkey, will remove the email from the server. I have not tried the option For at most 'X' days but I assume that would leave messages on the server for a maximum of 'X' days. While this would make emails available to your Blackberry and home computer, it might create other problems. You will end up with more than one local copy of many emails. Best wishes, Kevin Kevin L. Hill Long Beach, CA ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: what's happening w/ SM?
On Tue, 14 Feb 2012 11:23:03 -0500, chicagofan wrote: Can anyone tell me why, if they had to fool with passwords, they didn't give us the option of *always* showing passwords... in a password file? ;) bj Here is a workaround for the new and improved password manager. There is no guarantee how long the code will be kept in future versions. Here is a way to use the old password manager. Copy the following address into the browser: chrome://passwordmgr/content/passwordManager.xul Save it to a convenient bookmark. Use that bookmark when you need to work with your passwords. Kevin L. Hill Long Beach, CA ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
