tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 13 April 2012

Where's the Viewport Size Data?

Posted on 07:38 by Unknown


Chart of screen resolution from StatCounter.




StatCounter released data on Wednesday showing that the screen resolution of 1,366 x 768 has surpassed 1,024 x 768 as the most common screen resolution. If you've paid attention to the drive for widescreen displays on newer machines, this may not come as much of a surprise to you. I find it more surprising nobody has commented on the decline of most higher resolutions.




What was surprising was this quote in the release:




The screen resolution size people are using is a critical factor for developers when it comes to web design, particularly in the case of fixed width web pages.



For web developers who still develop fixed-width layouts, especially targeting 1,024 x 768, this doesn't matter. Those developers are already lost to us.




For developers who know that screen resolution doesn't necessarily equate to window, and by extension viewport, sizes then this still doesn't matter.




For developers who actually understand the concepts behind responsive web design (RWD) then this doesn't matter.




As anyone in this space knows, that minor shift in numbers that put the wider screen resolution (still the same height) just above the previous champ doesn't require a change to our processes. A skilled developer already has taken the time to assess the audience of a site, or when that data is unknown, is already coding and designing to accommodate various screen resolutions and window sizes. The only real challenge here is protecting our clients from hearing those data points in a vacuum and trying to react. We just need to be smart about counseling them.




That hasn't stopped it from getting a fair amount of attention from the more well-known web folk. Over at .net Magazine (Browser screen resolution stats rile devs) there are some quotes that seem a bit too reactive, along with some that are a fair bit smarter.




If you are somehow caught up with concerns over screen resolutions (and there are some valid reasons to be), then just don't forget that viewport sizes aren't the same as screen resolutions. Scrollbars, button bars, and other browser chrome all take away from that space. Twelve (12!) years ago I wrote a couple of articles addressing that, one of which gathered and presented all the data: Real-World Browser Size Stats, Part II. Last year Chris Coyier wrote a similar article: Screen Resolution ≠ Browser Window. This isn't new stuff.




If you want to take StatCounter to task for anything, then ask them this — where is the viewport size data?

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in browser, design, standards, usability, UX | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Copying Content Styled with Text-Transform
    Using the CSS property text-transform to automatically shift copy to uppercase has been popular for a while now, but a combination of a rec...
  • HTML5 Finally Gets... a Logo?
    Start Rant With all the debate about elements , attributes , semantic meaning and who really owns HTML5 , it's thrilling to see that t...
  • New Google Analytics Features
    In the article " Google Analytics Now More Powerful, Flexible and Intelligent " from last Tuesday (yes, I know I'm behind on t...
  • Speaking: Accessible Web Apps & Standards
    I will be speaking twice in September, both of them sponsored by Infotech Niagara. If you're in the Buffalo area, these are great opport...
  • Speaking at WordCamp Buffalo 2013
    This Saturday I will be speaking at Buffalo's second WordCamp . Last year was a great day-long event filled with many good speakers (not...
  • CSS-D Finds New Home at evolt.org
    The incredibly popular, active, and valuable mailing list devoted to Cascading Style Sheets, CSS-Discuss (css-d), has moved its hosting to ...
  • Google Chrome Pre-Installed on Sony PCs
    Google cut a deal with Sony's PC division to distribute Chrome as a pre-installed browser on their Vaio PCs. Google claims to be in talk...
  • Test in Lynx and Print, It's Your Job
    I have admittedly not taken the time to attend An Event Apart any of the times it's been held, but I do tend to follow the #aea hashtag...
  • Thanksgiving, Technology, and Just Picking a Fight
    My logs tell me that nobody took this 2011 plea seriously. I blame the typeface. Last year on Thanksgiving I made the case for ignoring soci...
  • Tables as Responsive Image Containers
    If you've been following the latest chaos in the responsive image debate, you may know that there is a battle afoot between supporters o...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ▼  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ▼  April (8)
      • Don't Blame Opera, Blame Devs
      • WHATWG as W3C Community Group in Name Only
      • Dining in the Dark
      • Speaking at Buffalo's Entrepalooza 2012 - May 10
      • Where's the Viewport Size Data?
      • Announcing PrintShame.com
      • More Evidence of the Need for Print Styles
      • W3C CSS Odor Module Released
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ►  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ►  January (11)
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile