Archive for the 'CSS' Category

“Jeffrey Zeldman is now following you on Twitter”

Monday, September 28th, 2009

…or how Twitter can be actually of some use;-)

{ Some drafts in my blog were hidden really deep, so… ;-) }

{ This story developed somewhere in July 2009… }

Twitter is an amazing… media? Social network? Means for ultra-fast transfer of news, wisdom, stupid things and “important” things like “I am drinking coffee now”? Something like IRC, but with an option for SMS, filtering, search, etc.?

Twitter is all of this simultaneously! :-)

Jeffrey Zeldman's hat…I am a Web designer and (partially) a geek, so it was very interesting for me to follow the discussion in two of the latest publications of Jeffrey Zeldman:

www.zeldman.com/2009/07/02/xhtml-wtf/
www.zeldman.com/2009/07/07/in-defense-of-web-developers/

…where the consequences of discontinuing the work on the XHTML 2 standard, and what will happen with XHTML 1.0, HTML 4.01, as well as with the new HTML 5, were passionately discussed.

At some point, in the Zeldman’s website, a strange bug appeared (in Firefox 3/Win): somewhere around 3/4 of the page with his last post and the numerous comments below, the content suddenly was disappearing (screenshot). Without a reason. The page itself was validating perfectly and there were no problems with the encoding or the HTML/CSS code.

Jeffrey noticed the problem, too, and was trying to solve it for quite a long time. The assumption that a problematic pingback with UTF-16 encoding was the culprit, was not confirmed.

I tried to investigate, too, out of curiosity, without any positive results, though.

Finally, I assumed that there’s a CSS bug in the rendering engine of Firefox/Win which (maybe) can be fixed with some new CSS rule. One of the readers of Zeldman’s blog mentioned that he tried to check something with Firebug, so I quickly made a test page + CSS file with the rule which (supposedly) was fixing this issue; then I tested in Firefox 3.0.11/WinXP. The problem was gone! :-)

Only one line fixed the problem for Firefox:

div#wrapper {
overflow: visible;
}

Then I’ve spent some more time to test in detail if the change did not affect any other popular browser (Opera 9.6, Safari 4, Chrome 2, IE7, IE6) and finally, I wrote to Zeldman, proposing him the fix for Firefox.

Zeldman replied:

@optimiced Will try as soon as I’m back on my feet. Thanks wise one.

Soon after that, Zeldman implemented the fix, and the design was fixed! :-)

Unfortunately, the fix introduced a new bug — the background of the page was “flashing” for a second or two on each page load because overflow: visible caused the background of the element #wrapper to load with a little delay (before: overflow: auto).

Well, after some more thought invested, I and another reader suggested two additional simple CSS solutions, which at a later stage proved to play very well together and fixed the “flashing problem” in all browsers — Firefox and Safari included! :-)

Last (but not least), I would like to say that Jeffrey Zeldman is a cool dude! After the whole story with the CSS bugs in Firefox and the red background flash was over, Jeffrey thanked me personally and added me to his Twitter list, and then promised to send me the new (third) edition of his popular book about Web Standards, as a present! (I think that somewhere in the CSS on zeldman.com there are some more acknowledgments hidden;-)

It’s always nice to communicate with such people, even if with messages only 140 characters long! ;-)

So, I am pleased to say, too: “Jeffrey, thank you!” :-)

* * *

Ah, and finally, why did I start this blog post with the question, what exactly is Twitter?

Because, after using Twitter for at least a few years, I can say that Twitter allows quick, precise communication in a new way. Comments in blogs, feedback forms, emails, allow us to communicate, too, but Twitter is something different. Something, which I cannot define precisely, but something, which fulfills its purpose and is also fun!

This is why you can (still) find me on Twitter (but you won’t probably find me on Facebook)… and, you can find me on my personal blog, of course! ;-p

XHTML 1.0 vs. HTML 4.01 (or HTML 5)?

Friday, May 15th, 2009

If you are a professional Web designer and create HTML/CSS code by hand for living, then you might be interested in the fact that Dave Shea switched from XHTML 1.0 to HTML 4.01.

It’s a fact that:

1) Lately, the HTML 5 standard gains up in speed.

2) XHTML 2.0 probably will never become a successor to XHTML 1.0. In fact, XHTML 2.0 probably will never exist at all.

3) Quite a few prominent Web designers and CSS/HTML coders are abandoning XHTML 1.0 and go back to HTML 4.01 (some of them even experiment very seriously with HTML 5).

What HTML standard for documents do you prefer? And am I the only one who (still) prefers XHTML 1.0 over HTML 4.01? :-)

It followed the interesting discussion at mezzoblue — I managed to read almost all of the comments there!

But, sometimes, it is not very clear to me as to where & why are going the Web Standards, guided by W3C.

After HTML 3.2, HTML 4.01 came, then the XHTML 1.0 standard was adopted, and now HTML 5 is developed? There’s almost no logic behind the versioning; plus, we have first the HTML language (which, in turn, derived from SGML), then W3C decided that it would be a great idea to combine XML + HTML (and so, XHTML 1.0 was ‘born’), and finally, they turn back to the idea of ‘pure’ HTML, and in the new standard (HTML 5), the ‘X’ is missing…

(more…)

The end of IE6 is soon?

Sunday, February 22nd, 2009

In the light of recent ideas that Web designers should spend less and less time, making fixes for Internet Explorer 6 (this browser is almost 10 years old already), I was curious to compare some browser stats for optimiced.com.

But first, a couple of words about the reasons why support for IE6 should be limited.

The Reasons

Dan Cederholm: How I Might Deal with IE6

Roger Johannson: No more pixel perfectionism in IE 6

Basically, the idea is as follows: Limit the time, which you dedicate to IE6, to the possible minimum. Yes, the design will look a bit different in this old browser, but so what? The important thing is that the design should work, and that there are no problems with the accessibility or functionality of the website.

In certain cases, you can even decide, if you wish to ensure a minimum support for IE6, or completely ignore it, in a similar way that Netscape 4.7x was ignored years ago, using the @import command for CSS styles.

For IE6, you can use IE conditional comments, like in this example:


<!--[if gte IE 7]><!-->
  <link rel="stylesheet" type="text/css" media="screen, projection" href="screen.css" />
<!--<![endif]-->

“Translated” to human language, this small piece of HTML code means the following:

If Internet Explorer is version 7 (or higher), the CSS file ‘screen.css’ will be loaded. Otherwise, the file won’t be loaded (IE6 or lower). All other browsers (Firefox, Opera, Safari, etc.) will load the file screen.css quite normally. I have tested this in Firefox 3, Safari 3.2, IE7, IE6, and the code works perfectly.

Here’s the test example

Open this page in Firefox, Opera, Safari or IE7+ — the background of the page should be green, and it means that the ‘screen.css’ file is loading normally.

Open the same page in IE6 (or even older version) — the background should be white, and it means, ‘screen.css’ is not loading for it.

And now about my browser stats.

I decided to check, how many site visitors of my personal blog are using Internet Explorer, how many of them are using version 6, and also, how stand up the numbers for Firefox and a few other popular browsers of today.

The Numbers

As a base for my comparison, I took the last month (Jan. 22 — Feb. 22 2009), and I also compared this period with the same period, but 1 years ago (Jan. 22 — Feb. 22 2008).

Firefox (Jan. 22, 2009 — Feb. 22, 2009): 56.18% of all visits
Firefox (Jan. 22, 2008 — Feb. 22, 2008): 49.79% of all visits
Firefox: +6.39% increase in number of visits, during a period of 1 year

Internet Explorer (Jan. 22, 2009 — Feb. 22, 2009): 33.47% of all visits
Internet Explorer (Jan. 22, 2008 — Feb. 22, 2008): 40.90% of all visits
Internet Explorer: -7.43% decrease in number of visits, during a period of 1 year

At the present moment, Opera is around 5%, Chrome is around 3.2% and Safari around 1.5% (of all visits to my site). All other browsers (Mozilla, for example) have so low numbers, that they can safely be ignored.

The tendency is clear. Firefox slowly, but constantly is increasing its influence, while Internet Explorer makes exactly the opposite. Safari, Opera, and also Chrome, are present in the whole picture, but quite modestly. Firefox and IE are the “big players”, or at least, this is true for my blog visitors… :)

Now let’s see the numbers for the different versions of IE.

IE7/IE8 vs. IE6

IE7 (Jan. 22, 2009 — Feb. 22, 2009): 55.22% from the total share of IE in the stats
IE7 (Jan. 22, 2008 — Feb. 22, 2008): 41.59% from the total share of IE in the stats
IE7: +13.63% increase in number of visits during a period of 1 year

IE6 (Jan. 22, 2009 — Feb. 22, 2009): 43.64% from the total share of IE in the stats
IE6 (Jan. 22, 2008 — Feb. 22, 2008): 57.18% from the total share of IE in the stats
IE6: -13.54% decrease in number of visits during a period of 1 year

The trend here is also clear: IE6 slowly loses grounds, while IE7 is becoming more and more widespread.

IE8 Beta also appears in the stats, but the numbers are very low — around 1%.

The Verdict

Firefox: 56.18% from all visits to the website
Internet Explorer: 33.47% from all visits to the website
— IE7: ~ 55% (of all IE visits)
— IE6: ~ 43% (of all IE visits)

In total, my users, which are using IE6, are less than 15%. All others use Firefox, IE7, Safari, Opera and Chrome.

Is 15% too low a number, so I can apply the CSS “filtering” for IE6? No, it is too early for that, I think.

But I guess that in 1-2 years the share of IE6 will become so low, that there really won’t be any point in trying to fix the XHTML/CSS code for it.

And then IE6 will become history, in a much similar way that Netscape Navigator 4.7x became history a few years ago — something which made me very happy at the time! :-)


[ optimiced.com is the virtual home of Web & graphic designer Michel Bozgounov | powered by WP & hosted by DreamHost | also available in български ]

0.536 / 25 / 22.5