I wouldn't be surprised if Vista RC1 comes out soon after the IE7 release, as I hear it's "imminent".
Speaking of IE7, I've had some feedback from Microsoft about my rant over the lack of standards compliance in the browser. I'm still not sure where IE7 is at when it comes to supporting the various standards, but I do think Microsoft is working hard to make it so. Trouble is, the base they're starting from seems to be IE6, which is a disaster area in that respect.
Anyway, Markus Mielke, IE7 Programme Manager, writes on IEBlog listing some of the things that have been fixed plus CSS changes, namely:
- Peekaboo Bug
- Internet Explorer and Expanding Box Problem
- Quirky Percentages
- Line-height bug
- Border Chaos
- Disappearing List-Background bug
- Guillotine Bug
- Unscrollable Content bug
- Duplicate Characters Bug
- IE and Italics
- Doubled Float-Margin bug
- Duplicate Indent bug
- Three pixel text jog
- Creeping Text bug
- Missing First letter bug
- Phantom box bug
Plus many, many more - see the link above for the full list.
It's a good clean-up effort, but it makes me wonder why Microsoft persists with the "Trident" rendering engine instead of writing a new one.
As for IE6, another IE programme manager, Tony Chor writes on IEBlog that there's an update coming up for it soon:
You may have read reports of a new, irresponsibly disclosed vulnerability that affects IE 6.0 SP1. We are aware of this issue and are actively working on an update that addresses the problem, which was introduced with our last security update (MS06-042). This issue only impacts customers running IE 6.0 SP1; customers running Windows XP SP2, Server 2003 SP1, IE 5.01 on Windows 2000, or any of the IE7 betas including Windows Vista are not affected. As far as we know, there are no active exploits at this time. The Microsoft Security Response Center (MSRC) has released security advisory 923762 with guidance for customers on this issue.
Briefly, after the initial release of MS06-042, we were responsibly informed of a potentially exploitable security vulnerability via a crash in urlmon.dll; we also started receiving reports of customers running into the crash during normal usage. As a result of the security and reliability impact of this bug, we decided not to wait for the next normally scheduled update. We had planned to release the update today, but last night we found an issue that would prevent some customers from being able to deploy the update. As a result, we decided to hold the release until it meets the appropriate level of quality for such a broad distribution.
Other related posts:
Video: Kim Dotcom and Mathias Ortman at the IITP Mega breakfast
Two-factor authentication broken
The problem with naming and shaming
comments powered by Disqus