🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.comp.lang.coldfusion
Article #11

Re: How to get the resolution of the user

#11
From: no spam
Date: Sun, 31 Mar 2002 17:25
63 lines
4312 bytes
Jim Davis wrote:

>> Starting with the number of visitors who have their browsers at less than,
>> say, 700 px.
>> 
>> On the Superstats site, that's around 35%.  On the client site I mentioned,
>> it's 38%.  Check your client's site info, then ask the client if they're
>> willing to at the very least annoy that many visitors.
> 
> Again, is this the available space in the browser or the application window?
> I wouldn'y make any decisions based on that data AT ALL until that question
> is answered.

You should, and it doesn't matter whether the stats are the browser window
or available space.

The data is a clear indication that there isn't a 1:1 correlation between
monitor resolution and browser width, and that many surfers set their
windows based on their wants rather than on available space.  Sites like
yours that list only monitor resolutions implicitly communicate that
resolution is the more important issue in design, and it's not if you're
concerned about site usability.

I admit that getting monitor width is a bit tougher than getting the
resolution but it's still pretty easy.  The problem is that you can't
measure window width in IE until the window has loaded.

A reasonable workaround (if you feel you can't live with flexible pages and
simply _must_ serve different content to different-sized browsers) is to
load a blank page with code in the head that kicks in onLoad:

if (!innerWidth){
    innerWidth = document.body.clientWidth;
    innerHeight = document.body.clientHeight;
    ... now do something based on the above ...
    }

then use "innerWidth" in code that provides your custom content.  (My
personal choice is flexible pages, but chacun a son gout.)


> But why pick "700" anyway

Because there is a huge number of surfers with their browsers set that way,
so it serves as a good example of why it's not a good idea to design
fixed-width pages based on monitor resolutions.

[ ... snipped a whole bunch of stuff about how we can eventually force
surfers to maximize their browsers by creating larger fixed-width sites,
snipped because it ignores that fact that clients will quit hiring us if we
keep driving away a third or more of their visitors ...]


>> From which you can infer that hardly anybody is ever going to change their
>> window size for any Web site.
> 
> For any single site, yes - but they will change the size to ensure the best
> experience across MOST sites.

In truth, most sites are flexible rather than ego-feeding or novice-built
fixed sizes, so surfers will continue to set their browser sizes for their
own convenience, and avoid sites that expect them to change their behavior
for the designer's convenience.
Technical Details
Message-ID: <B8CC867A.39B21%nosignin@hotmail.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!nntp.abs.net!uunet!dca.uu.net!news.chatlink.com!not-for-mail
References: <FV%o8.6811$DZ4.379109@news-nb00s0.nbnet.nb.ca> <a82hh10img@enews2.newsguy.com> <B8CA2D2B.392E2%nosignin@hotmail.com> <a839tv01t0n@enews2.newsguy.com> <B8CA853B.2EFC3%nosignin@hotmail.com> <a83mbd02jqc@enews3.newsguy.com> <3ca5ab46.8912114@news.cis.dfn.de> <a8563101qpo@enews3.newsguy.com> <B8CB752E.398BA%nosignin@hotmail.com> <a85k9r013df@enews1.newsguy.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f65aa,3a22c885edf2ce1f
X-Google-Attributes: gidf65aa,public
X-Google-Thread: fd36c,3a22c885edf2ce1f
X-Google-Attributes: gidfd36c,public
X-Google-Thread: fb3cb,3a22c885edf2ce1f
X-Google-Attributes: gidfb3cb,public
X-Google-ArrivalTime: 2002-03-31 09:25:19 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!nntp.abs.net!uunet!dca.uu.net!news.chatlink.com!not-for-mail
From: no spam <nosignin@hotmail.com>
Newsgroups: alt.comp.lang.coldfusion,comp.lang.javascript,fj.comp.lang.javascript
Subject: Re: How to get the resolution of the user
Date: Sun, 31 Mar 2002 09:25:14 -0800
Organization: OWDS Inc.
Lines: 65
Message-ID: <B8CC867A.39B21%nosignin@hotmail.com>
References: <FV%o8.6811$DZ4.379109@news-nb00s0.nbnet.nb.ca> <a82hh10img@enews2.newsguy.com> <B8CA2D2B.392E2%nosignin@hotmail.com> <a839tv01t0n@enews2.newsguy.com> <B8CA853B.2EFC3%nosignin@hotmail.com> <a83mbd02jqc@enews3.newsguy.com> <3ca5ab46.8912114@news.cis.dfn.de> <a8563101qpo@enews3.newsguy.com> <B8CB752E.398BA%nosignin@hotmail.com> <a85k9r013df@enews1.newsguy.com>
NNTP-Posting-Host: 1cust150.tnt46.lax3.da.uu.net
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Trace: news.chatlink.com 1017595516 15787 67.224.40.150 (31 Mar 2002 17:25:16 GMT)
X-Complaints-To: abuse@chatlink.com
NNTP-Posting-Date: Sun, 31 Mar 2002 17:25:16 +0000 (UTC)
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022