MozillaZine

Links Toolbar Landed

Wednesday October 3rd, 2001

Gervase Markham writes: "The Links Toolbar from bug 87428 has finally landed, bringing us ever-closer to full support for HTML 2.0. You'll see it in this morning's builds. The auto-show is still in development over in bug 102832. Good places to try it out are Bugzilla buglists, the W3C, htmlhelp.com and many machine-generated manuals or documents, such as the GNU Make manual."


#64 Re: Re: Re: Cool, but ...

by choess <choess@stwing.upenn.edu>

Friday October 5th, 2001 12:26 AM

You are replying to this message

>>Here's what HTML 4.01 says about the LINK tag at (LINK) : "Although LINK has no content, it conveys relationship information that may be rendered by user agents in a variety of ways (e.g., a tool-bar with a drop-down menu of links)." There is no requirement that they be represented by the user agent at all -- that's what the word "may" means. RFC's are very precise with language like "may," "should," and "must."<<

This argument is fallacious-see the comments at the bottom of bug 7954. The requirements imposed on user agents by HTML 4.01 are actually very small-a UA that didn't implement any SHOULDs wouldn't be much use. HTML 4.01 uses RFC-requirements language, but does it badly (much like it uses SGML).

>>I think it's more accurate to say that, like many immature engineering organizations, Netscape/Mozilla lacks the discipline to stop adding new things and just fix and polish what's already been added at the right stage of the project. Those of us who've been through this perennial engineering conundrum know that it's a recipe for shipping an unstable product, or never shipping at all.<<

Um, well, no. Free clues: 1) This wasn't written by Netscape people. It's been under development by outside contributors for quite some time (see bugs 2800 and 87428 for the gory details). 2) It was checked into the tree on 10/4/01, caused a performance hit, and was disabled because of it. It's now back in, modulo two performance patches and a couple of polish patches. IOW, the feature *WAS* halted because it was found not to be sufficiently polished; now it is.

Please take the "you guys can't design and manage software" horse you rode in on and go back where you came from.

(FWIW, a commentary on a similar UI feature is here: <URL:<http://www.useit.com/papers/icab.html>>)