Posts Tagged ‘browsers’

Guess What? Size DOES matter.

Wednesday, January 20th, 2010

googlebrowsersizeThe Internet is full of variables.  As web developers and web designers, we constantly wrestle with web user variables.  Things like: browser types, browser versions, platforms, Flash, JavaScript, cookies, web-safe colors, connection speed, visual impairments, and fonts.

Our goal is to find the most common settings, and to deliver web sites which match settings with a majority of users viewing the sites.  Also, we need to mitigate any problems which might arise if the user doesn’t have their environment settings similar to the development team’s in-house settings.  Let’s face it, not everybody uses Firefox or Chrome.
(more…)

Google Chrome is at it again

Monday, January 18th, 2010

IEChromeOver the weekend I was researching some new web technologies and stumbled across a new plug-in for Internet Explorer (IE). It’s called Google Chrome Frame, and it solves some big problems in the current development cycle for web apps.

Many people don’t know this, but a lot of time is devoted entirely to making IE (especially older versions) behave properly with W3C standard based browsers (Mozilla Firefox, Safari, Google Chrome, Opera, etc.). This makes developing for the web more complex than it needs to be because most browsers function as you would expect them to. Unfortunately, IE is used by most users across the planet, so the fact that it isn’t based on current standards and behaves oddly isn’t something that we developers can ignore. This is where Google-Chrome-Frame comes to the rescue.

(more…)

Something we can all stand behind

Thursday, August 6th, 2009

stupidIEAs web developers, we have scruples. Two things that have been approaching our radar lately affect everyone who gets mail using Microsoft Outlook, or anyone that goes online. That’s a lot of people.

First let’s talk about Outlook. For the last several versions of Office, Outlook has been using Microsoft Word’s HTML rendering to show HTML emails in Outlook. Word doesn’t follow web standards, nor does it have some of even the most basic features of HTML. Microsoft recently announced that they will go ahead and use Word’s rendering engine in Outlook 2010, even with the public outcry against that decision. You can join us and ~25,000+ others that want to have Microsoft change this. If they supported a standards based rendering engine, we could make your e-blasts so much prettier! Just imagine being able to code emails without tables, and with background images! For more info, check out http://fixoutlook.org/.

Another problem that is currently being brought up is the killing off of Internet Explorer 6. Several initiatives have come and gone, trying and trying again to kill off the 9 year old browser, but it somehow still lingers in the 15%-20% range of browsers used today. This thing is terrible! Ask any web developer what browser gives them the most trouble. It wasn’t so bad when it came out in 2000, but it’s really holding back the future of web development. The latest initiative is IE6 No More. Feel free to click here and see the Google results for “Kill IE6.” This is exactly how we feel about IE6, and when I say “we”, I mean the entire world.

Join us as we stand together and oppose the oppression of the internet and fight to make the World Wide Web a prettier, more user friendly world to live in.

W3C Validation & Testing

Thursday, July 30th, 2009
W3C

W3C

Here at Zoom Creates, we’re fanatical about testing & validation of the web sites we produce. Before a web site is launched, our team performs a site-wide validation check for HTML & CSS compliance using the globally-recognized standards taken from the W3C (World Wide Web Consortium).

What the W3C does:
The World Wide Web Consortium (W3C) develops interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to its full potential. W3C is a forum for information, commerce, communication, and collective understanding. It is the organization which all web standards are derived from and should adhere to.

Valid XHTML 1.0 Transitional

Top 3 reasons why validation and testing of a web site is important:

  1. Multi-browser, multi-version, multi-OS compatibility:  Ensure that the site will look the same on every web browser and operating system being used. However, there are some limitations to this (see below).
  2. Search engine indexing: A compliant web site allows search engines to more easily index the contents of a web site, making for superior organic SEO results.
  3. Maintenance and scalability: When future edits need to be made to a web site, starting off with a compliant site provides the developer with a “clean slate” to work from. Not having to go back and fix junky code saves valuable time and costs. (more…)