willCode4Beer

Citing with Quote and Blockquote

There as been a lot of debate about the quote tag (<q cite="http://willcode4beer.com">my quote</q>). Many are upset that Internet Explorer doesn't render it correctly, others argue, "who cares". Though semantic mark-up is often at the center of the debate, often missed is, why have a quote tag in the first place.

To render quote marks doesn't really make a strong argument. The rendered quote characters can depend upon a user's language. Doesn't it make more sense to render quotes with the language of the article being read? Besides, the rendering can be fairly easily dealt with using behaviors or javascript (as my page on fixing quotes in IE shows).

Back to the semantics. There is an attribute of the quote tag meant to refer to the source of the quote. The specification says that the attribute should be a URL. However, none of the browsers, including those that render quote characters, do anything with the CITE attribute.

The blockquote tag doesn't suffer from the debate. However, its cite attribute is still unused.

So, we have this wonderful piece of contextual, semantic information but, the browser provides no way for a user to make use of it, and the average user doesn't even know the information is available.

I built a citation tool-tip script to make floating tool-tips with the cite attribute hyper-linked and with the tag title as a title in the tool-tip. But, isn't this really a work around of what the browser should be doing anyway?

Maybe the next step should be a browser plug-in/extension that can show a "citations" sidebar. This could easily show what is cited and provide navigation to the citation.

I wonder, how many people actually use the "cite" attribute anyway...

--Paul

Labels: development, html, javascript, standards

posted by willCode4Beer @ 2:08 PM

0 comments

Safari on Windows

I just installed the beta3 of Safari for windows. I usually just use Konqueror as a Safari stand in (they both use the KHTML rendering engine). However, using a stand in is always a bit risky but, I'm just not going to buy a Mac only to test web pages.

So far, for my pages anyway, it appears to render my pages the same as Konqueror. It does appear to have some newer features (or maybe my Konq is out of date). I see the opacity in CSS is working (woohoo! my DHTML fading tricks work on it). The XML/XSLT transform appears to be at least as good as Firefox/IE (completely broken in Konq). I'll find more as I experiment with it.

I've tried to give a little bit of a shakedown though, nothing thorough. I like it if a browser can support common (to me) keyboard shortcuts.

• ctrl-l and alt-d will bring the focus to the address bar
• ctrl-k puts the focus on the search bar
• ctrl-t starts a new tab
• ctrl-w will close the current tab
• alt-left/right arrows nav forward and backward

Those are the things I use most frequently so, it seems to be holding up. Currently, my only beef is when using 'windows-m', which should minimize every window, I find Safari still sitting on top (bummer).

At first glance, it appears to be a decent addition to the web browser collection. More variety is a good thing.

Labels: browser, html, safari

posted by willCode4Beer @ 6:55 AM

3 comments