DISQUS

Hello Mr Al Billings,

I'm against a public bug reporting database at Microsoft regarding Internet Explorer at this time for some of the reasons you have given yourself in your own post:
- noise/signal too high
- duplication/high frequency of duplicated bug reports (on the same issue)
- disconnection of the team IE dev. members from reporters in several ways: the community reporters are blind while the IE dev. team is mute.

OTOH, I am all for that Microsoft IE dev. team creates an internal database from all the bugs which are (and have been) explained, are documented, with testcase coming from web developers themselves:
- bugs that create application crash, hang, cpu maxed in MSIE 7: those bugs exist and are already publicly reproducible in testcases. So, it's all up to Microsoft to wake up and to fix those
- bugs that creates usability and/or accessibility problems
-
- collapsing adjoining margins implementation: this affects almost every single CSS columnar webpage template
- float implementation
- inherit implementation
- background (background-image, background-color) implementation
- position and z-index implementation
- CSS inline box model bugs

I've said this same thing in many places repeatedly. With *_so many_* documented, reproducible, testcase-ed bugs, specs violations occuring in MSIE 7, there is no need right now to create a public database.

You want people to start talking about IE 8? I'm against that. Talking is good when you need planning, establish a roadmap, a schedule, a to-do list, etc. Action is what is needed now, not talk. Bug fix is what's needed now, not talk. Some of the bugs and spec. violations (HTML 4, DOM 1 & 2, CSS 2.1) regarding MSIE 7 have been reported, explained and documented for over 9 years now. Why would we or should we need to talk about this again?

I'm for monthly build available for testing purposes. But then again, it won't mean much if already reported bugs - for many years - and there are hundreds of them - still have not been fixed.

Regards,

Gérard Talbot

Deb, I confirm that there are layout problems of the navigation links when using the latest IE 7 beta 2 build 5346.5.

Note that the javascript console report CSS parsing errors:

#navigation #personal a {
_width: 1%;
}

_width is not a CSS property.

Warning: Unknown property '_width'. Declaration dropped.
Source File: http://developer.mozilla.org/css/base.css
Line: 194

Gérard