Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Arnie Goetchius wrote: According to the latest download of Seamonkey 2.1b2pre there is a process to report broken web sites as described in the following paragraph: SeaMonkey comes with a new tool for reporting broken web sites (available through the Custom Install option). From the 'Help' menu, select 'Report Broken Web Site' and provide as much information as you can about the issue that you are encountering. Ah, that's on this page: http://www.seamonkey-project.org/dev/get-involved KaiRo, can you remove that paragraph please? I did a custom install but did not see anywhere that I could load that option. When I click on the Help menu, I don't see 'Report Broken Web Site'. Is this in the future? Sounds like a terrific idea. Actually it's in SM 2.0 but has been removed for SM 2.1 because the reports basically went nowhere (no-one picked them up). Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=590102 SM 2.1 website compatibility should be better in general, though, since it now advertises itself as Firefox in addition to SeaMonkey. HTH Jens -- Jens Hatlak http://jens.hatlak.de/ SeaMonkey Trunk Tracker http://smtt.blogspot.com/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: strange seamonkey crashing problem
Jim wrote: SM 2.0.10, Windows XP w/SP3, Pentium 4 with 1.5 gigs RAM. Last night I was using the SM Browser and it crashed. After that, I could not start up the browser. The Select a Profile screen came up, but, as soon as I moused over the screen, it would crash. I tried starting u[ the browser with options from the command line, and a page would load just fine, until I moused over any place in the page, and it would crashe. Same with SM mail. I couldn't reboot because I was running a distribute computing app in the background, and didn't want to lose 4 hours of work. This morning, I came down and SM started up just fine. Comments on this? Does SM set some error flag some place? Seemed like something was in memory that SM didn't like. I'm also running Norton Internet Security, and it likes doing stuff during the wee hours of the night, so maybe it took up whatever was in memory that was bugging SM? Jim Jim, a while back, SeaMonkey (or, more likely, it pre-decedent Mozilla Suite) had a problem where you were able to close the program, but it would still be shown as running in the list of Running programs found when you did a Ctrl-Alt-Del, so you were unable to re-start the program until you had clicked on the name in the list of running programs and then you clicked on Finish or Close or whatever. You're being ab;e to start SeaMonkey the next morning might have been because SM had naturally been closed by Windows. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Jens Hatlak schrieb: Ah, that's on this page: http://www.seamonkey-project.org/dev/get-involved KaiRo, can you remove that paragraph please? Please file a bug, even better a patch. 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
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Jens Hatlak wrote: Arnie Goetchius wrote: SM 2.1 website compatibility should be better in general, though, since it now advertises itself as Firefox in addition to SeaMonkey. FWIW, I can log into http://adwords.microsoft.com with 2.1 without getting an incompatible browser error message. I get an error message using 2.010 However, I still get incompatible browser error message when logging into http://adwords.google.com with SM 2.1. No error message if I log in with FF 3.6 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey page render issue
Eric wrote: David Cox wrote: On 18/11/2010 11:20 AM, Eric wrote: I just checked seamonkey's rendering of http://www.w3.org/Amaya/Overview.html It doesn't properly render it. One of the side frames overlaps the words on another frame. Though readable, it is annoying. Do you have a minimum font size set? That can cause frames to overlap. djc snip I've never changed it, but when I go in to about:config it says default 20 Eric I have the same problem on some pages, but I never explored the reason for the overlap that sometimes makes a page unreadable. I usually just use a different browser. When I look at the SeaMonkey parameters, I see that font.minimum-size.th = 10 and all the others = 0. I went to the site you cited and had no problems with text overlap. I am using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.15) Gecko/20101027 SeaMonkey/2.0.10. I look at the problem and I believe that those that have the skills to fix the problem probably have different priorities and that it will get fixed eventually. I am sure that they are already aware of the problem if they use SeaMonkey. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Beauregard T. Shagnasty wrote: Arnie Goetchius wrote: Jens Hatlak wrote: Arnie Goetchius wrote: SM 2.1 website compatibility should be better in general, though, since it now advertises itself as Firefox in addition to SeaMonkey. FWIW, I can log into http://adwords.microsoft.com with 2.1 without getting an incompatible browser error message. I get an error message using 2.010 However, I still get incompatible browser error message when logging into http://adwords.google.com with SM 2.1. No error message if I log in with FF 3.6 I get 404s for both of those 'adwords' URLs ... no error, just missing. Should have been: http://adcenter.microsoft.com https://www.google.com/accounts/ServiceLogin?service=adwords Sorry for my error. sigh Personally, I can't see any advantage to a browser utility that sends some kind of error message to a web site. There are so many broken sites out there that (if this reporting thingy became popular) webmasters would start directing all such messages to dev/null. I can envision users-without-clue sending hundreds/thousands of these reports and possibly causing the site authors to ban access by those browsers. Good point. There are enough of us without a clue to not add any more ;) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SOLVED! SM email not properly responding to FF mailto links
I also took the time to report this in Bugzilla: Incorrect default switches to handle mailto: links / new message window will not open https://bugzilla.mozilla.org/show_bug.cgi?id=613724 -- Michael Lueck ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: strange seamonkey crashing problem
Daniel wrote: Jim wrote: SM 2.0.10, Windows XP w/SP3, Pentium 4 with 1.5 gigs RAM. Last night I was using the SM Browser and it crashed. After that, I could not start up the browser. The Select a Profile screen came up, but, as soon as I moused over the screen, it would crash. I tried starting u[ the browser with options from the command line, and a page would load just fine, until I moused over any place in the page, and it would crashe. Same with SM mail. I couldn't reboot because I was running a distribute computing app in the background, and didn't want to lose 4 hours of work. This morning, I came down and SM started up just fine. Comments on this? Does SM set some error flag some place? Seemed like something was in memory that SM didn't like. I'm also running Norton Internet Security, and it likes doing stuff during the wee hours of the night, so maybe it took up whatever was in memory that was bugging SM? Jim Jim, a while back, SeaMonkey (or, more likely, it pre-decedent Mozilla Suite) had a problem where you were able to close the program, but it would still be shown as running in the list of Running programs found when you did a Ctrl-Alt-Del, so you were unable to re-start the program until you had clicked on the name in the list of running programs and then you clicked on Finish or Close or whatever. You're being ab;e to start SeaMonkey the next morning might have been because SM had naturally been closed by Windows. Daniel Actually, SeaMonkey had shut down and no longer appeared in the list of running programs in Process Explorer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Arnie Goetchius wrote: Beauregard T. Shagnasty wrote: Arnie Goetchius wrote: However, I still get incompatible browser error message when logging into http://adwords.google.com with SM 2.1. No error message if I log in with FF 3.6 I get 404s for both of those 'adwords' URLs ... no error, just missing. Should have been: http://adcenter.microsoft.com https://www.google.com/accounts/ServiceLogin?service=adwords Sorry for my error. sigh Ah, thanks. I see what you mean with the Microsloth site. Setting my UA to any of Ipod, Iphone, Iceweasel, Firefox Linux, multiple Operas including Opera Mobile, and my favorite Borgzilla, I am rejected. Works fine as any IE version... but then it is a Microsloth site. I had no problem with the Google site with any of the above UAs. Since that MS site is looking for advertisers/revenue, I am truly confused why they even care about what browser the prospective spender of money would be using. Oh wait .. it's Microsloth. My Borgzilla is humor: Borgzilla/31.0 (X11;U;Linux i686;en-US;rv:31.0) Resistance is futile Personally, I can't see any advantage to a browser utility that sends some kind of error message to a web site. There are so many broken sites out there that (if this reporting thingy became popular) webmasters would start directing all such messages to dev/null. I can envision users-without-clue sending hundreds/thousands of these reports and possibly causing the site authors to ban access by those browsers. Good point. There are enough of us without a clue to not add any more ;) I'd consider you to be in the Have Clue category, Arnie. g -- -bts -Four wheels carry the body; two wheels move the soul ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Beauregard T. Shagnasty wrote: Arnie Goetchius wrote: Beauregard T. Shagnasty wrote: Arnie Goetchius wrote: However, I still get incompatible browser error message when logging into http://adwords.google.com with SM 2.1. No error message if I log in with FF 3.6 I get 404s for both of those 'adwords' URLs ... no error, just missing. Should have been: http://adcenter.microsoft.com https://www.google.com/accounts/ServiceLogin?service=adwords Sorry for my error. sigh Ah, thanks. I see what you mean with the Microsloth site. Setting my UA to any of Ipod, Iphone, Iceweasel, Firefox Linux, multiple Operas including Opera Mobile, and my favorite Borgzilla, I am rejected. Works fine as any IE version... but then it is a Microsloth site. I had no problem with the Google site with any of the above UAs. Since that MS site is looking for advertisers/revenue, I am truly confused why they even care about what browser the prospective spender of money would be using. Oh wait .. it's Microsloth. My Borgzilla is humor: Borgzilla/31.0 (X11;U;Linux i686;en-US;rv:31.0) Resistance is futile Personally, I can't see any advantage to a browser utility that sends some kind of error message to a web site. There are so many broken sites out there that (if this reporting thingy became popular) webmasters would start directing all such messages to dev/null. I can envision users-without-clue sending hundreds/thousands of these reports and possibly causing the site authors to ban access by those browsers. Good point. There are enough of us without a clue to not add any more ;) I'd consider you to be in the Have Clue category, Arnie.g Thanks for the very kind words. I owe you a beer!! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Robert Kaiser wrote: Jens Hatlak schrieb: Ah, that's on this page: http://www.seamonkey-project.org/dev/get-involved KaiRo, can you remove that paragraph please? Please file a bug, even better a patch. Filed bug 613770. I don't see the sense in writing a patch for plain removal, though, so I skipped that step. Greetings, Jens -- Jens Hatlak http://jens.hatlak.de/ SeaMonkey Trunk Tracker http://smtt.blogspot.com/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 'Report Broken Web Site' Not Available in SM 2.1b2pre
Jens Hatlak schrieb: Filed bug 613770. I don't see the sense in writing a patch for plain removal, though, so I skipped that step. Well, I am seriously cutting down the time I'm working on SeaMonkey and trying to cut down on work time in general, so it will take me some time if I need to look into it. 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
Re: Seamonkey page render issue
James wrote: Eric wrote: David Cox wrote: On 18/11/2010 11:20 AM, Eric wrote: I just checked seamonkey's rendering of http://www.w3.org/Amaya/Overview.html It doesn't properly render it. One of the side frames overlaps the words on another frame. Though readable, it is annoying. Do you have a minimum font size set? That can cause frames to overlap. djc snip I've never changed it, but when I go in to about:config it says default 20 Eric I have the same problem on some pages, but I never explored the reason for the overlap that sometimes makes a page unreadable. I usually just use a different browser. When I look at the SeaMonkey parameters, I see that font.minimum-size.th = 10 and all the others = 0. I went to the site you cited and had no problems with text overlap. I am using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.15) Gecko/20101027 SeaMonkey/2.0.10. I look at the problem and I believe that those that have the skills to fix the problem probably have different priorities and that it will get fixed eventually. I am sure that they are already aware of the problem if they use SeaMonkey. Well, Thanks everyone for the thoughts. I've changed the minimum font to no min or blank, but the fonts everywhere became too small, so I've changed the pixels up, and that seems to work, the overlap is gone, and I can read the screen without squinting. Thanks everyone for the assistance, and I hope this discussion helps others who are experiencing similar difficulties. Eric ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey page render issue
On 11/17/2010 08:35 PM, David Cox wrote: On 18/11/2010 11:20 AM, Eric wrote: I just checked seamonkey's rendering of http://www.w3.org/Amaya/Overview.html It doesn't properly render it. One of the side frames overlaps the words on another frame. Though readable, it is annoying. Do you have a minimum font size set? That can cause frames to overlap. Interesting... I've suffered from this issue just set my minimum font size to 'None' it resolves the issue for me. However it also affects mail windows as well (for instance this one), so it would be nice to be able to set a minimum for mail/news and one for browsing. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0.10 Mac - crashing...and crashing...and crashing...
Chris Ilias wrote: On 10-11-18 11:54 PM, Rufus wrote: Started a couple nights ago...repeated crashes trying to use SM Mail. Then tonight repeated crashes on launch. All reported. Reinstalled SM...so far, so better. So far... Open SeaMonkey, go to the address about:crashes (without the quotes) and tell us your latest crash IDs. We can then look at the data specific to your crash and have a better idea of what is causing the problem. Here they are: Report ID Date Submitted bp-cfb4f38b-adbc-41e9-9c9c-2c0f62101119 11/19/109:06 PM bp-205136aa-405c-46b1-997b-b6e982101119 11/19/109:06 PM bp-b532092b-524d-4b4f-b1be-651b62101119 11/19/109:00 PM bp-36abf4ce-8ae3-4d43-9b8c-0705b2101119 11/19/109:00 PM bp-39ce2cd2-03cc-488b-96b4-a0df32101118 11/18/108:04 PM bp-bd7f092b-68ca-4eff-a28a-4ab532101118 11/18/108:04 PM bp-8b36819b-e19e-4cc8-af88-8ff502101118 11/18/108:04 PM bp-616b818a-1a2d-4541-9544-945452101118 11/18/108:03 PM bp-73914e00-bf24-4182-b6c9-84be72101118 11/18/108:03 PM bp-0abbd060-d90b-464e-ba2f-5ee6f2101118 11/18/108:03 PM bp-6e4a3ff4-3850-41fb-ab6d-0ecd42101118 11/18/108:03 PM bp-1e019584-bae1-4e2d-8851-db8fe2101117 11/17/108:14 PM bp-c01bf9d8-474c-4a57-89f6-5c98d2101117 11/17/108:14 PM bp-d413a5fc-72bd-4f23-8595-acc2c2101117 11/17/108:14 PM bp-78bbe296-940b-46e7-9e2a-44c072101117 11/17/108:14 PM bp-7c167cc8-ab31-44cb-b401-c72c92101117 11/17/108:13 PM bp-968fa452-aae0-4a7c-980a-f84122101117 11/17/108:13 PM bp-d21976b5-1970-4c05-b77b-f81222101117 11/17/108:13 PM 992627F3-805E-4646-B500-7D811DB44CC811/17/107:26 PM bp-fb88e14c-5fe7-49a6-957a-7da662091230 12/30/096:32 PM bp-81c77584-38b1-4480-9beb-3afa72091221 12/21/0910:03 PM -- - Rufus ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
