Twitter is all of this simultaneously! :-)<\/p>\n
www.zeldman.com\/2009\/07\/02\/xhtml-wtf\/<\/a> …where the consequences of discontinuing the work on the XHTML 2 standard<\/a>, and what will happen with XHTML 1.0, HTML 4.01, as well as with the new HTML 5, were passionately discussed.<\/p>\n 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<\/a>). Without a reason. The page itself was validating perfectly and there were no problems with the encoding or the HTML\/CSS code.<\/p>\n Jeffrey noticed the problem, too, and was trying to solve it for quite a long time<\/a>. The assumption that a problematic pingback<\/a> with UTF-16 encoding was the culprit, was not confirmed.<\/p>\n I tried to investigate, too, out of curiosity, without any positive results, though.<\/p>\n 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<\/a>, 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! :-)<\/p>\n Only one line fixed the problem for Firefox:<\/p>\n 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<\/a> to Zeldman, proposing him the fix for Firefox.<\/p>\n Zeldman replied<\/a>:<\/p>\n @optimiced Will try as soon as I’m back on my feet. Thanks wise one.<\/p><\/blockquote>\n Soon after that, Zeldman implemented the fix, and the design was fixed! :-)<\/p>\n Unfortunately, the fix introduced a new bug<\/a> — the background of the page was “flashing” for a second or two on each page load because 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! :-)<\/p>\n 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<\/a>, and then promised to send me the new (third) edition of his popular book about Web Standards<\/a>, as a present! (I think that somewhere in the CSS<\/a> on zeldman.com there are some more acknowledgments hidden;-)<\/em> <\/p>\n It’s always nice to communicate with such people, even if with messages only 140 characters long! ;-)<\/p>\n So, I am pleased to say, too: “Jeffrey, thank you!” :-)<\/p>\n * * *<\/p>\n Ah, and finally, why did I start this blog post with the question, what exactly is Twitter?<\/p>\n 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!<\/p>\n![\"Jeffrey](\"https:\/\/www.optimiced.com\/wp-uploads\/2009\/09\/jeffrey-zeldman-hat.gif\")
<\/a>…I am a Web designer and (partially) a geek<\/em>, so it was very interesting for me to follow the discussion in two of the latest publications of Jeffrey Zeldman:<\/p>\n
\nwww.zeldman.com\/2009\/07\/07\/in-defense-of-web-developers\/<\/a><\/p>\n\r\ndiv#wrapper {\r\noverflow: visible;\r\n}\r\n<\/pre>\noverflow: visible<\/code> caused the background of the element #wrapper<\/code> to load with a little delay (before: overflow: auto<\/code>).<\/p>\n
![screenshot<\/a>). Without a reason. The page itself was validating perfectly and there were no problems with the encoding or the HTML\/CSS code.<\/p>\nJeffrey noticed the problem, too, and was trying to solve it for quite a long time<\/a>. The assumption that a problematic pingback<\/a> with UTF-16 encoding was the culprit, was not confirmed.<\/p>\nI tried to investigate, too, out of curiosity, without any positive results, though.<\/p>\nFinally, 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<\/a>, 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! :-)<\/p>\nOnly one line fixed the problem for Firefox:<\/p>\n\r\ndiv#wrapper {\r\noverflow: visible;\r\n}\r\n<\/pre>\nThen 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<\/a> to Zeldman, proposing him the fix for Firefox.<\/p>\nZeldman replied<\/a>:<\/p>\n@optimiced Will try as soon as I’m back on my feet. Thanks wise one.<\/p><\/blockquote>\nSoon after that, Zeldman implemented the fix, and the design was fixed! :-)<\/p>\nUnfortunately, the fix introduced a new bug<\/a> — the background of the page was “flashing” for a second or two on each page load because overflow: visible<\/code> caused the background of the element #wrapper<\/code> to load with a little delay (before: overflow: auto<\/code>).<\/p>\nWell, 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! :-)<\/p>\nLast (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<\/a>, and then promised to send me the new (third) edition of his popular book about Web Standards<\/a>, as a present! (I think that somewhere in the CSS<\/a> on zeldman.com there are some more acknowledgments hidden;-)<\/em> <\/p>\nIt’s always nice to communicate with such people, even if with messages only 140 characters long! ;-)<\/p>\nSo, I am pleased to say, too: “Jeffrey, thank you!” :-)<\/p>\n* * *<\/p>\nAh, and finally, why did I start this blog post with the question, what exactly is Twitter?<\/p>\nBecause, 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!<\/p>\nThis 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<\/a>, of course! ;-p<\/p>\n","protected":false},"excerpt":{"rendered":"…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…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,16],"tags":[],"class_list":["post-588","post","type-post","status-publish","format-standard","hentry","category-css","category-webdesign"],"_links":{"self":[{"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/posts\/588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/comments?post=588"}],"version-history":[{"count":3,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/posts\/588\/revisions"}],"predecessor-version":[{"id":598,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/posts\/588\/revisions\/598"}],"wp:attachment":[{"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/media?parent=588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/categories?post=588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.optimiced.com\/en\/wp-json\/wp\/v2\/tags?post=588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/www.optimiced.com\/web\/2009\/zeldman\/zeldman-screen.jpg\"){kind=link}
![Twitter list<\/a>, and then promised to send me the new (third) edition of his](\"https:\/\/www.optimiced.com\/wp-uploads\/2009\/07\/twitter-zeldman.jpg\"){kind=link}