Over at the Mozilla
Over at the Mozilla project, the drive for release 1.0 continues. The
Mozilla DOM team is looking for public input on which DOM 2 Core bugs
(
“http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Browser&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&keywords=dom2&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27Importance%27″>
here’s the list) are considered most critical and in need of
fixing before shipping Mozilla 1.0. If you’re a web developer who
depends on DOM 2 support for developing web applications, why not sign
up on the
“news://news.mozilla.org/netscape.public.mozilla.dom”>Mozilla DOM
newsgroup or Peter-Paul Koch’s
“http://groups.yahoo.com/group/wdf-dom”>DOM discussion list and
voice your opinions on what should be fixed pronto and what can slide
until later.
Previously: Doc Searls’ new approach