Re[2]: Malformed Pages
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 25212
interpreted = N
texte = Thank you all for your suggestions, but I think you are missing the point here. The page does not display _because_ it is not complete; it frequently end in the middle of a tag, but only under Navigator. It looks like Netscape simply gets bored waiting and gives up, then cannot render the page since it has only 3/4 of the text. The exact same page, with the exact same HTML tags, will display one time and not another. Nothing changes except that sometime NN will see the whole page and sometimes it won't.
And as for closing tags, they are REQUIRED not optional. Just because MS-HTML is lazy doesn't mean I am ever going to ignore the standard. I look forward to many sites breaking when the next generation XML browsers become common. Virtually all tags require closing, all tag parameters must be ALL CAPS, and all parameter values must be quoted. My sites will probably work, will yours??? John PeacockNote: no specific criticsm of anyone's site is intended. It just makes me crazy when MS-HTML is used as the default, when it is clearly broken. ____________________Reply Separator____________________ Subject: Re: Malformed Pages Author:
(WebCatalog Talk) Date: 12/6/99 8:07 PMwhenever I've had this happen, it was a error in a table. Netscape is very particular that everything has a close tag. it's also the easiest to fix, so really scour your html and make sure the tables are right... jpeacock@univpress.com wrote:> Environment: > WebCatalog Windows EXE version 3.0.4 > Windows NT 4.0 (Service Pack 3) > O'Reilly's WebSite 2.4.0.8 (Beta) > Netscape Navigator 4.6 > > Has anyone experienced a problem where a page will display as blank, although it > clearly contains data (using View Source). The pages are alway large, contain > several tables, and seem to end prematurely in View Source. Almost always, > hitting Reload will correct the display problem. I have only managed to have it > happen in Netscape; I hardly ever touch IE until the last step. > > This is a site that relies heavily on WebDNA for all pages. If I reduce the > number of records returned on the destination page, it reduces the likelyhood of > a problem occurring. When the page works, the HTML appears fine. I do not > think that the coding is causing it; it strikes me that is is a browser buffer > issue. I can get it to happen with two different cache programs, as well as > direct connection. > > I saved the file on an occasion when it displayed properly and found that the > file was ~95k (sans graphics). This is hardly very large (considering I am now > viewing a >300k file from Netscape tech support). Is this a Netscape/WebCat bug > or should I report it to WebSite??? > > John Peacock > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. > To end your Mail problems go to . > > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
| |
- Re[2]: Malformed Pages ( 1999)
|
Thank you all for your suggestions, but I think you are missing the point here. The page does not display _because_ it is not complete; it frequently end in the middle of a tag, but only under Navigator. It looks like Netscape simply gets bored waiting and gives up, then cannot render the page since it has only 3/4 of the text. The exact same page, with the exact same HTML tags, will display one time and not another. Nothing changes except that sometime NN will see the whole page and sometimes it won't. And as for closing tags, they are REQUIRED not optional. Just because MS-HTML is lazy doesn't mean I am ever going to ignore the standard. I look forward to many sites breaking when the next generation XML browsers become common. Virtually all tags require closing, all tag parameters must be ALL CAPS, and all parameter values must be quoted. My sites will probably work, will yours??? John PeacockNote: no specific criticsm of anyone's site is intended. It just makes me crazy when MS-HTML is used as the default, when it is clearly broken. ____________________Reply Separator____________________ Subject: Re: Malformed Pages Author: (WebCatalog Talk) Date: 12/6/99 8:07 PMwhenever I've had this happen, it was a error in a table. Netscape is very particular that everything has a close tag. it's also the easiest to fix, so really scour your html and make sure the tables are right... jpeacock@univpress.com wrote:> Environment: > WebCatalog Windows EXE version 3.0.4 > Windows NT 4.0 (Service Pack 3) > O'Reilly's WebSite 2.4.0.8 (Beta) > Netscape Navigator 4.6 > > Has anyone experienced a problem where a page will display as blank, although it > clearly contains data (using View Source). The pages are alway large, contain > several tables, and seem to end prematurely in View Source. Almost always, > hitting Reload will correct the display problem. I have only managed to have it > happen in Netscape; I hardly ever touch IE until the last step. > > This is a site that relies heavily on WebDNA for all pages. If I reduce the > number of records returned on the destination page, it reduces the likelyhood of > a problem occurring. When the page works, the HTML appears fine. I do not > think that the coding is causing it; it strikes me that is is a browser buffer > issue. I can get it to happen with two different cache programs, as well as > direct connection. > > I saved the file on an occasion when it displayed properly and found that the > file was ~95k (sans graphics). This is hardly very large (considering I am now > viewing a >300k file from Netscape tech support). Is this a Netscape/WebCat bug > or should I report it to WebSite??? > > John Peacock > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. > To end your Mail problems go to . > > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Exclamation point (1997)
E-mailer error codes (1997)
Need help with form (1998)
[Sum] function? (1997)
[protect admin] (1997)
No more misunderstanding ... yay! :) (1997)
On a related topic (2006)
typhoon... (1997)
Setting up shop (1997)
Blowback and budgets. (2000)
access denied problem (1997)
remote install on RH9 (2004)
Help! WebCat2 bug (1997)
Form Weirdness (2002)
Out of the woodwork (2007)
Custom Shipping Charges (1997)
[WebDNA] products.db (2013)
Reports of ErrorLog.txt not being written in Linux (2000)
.db-tmp (2000)
PCS Emailer's role ? (1997)