Re: Browser Resolution
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 25012
interpreted = N
texte = On 12/2/1999 3:12 PM, Alex McCombie atAlex@NewWorldMedia.com wrote:>> The slightly longer answer is that it is none of>> your business. HTML is supposed to be resolution >> agnostic;>> I almost didn't reply to this, but I just couldn't > take it...[snip]> Without making this a personal flame, I would saythat > I whole-heartedly disagree. Developers that use > technology to it's fullest to further improve> the online experience for visitors may ultimately be> far more successful than those who simply say HTML > wasn't designed to do thatThat's not what John said; he correctly pointed outthat HTML was originally designed to be resolutionagnostic, and (in fact) appearance agnostic ingeneral. The ideal was to tag text with what it was,not how it should appear. With the onset of CSS and XML, this separation ofcontent and presentation is becoming clearer andreturning to HTML's roots.Besides, depending on how someone may choose to usethat browser information, it may not improve my onlineexperience. A client just asked me today if they couldalways have their window be 640x480. Ugh. With theright JavaScript, sure. But personally, I get tickedwhen JavaScript takes over my screen and determinesthe correct size for me.I apologize for the OTP...__________________________________________________Do You Yahoo!?Thousands of Stores. Millions of Products. All in one place.Yahoo! Shopping: http://shopping.yahoo.com-------------------------------------------------------------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:
On 12/2/1999 3:12 PM, Alex McCombie atAlex@NewWorldMedia.com wrote:>> The slightly longer answer is that it is none of>> your business. HTML is supposed to be resolution >> agnostic;>> I almost didn't reply to this, but I just couldn't > take it...[snip]> Without making this a personal flame, I would saythat > I whole-heartedly disagree. Developers that use > technology to it's fullest to further improve> the online experience for visitors may ultimately be> far more successful than those who simply say HTML > wasn't designed to do thatThat's not what John said; he correctly pointed outthat HTML was originally designed to be resolutionagnostic, and (in fact) appearance agnostic ingeneral. The ideal was to tag text with what it was,not how it should appear. With the onset of CSS and XML, this separation ofcontent and presentation is becoming clearer andreturning to HTML's roots.Besides, depending on how someone may choose to usethat browser information, it may not improve my onlineexperience. A client just asked me today if they couldalways have their window be 640x480. Ugh. With theright JavaScript, sure. But personally, I get tickedwhen JavaScript takes over my screen and determinesthe correct size for me.I apologize for the OTP...__________________________________________________Do You Yahoo!?Thousands of Stores. Millions of Products. All in one place.Yahoo! Shopping: http://shopping.yahoo.com-------------------------------------------------------------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
Chris Vargas
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:
UPS Quick Cost Calculator (1997)
Sub Totals (2000)
pc (1997)
WebCat2 Append problem (B14Macacgi) (1997)
color and size options / ARCHIVES (1997)
dbQuickView 2.0 (2005)
Setting up shop (1997)
WebCatalog Hosting (1996)
Error Lob.db records error message not name (1997)
[OT] Happy Turkey Day! (2003)
multiple credit card merchant accounts/processors (1997)
Using Cookie for client specific info? (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Further tests with the infamous shipCost (1997)
Locking up with WebCatalog... (1997)
Plugin or CGI or both (1997)
[OT] Shell script (2004)
2nd WebCatalog2 Feature Request (1996)
price carry over (1997)
Limiting user access to .tmpl files (1997)