Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Keith Whaley


Phillip Jones wrote:
Hello, it been a while I vowed never to come back to this forum except 
to ask a question. I remain true to my vow. I am asking a question


I have a puzzle.

examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as it 
should.


In SM 1.1.17

after the side text is shown then the main text shows about an inch to 
inch and a half wide.


On my SM 1.1.17, the body text shows up on the left side of the main
body, as a 3/4 wide vertical strip.

On the other hand, it renders perfectly in my FireFox v.3.5.2.

using the w3c validator, typing the  link above shows numerous items 
needing correction and several warning. yet the other applications 
appear to load correctly. If you go to any links other than vacation, 
the pages work even on SM1.1.17.


Anyone have an explanation.


Sorry. Can't offer any remedy or explanation, but can confirm what you
have experienced...
I look forward to FF 2.0, but use none of the others you mentioned...
Nice to see you back again, even if it IS for a brief time...

keith


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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Stanimir Stamenkov

Sun, 30 Aug 2009 23:27:39 -0400, /Phillip Jones/:


examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as it 
should.


It display as intended SeaMonkey 1.1.*, IMO.  There's a weird table 
definition used to lay out the problem content:


table class=MS_WH_ZoneRow
tbody
  tr
td style=WIDTH: 1%/
td style=WIDTH: 10%.../td
td style=WIDTH: 89%/
  /tr
/tbody
/table

Note the abbreviated empty-element XML syntax used is not compatible 
with the text/html type served, but what's really causing trouble 
is the second td style=WIDTH: 10%.../td element which holds 
the main content.  Why the author has chosen to specify 10% of the 
available space for the main content and 89% for its right margin is 
not clear to me.  What we probably see with the more modern browsers 
is effect of the newer _non-normative_ automatic table layout [1] 
algorithm recommended just lately.


[1] http://www.w3.org/TR/CSS21/tables.html#auto-table-layout

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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Phillip Jones

David E. Ross wrote:

On 8/30/2009 8:27 PM, Phillip Jones wrote:
Hello, it been a while I vowed never to come back to this forum except 
to ask a question. I remain true to my vow. I am asking a question


I have a puzzle.

examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as it 
should.


In SM 1.1.17

after the side text is shown then the main text shows about an inch to 
inch and a half wide.


using the w3c validator, typing the  link above shows numerous items 
needing correction and several warning. yet the other applications 
appear to load correctly. If you go to any links other than vacation, 
the pages work even on SM1.1.17.


Anyone have an explanation.


Generally, a rendering engine (the browser's guts that display a Web
page) is programmed to guess how to display a page that is buggy.
Different rendering engines might guess differently, depending on how
the programmer decides HTML syntax errors should be handled.

SeaMonkey 1.1.17 gives different results from SeaMonkey 2.x because they
different Gecko engines.  SeaMonkey 2.x uses approximately the same
engine that is used by Firefox 3.x, an engine that guesses differently
from the one used by SeaMonkey 1.1.17.

In my opinion, a browser is not at fault if it displays a buggy Web page
incorrectly, even if other browsers are able to display the page
appropriately.  After all, if you input manure, you should not be
surprised if the output is also manure.



I agree, I knew it wasn't right by running, it through the Validator and 
coming up with all those errors and warnings.


But I find it curious, that the efforts to be standards compliant was to 
make it so that if a site was using bad code it wasn't suppose to load. 
 Forcing developer of website to get it right.  Yet all the new 
Browsers whether Gecko or webkit appear to be falling back to an old IE 
5 trick of self healing.


It appears only SeaMonkey 1.1.17 is the only one loading it correctly.
--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net   http://www.vpea.org
mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Phillip Jones

Keith Whaley wrote:


Phillip Jones wrote:
Hello, it been a while I vowed never to come back to this forum except 
to ask a question. I remain true to my vow. I am asking a question


I have a puzzle.

examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as 
it should.


In SM 1.1.17

after the side text is shown then the main text shows about an inch to 
inch and a half wide.


On my SM 1.1.17, the body text shows up on the left side of the main
body, as a 3/4 wide vertical strip.

On the other hand, it renders perfectly in my FireFox v.3.5.2.

using the w3c validator, typing the  link above shows numerous items 
needing correction and several warning. yet the other applications 
appear to load correctly. If you go to any links other than vacation, 
the pages work even on SM1.1.17.


Anyone have an explanation.


Sorry. Can't offer any remedy or explanation, but can confirm what you
have experienced...
I look forward to FF 2.0, but use none of the others you mentioned...
Nice to see you back again, even if it IS for a brief time...

keith


I don't really use the others, my browser of choice until SM2 becomes a 
god version (non beta, non release Candidate) is SM1.1x For one thing 
SM2 and FF3.x breaks my SkyPilot skin.


I use Opera, OmniWeb, iCab and Safari 4 for site testing purposes. two 
three of them Safari, iCab, and OmniWeb have no way to make secure login 
(Type a Password at beginning before any messages thing will download),


Opera, SM,SM2, and FireFox have secure login. The other s don't and use 
AppleKey Chain only.


--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net   http://www.vpea.org
mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread David E. Ross
On 8/31/2009 7:35 AM, Phillip Jones wrote:
 David E. Ross wrote:
 On 8/30/2009 8:27 PM, Phillip Jones wrote:
 Hello, it been a while I vowed never to come back to this forum except 
 to ask a question. I remain true to my vow. I am asking a question

 I have a puzzle.

 examine this page with SM 1.1.17:

 http://villageelectronicsservice.com/VacationSchedule.aspx

 Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

 In all of those All-in-ones and Web Browsers The page for me views as it 
 should.

 In SM 1.1.17

 after the side text is shown then the main text shows about an inch to 
 inch and a half wide.

 using the w3c validator, typing the  link above shows numerous items 
 needing correction and several warning. yet the other applications 
 appear to load correctly. If you go to any links other than vacation, 
 the pages work even on SM1.1.17.

 Anyone have an explanation.
 Generally, a rendering engine (the browser's guts that display a Web
 page) is programmed to guess how to display a page that is buggy.
 Different rendering engines might guess differently, depending on how
 the programmer decides HTML syntax errors should be handled.

 SeaMonkey 1.1.17 gives different results from SeaMonkey 2.x because they
 different Gecko engines.  SeaMonkey 2.x uses approximately the same
 engine that is used by Firefox 3.x, an engine that guesses differently
 from the one used by SeaMonkey 1.1.17.

 In my opinion, a browser is not at fault if it displays a buggy Web page
 incorrectly, even if other browsers are able to display the page
 appropriately.  After all, if you input manure, you should not be
 surprised if the output is also manure.

 
 I agree, I knew it wasn't right by running, it through the Validator and 
 coming up with all those errors and warnings.
 
 But I find it curious, that the efforts to be standards compliant was to 
 make it so that if a site was using bad code it wasn't suppose to load. 
   Forcing developer of website to get it right.  Yet all the new 
 Browsers whether Gecko or webkit appear to be falling back to an old IE 
 5 trick of self healing.
 
 It appears only SeaMonkey 1.1.17 is the only one loading it correctly.

While I've read suggestions that browsers reject bad HTML, I don't think
that has been implemented anywhere.  It would suddenly make much of the
Web inaccessible.  It would also cause havoc with much HTML-formatted
E-mail (an average of 9.1 HTML errors per kilobyte of message).

-- 
David E. Ross
http://www.rossde.com/

Go to Mozdev at http://www.mozdev.org/ for quick access to
extensions for Firefox, Thunderbird, SeaMonkey, and other
Mozilla-related applications.  You can access Mozdev much
more quickly than you can Mozilla Add-Ons.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Bush

Phillip Jones wrote:
Hello, it been a while I vowed never to come back to this forum except 
to ask a question. I remain true to my vow. I am asking a question


I have a puzzle.

examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as it 
should.


In SM 1.1.17

after the side text is shown then the main text shows about an inch to 
inch and a half wide.


using the w3c validator, typing the  link above shows numerous items 
needing correction and several warning. yet the other applications 
appear to load correctly. If you go to any links other than vacation, 
the pages work even on SM1.1.17.


Anyone have an explanation.

Same results here with Sm 1.1.17

Another site is the Same .. Started with SM 1.1.15

http://www.co.genesee.mi.us/treasurer/pi.htm

Click onAssessment and Tax Information

in the search box Choose  SMITH  ( just because it is a Common Name )

Then click one of the Smiths listed and See the Resulting page .

It's  Garbage One paragraph Written over the other .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Stanimir Stamenkov

Mon, 31 Aug 2009 17:33:08 +0300, /Stanimir Stamenkov/:

Sun, 30 Aug 2009 23:27:39 -0400, /Phillip Jones/:


examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as 
it should.


It display as intended SeaMonkey 1.1.*, IMO.  There's a weird table 
definition used to lay out the problem content:


table class=MS_WH_ZoneRow
tbody
  tr
td style=WIDTH: 1%/
td style=WIDTH: 10%.../td
td style=WIDTH: 89%/
  /tr
/tbody
/table


You may workaround the obvious authoring error by applying the 
following user style:


@-moz-document url-prefix(http://villageelectronicsservice.com/;) {
  td.MS_WH_ZoneSpacing { width: 1% !important; }
  td.MS_WH_ZoneSpacing + td { width: 98% !important; }
}

You can place it in your userContent.css or apply it using the 
Stylish http://xsidebar.mozdev.org/modifiedmisc.html#stylish 
extension.


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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Stanimir Stamenkov

Mon, 31 Aug 2009 11:31:56 -0400, /Bush/:


http://www.co.genesee.mi.us/treasurer/pi.htm

Click onAssessment and Tax Information

in the search box Choose  SMITH  ( just because it is a Common Name )

Then click one of the Smiths listed and See the Resulting page .

It's  Garbage One paragraph Written over the other .


Again, as with the original example it is an obvious author error. 
There's a completely unnecessary CSS height declaration to one of 
the DIV elements:


div align=center style=width: 567; height: 326...

You may workaround it by applying the following user style:

@-moz-document 
url-prefix(http://www.co.genesee.mi.us/tax/parcel_data3.asp;) {

  div { height: auto !important; }
}

The most convenient way of doing this is by using the Stylish extension.

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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Paul B. Gallagher

Stanimir Stamenkov wrote:

Sun, 30 Aug 2009 23:27:39 -0400, /Phillip Jones/:


examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as 
it should.


It display as intended SeaMonkey 1.1.*, IMO.  There's a weird table 
definition used to lay out the problem content:


table class=MS_WH_ZoneRow
tbody
  tr
td style=WIDTH: 1%/
td style=WIDTH: 10%.../td
td style=WIDTH: 89%/
  /tr
/tbody
/table

Note the abbreviated empty-element XML syntax used is not compatible 
with the text/html type served, but what's really causing trouble is 
the second td style=WIDTH: 10%.../td element which holds the main 
content.  Why the author has chosen to specify 10% of the available 
space for the main content and 89% for its right margin is not clear to 
me.  What we probably see with the more modern browsers is effect of the 
newer _non-normative_ automatic table layout [1] algorithm recommended 
just lately.


Yes. SM 1.1.16 honors the idiotic setting and hides most of the content, 
as the author seems to intend.


--
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: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Phillip Jones

Stanimir Stamenkov wrote:

Mon, 31 Aug 2009 17:33:08 +0300, /Stanimir Stamenkov/:

Sun, 30 Aug 2009 23:27:39 -0400, /Phillip Jones/:


examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as 
it should.


It display as intended SeaMonkey 1.1.*, IMO.  There's a weird table 
definition used to lay out the problem content:


table class=MS_WH_ZoneRow
tbody
  tr
td style=WIDTH: 1%/
td style=WIDTH: 10%.../td
td style=WIDTH: 89%/
  /tr
/tbody
/table


You may workaround the obvious authoring error by applying the following 
user style:


@-moz-document url-prefix(http://villageelectronicsservice.com/;) {
  td.MS_WH_ZoneSpacing { width: 1% !important; }
  td.MS_WH_ZoneSpacing + td { width: 98% !important; }
}

You can place it in your userContent.css or apply it using the Stylish 
http://xsidebar.mozdev.org/modifiedmisc.html#stylish extension.




Thanks it works.

--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net   http://www.vpea.org
mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Phillip Jones

Stanimir Stamenkov wrote:

Mon, 31 Aug 2009 11:31:56 -0400, /Bush/:


http://www.co.genesee.mi.us/treasurer/pi.htm

Click onAssessment and Tax Information

in the search box Choose  SMITH  ( just because it is a Common Name )

Then click one of the Smiths listed and See the Resulting page .

It's  Garbage One paragraph Written over the other .


Again, as with the original example it is an obvious author error. 
There's a completely unnecessary CSS height declaration to one of the 
DIV elements:


div align=center style=width: 567; height: 326...

You may workaround it by applying the following user style:

@-moz-document 
url-prefix(http://www.co.genesee.mi.us/tax/parcel_data3.asp;) {

  div { height: auto !important; }
}

The most convenient way of doing this is by using the Stylish extension.



I've had a problem with the stylish extension despite saving it to 
profile folder I ended up having reinstall it with each new version of 
SM I install and have to redo my styles.


--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net   http://www.vpea.org
mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Phillip Jones

Paul B. Gallagher wrote:

Stanimir Stamenkov wrote:

Sun, 30 Aug 2009 23:27:39 -0400, /Phillip Jones/:


examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as 
it should.


It display as intended SeaMonkey 1.1.*, IMO.  There's a weird table 
definition used to lay out the problem content:


table class=MS_WH_ZoneRow
tbody
  tr
td style=WIDTH: 1%/
td style=WIDTH: 10%.../td
td style=WIDTH: 89%/
  /tr
/tbody
/table

Note the abbreviated empty-element XML syntax used is not compatible 
with the text/html type served, but what's really causing trouble is 
the second td style=WIDTH: 10%.../td element which holds the 
main content.  Why the author has chosen to specify 10% of the 
available space for the main content and 89% for its right margin is 
not clear to me.  What we probably see with the more modern browsers 
is effect of the newer _non-normative_ automatic table layout [1] 
algorithm recommended just lately.


Yes. SM 1.1.16 honors the idiotic setting and hides most of the content, 
as the author seems to intend.


Thanks all for the comments. My question has been settled. I will step 
out of the Forum again.


--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net   http://www.vpea.org
mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Stanimir Stamenkov

Mon, 31 Aug 2009 14:35:12 -0400, /Phillip Jones/:

Stanimir Stamenkov wrote:


The most convenient way of doing this is by using the Stylish extension.


I've had a problem with the stylish extension despite saving it to 
profile folder I ended up having reinstall it with each new version of 
SM I install and have to redo my styles.


Haven't got problems with the Stylish extension, so far.  I'm always 
installing it to the application directory (and reinstalling on 
SeaMonkey upgrades) but my styles are kept intact in my profile.


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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-31 Thread Rick

Phillip Jones wrote:
Hello, it been a while I vowed never to come back to this forum except 
to ask a question. I remain true to my vow. I am asking a question


I have a puzzle.

examine this page with SM 1.1.17:

http://villageelectronicsservice.com/VacationSchedule.aspx

Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.

In all of those All-in-ones and Web Browsers The page for me views as it 
should.


In SM 1.1.17

after the side text is shown then the main text shows about an inch to 
inch and a half wide.


using the w3c validator, typing the  link above shows numerous items 
needing correction and several warning. yet the other applications 
appear to load correctly. If you go to any links other than vacation, 
the pages work even on SM1.1.17.


Anyone have an explanation.
I agree with David Ross--poorly designed page--I would let them know 
about it.  I am guessing that they paid to have this site designed and 
if it does not work in all browsers then IMO they basically wasted their 
money.

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


Re: Site doesn't appear correct on SM 1.1.17

2009-08-30 Thread David E. Ross
On 8/30/2009 8:27 PM, Phillip Jones wrote:
 Hello, it been a while I vowed never to come back to this forum except 
 to ask a question. I remain true to my vow. I am asking a question
 
 I have a puzzle.
 
 examine this page with SM 1.1.17:
 
 http://villageelectronicsservice.com/VacationSchedule.aspx
 
 Now use: SM 2, FF3.0/3.5, Omniweb, Opera or iCab.
 
 In all of those All-in-ones and Web Browsers The page for me views as it 
 should.
 
 In SM 1.1.17
 
 after the side text is shown then the main text shows about an inch to 
 inch and a half wide.
 
 using the w3c validator, typing the  link above shows numerous items 
 needing correction and several warning. yet the other applications 
 appear to load correctly. If you go to any links other than vacation, 
 the pages work even on SM1.1.17.
 
 Anyone have an explanation.

Generally, a rendering engine (the browser's guts that display a Web
page) is programmed to guess how to display a page that is buggy.
Different rendering engines might guess differently, depending on how
the programmer decides HTML syntax errors should be handled.

SeaMonkey 1.1.17 gives different results from SeaMonkey 2.x because they
different Gecko engines.  SeaMonkey 2.x uses approximately the same
engine that is used by Firefox 3.x, an engine that guesses differently
from the one used by SeaMonkey 1.1.17.

In my opinion, a browser is not at fault if it displays a buggy Web page
incorrectly, even if other browsers are able to display the page
appropriately.  After all, if you input manure, you should not be
surprised if the output is also manure.

-- 
David E. Ross
http://www.rossde.com/

Go to Mozdev at http://www.mozdev.org/ for quick access to
extensions for Firefox, Thunderbird, SeaMonkey, and other
Mozilla-related applications.  You can access Mozdev much
more quickly than you can Mozilla Add-Ons.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey