w3future.com

Site Search
Site Colors
Site E-mail Me

Syn Atom 1.0
Syn RSS 0.91
Syn Subscribe

CC Licensed
Geo URL
With Radio

WYSIWYG editing in Mozilla

As a by-product of the Xopus project, Q42 has released code to enable basic WYSIWYG editing in Mozilla. It's not complete, because every special key has to be scripted individually. It's not very hard to add more features, and useful additions are welcome.

And back it is!

Ideas for RSS Evolution: "Sjoerd Visscher and Rahul Dave both offered the same convincing argument for global IDs instead of local ones, so I flipped it back." [Dave Winer]

Yes! Thanks Dave!

Give me back that GUID

I updated my Ideas for Evolution of RSS page, posted yesterday. I realized that there was no need for global uniqueness of the id's, that uniqueness to the channel is good enough [Dave Winer]

I liked a GUID much more. Sometimes one item ends up in more than one channel. With a GUID you can tell it is the same item. Also, once you have a GUID, you can build from that. If a post is a reply to another post, the RSS file could point to that other post (using f.e. an <inReplyTo> element).

Radio can output XHTML

It's a safe bet that none of these are Radio weblogs, since Radio makes it virtually impossible to output XHTML. [dive into mark/May 19, 2002]

That's not really correct. This is an XHTML Radio weblog. It's true that Radio doesn't help you to output XHTML, but it's far from impossible.

A bad use of fragment identifiers?

I received an e-mail from Paul Sowden, with his comments about the URIs for dynamic pages article. It is an interesting e-mail, because Paul's conclusion is exactly the opposite of my opinion. I'm showing here a large part of the e-mail.

A fragment identifier is the part of the URI after the '#' sign and they are used to scroll to a specific point on the page.

This statement is wrong, the fragment identifier is not part of a URL or its parent family, URIs.

The problem with changing the url is that the browser will unload the current page and do a new http request.

This is obviously what you would expect, the different URL is pointing to a different location and as far as the client is concerned, a completely different document. It would be wrong for the client to behave otherwise.

There's one thing the web gurus agree on. It's axiom 0 in Tim Berners-Lee's web architecture: "Any resource of significance should be given a URI."

This statement stays true due to my above statement. Your article is implying otherwise, that a fragment identifier can be used to signify a different document.

I think it would be extremely bad behaviour to use the fragment identifier to refer to a document other than that at the URI. The fragment identifier is only meant to reference material inside of the document at the current URI. Using the behaviour you have described, whilst it could be made to degrade and universily work, would be very bad, imo.

I've found a page on the w3c site that says: Formally, the URI does include the fragment ID. So there's no factual error. But "URI reference" would have been the better term.

My article is not implying that a fragment identifier can be used to signify a different document. The trick is using the fragment identifier to signify the same document, but in a different state. I think this is a proper use of the fragment ID, certainly when comparing it to the examples in the same w3c document:

For example, for a 3D object the fragment ID could give a viewport. For a music object, the Fragment ID could give a section in time, or a set of parts, or it could include a suggested tempo.

I cannot think of a more appropriate use of the fragment ID with framesets than indicating which documents it is showing. And for dynamic pages the fragment ID should indicate as much of the state of the page as possible. My opinion is that is better to use the trick, than not using it. Not only from a usability viewpoint, but also from a technical, semantic viewpoint.

:hover now works hierarchical

The annoying part for me is he proceeds to demonstrate using display:blocked anchors for box-shaped links and how easily a :hover style is applied, when my sidebar boxes (at least on the main page) have :hover styles that (again, at least in K-Meleon 0.6) only work if you don't mouse over the content in the boxes, just the boxes. Gah. [markpasc.blog]

Then I think you'd like to know this bug has just been fixed in Mozilla RC2.

AIM in Radio

Eric Soroos is implementing AIM in Radio. I've got it working, but I get a lot of TCP/IP errors. I want to use it to let Radio Userland send me notifications.

Trouble at home?

Rioting continues at the 'Binnenhof", where parliment sits. Protestors on the scene are blaming incumbent paolitical parties for his murder. It seems to be reasonable under control. Riots always look worse on tv at night. [Adam Curry's Weblog]

That's right. I live at the 'Buitenhof', right next to the 'Binnenhof'. And I'm just comming home. (1:15 AM) I was quite nervous to go home, because of the footage on TV about the riots. But thankfully there wasn't any noticable trouble anymore.

URIs for dynamic pages

I've put a new story online. It tries to give a solution to the problem of bookmarking and linking to dynamic pages.