Mordechai Peller wrote:
Lea de Groot wrote:
Yes, speculation is useless.Interesting, but you're missing a critical piece of data. Without knowing what their resolution is at 100%, the value of the data is very limited. For example, [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED]
One of my clients, for the month of August shows the follow figures in their logs:
Count | % of screen used by window <snip />
Yes, you can grab that info with JS as well to get the full picture for each hit.
Getting back to accessibility - you could look at screen res as a probability curve and see that the great majority of general visitors would use 800 and 1024. Aim for these resolutions, if the user runs 640x480 and the content is still readable (even with a side scroll) then that's ok. If the content is still readable at high res (albeit with lots of whitespace) then that's ok.
Trying to convince a designer of this is another matter :D
My POV is if a user resizes the browser window to 200x100 then that's something they have undertaken after the page has been delivered to them. Once they have the page, what they want to do to break it is entirely their problem, it's only client side code.
Cheers James
(using a common res of 1680x1050 :) )
****************************************************** The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
