licentious radio

February 2003
Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28  
Jan   Mar

   Click here to visit the Radio UserLand website.
   Click to see the XML version of this web page.


"What kind of peace do I mean? What kind of peace do we seek? Not a Pax Americana enforced on the world by American weapons of war. Not the peace of the grave or the security of the slave. I am talking about genuine peace, the kind of peace that makes life on earth worth living, the kind that enables men and nations to grow and to hope and to build a better life for their children - not merely peace for Americans but peace for all men and women - not merely peace in our time but peace for all time." -- JFK
 
Home | Stories | Politics/Humor | Web Usability/Humor | ipaq 3800 Linux | RadioRadio | Typography | About | Contact
Web - Usability - Humor
Sunday, February 9, 2003
[1:31:09 PM]     
Rating links [technorati.com] to Shirky's article on weblogs.

Top links right now: Scripting News 1490, Boing Boing Blog 1085, Instapundit.com 609. Megnut is #6 with 267. licentious radio is #21 with 16. (That's the number of "inbound blogs".) We presume licentious radio's rank will fall as more websites link to the article. It's interesting how easy it is to find evidence of Shirky's point.

[12:08:22 PM]     
Here's a question I never saw the answer to: if you *know* your html is invalid, should you still add a DTD declaration?

In the old days, you could start with valid HTML, but then you would have to fix it up if you wanted it not to look horrible in Netscape and various other browsers.

The only actual use of the DTD that I knew of was that one very bad browser would refuse to display a page if it had a higher DTD number than it "knew". It didn't matter if it knew all the tags in use. It just would display the page.

I suppose the answer is that you *should* use a DTD for invalid pages, but it's hard to see what practical value this has had, up until now, or in the semantic future.

[11:58:09 AM]     
Update: This post was fundamentally wrong. You *can* use a transitional DTD without being thrown into quirks mode. You just have to know *which* way to specify the DTD. *Without* a URL, you get quirks-mode. You can get standards mode, or Mozilla/Gecko's 'nearly-standards' mode, by choosing the right DTD declaration. You just have to know. Here's the Mozilla/Gecko behavior [mozilla.org].

Cost of DTD hijacking.... (Choosing quirks mode based on transitional dtd considered costly.)

We have this problem of a gazillion web pages that were tailored to now-old browsers that were definitely quirky about rendering. "Quirky" being partly a euphemism for "non-standard".... A browser that does things *right* will suddenly gag on these old pages (render them ugly). So you might want the new browser to be able to render an old-fashioned page the way the old-fashioned browser rendered it. But how will the browser know to use quirks mode, not standards mode?

You use the DTD, was the answer. The DTD had (practically) never been used for anything, so why not?

I'm glad *I* didn't have to make a decision like that. For me, I would have been glad if a transitional DTD let me make pages that would work pretty well in non-CSS browsers, *without* enforcing old bugs (etc.) when someone uses a new browser to look at the page.

The example is you might want to use bgcolor, link, and vlink in the body tag, and even the despised but functional font tag. But if you use a transitional DTD, Mozilla duplicates various nasty 1997-era bugs. So now if I want to use transitional tags, I've got to do all the work-arounds that we hated before. In order to avoid the old bugs, you have to give up usability for old browsers.

Here's an example.... You put a div around the "content" part of the page, and style based on the div. Everything within the div looks fine, until you have some tabular data -- in a table. Because you use a transitional DTD -- in Mozilla and other browsers -- the text in the table cells doesn't get the styling of the div. That's not necessarily so bad, because you can style the contents of the table cells. But with the cascading nature of CSS, if a browser comes along that *doesn't* support quirks mode, the styles could be applied twice: .9em times .9em. So don't use ems, right? Ouch.

I have a different perspective on this than some. I don't care if old pages look bad in new browsers. People who want their websites to look pretty can update their pages, from my perspective. I would rather that it be easy to make new pages that follow standards with a bit of a nod to downward compatibility.

Like I say, I'm glad *I* didn't have to make these decisions, because I would have leaned the other way.

[10:07:39 AM]     
DaveNet Dave points to Shirkey on weblogs. I don't quite get Dave's point. Shirky says weblog readership is a "power law" deal, where very few weblogs get huge readership, and almost all weblogs get very little readership, with many weblogs in between. I guess Dave is saying that weblogs are more niche-oriented. But I thought that's what Shirky was saying, too.

[9:41:11 AM]     
Interesting claim on the Opera/MSN story.... They suggest MSN tweaked a stylesheet to work better with Opera 6. When Opera 7 came out, the tweaked stylesheet broke the layout, because of changes in the browser. I haven't tested this, but it sounds plausible (slashdot comment).

First, make your browser follow the standards. Second, when browser-sniffing, be aware that new versions will come out eventually, and the new versions will be specifically *different* than the current version. So limit your targeting to known versions. When Opera 7 comes out, give it some generic stylesheet until you take the time to figure out what you need to do to support it.

[9:12:33 AM]     
I guess that makes it official, then. I am the Anti-zeldman [google.com]. (ha ha)



Copyright © 2003 Licentious Radio.
Last update: 9/20/03; 3:00:48 PM.