Skip to page content or Skip to Accesskey List.


Main Page Content

Changing Times An Update

Rated 3.89 (Ratings: 0)

Want more?

Picture of persist1

Ben Henick

Member info

User since: 24 Jan 2000

Articles written: 9

Having shot off my mouth, I did some research.

Here's what I've found so far:

  • According to Jakob Nielsen [ed. note: Stuck With Old Browsers Until 2003], Mozilla is unlikely to ever supersede Communicator 4 in terms of market share. Can this prediction be proven wrong? I think it can.
  • Specific and clear documentation on what Mozilla wants from JavaScript to access the DOM is still lacking [ed. note: Get Ready for Navigator 5.0 DHTML]. W3C explicitly calls for something along the lines of 'document.tags.elementType' (my paraphrase), but I at least am still without a clue.
  • There seems to be a lot of worrying about how code written for Mozilla can be made backward-compatible with Communicator 4... which is exactly what I would hope to avoid.
  • My earlier post completely ignored the role of the Web Standards Project (WSP). The omission was deliberate, and in truth I rather suspect that the happiness of the WSP has hardly been on the radar of the folks who coordinate and contribute to the Mozilla build. At the same time, I failed to give credit where it was due.

Another question has to do with the average skill level of the developers out there. If the developers who can write cutting-edge sites take an action such as the one I've proposed, will folks actually notice?

Any follow-up on these points is more than welcome.

The access keys for this page are: ALT (Control on a Mac) plus: is an all-volunteer resource for web developers made up of a discussion list, a browser archive, and member-submitted articles. This article is the property of its author, please do not redistribute or use elsewhere without checking with the author.