Well, I've been using Safari Windows for a few weeks now, and I though it's time for a report. This report is only about the Windows version, because I can't install the Mac one. Why not? Because I don't have the right OS X version.
Browser news.
Includes:
Well, I've been using Safari Windows for a few weeks now, and I though it's time for a report. This report is only about the Windows version, because I can't install the Mac one. Why not? Because I don't have the right OS X version.
Yesterday I downloaded Safari 3.0 Windows as soon as I found out it was available. It looks fine. Below you find a list of CSS changes, as well as a curious bug that appears on a minority of Windows systems.
The MSIE team has asked for input on features that the next version of Internet Explorer should support. Please take a moment to help them out.
29 April 2006
Permalink | Explorer | 18 comments (closed)
Recently Erik Arvidsson lamented the lack of JavaScript progress in IE 7. Strictly speaking he's right, of course: there are few JavaScript bug fixes in the new release, because Microsoft has made CSS fixes its priority. Microsoft has done what it's promised, and it never promised us JavaScript fixes for this release.
That said, everybody knows there are a few things lacking in IE's JavaScript support. The point of this entry is to start creating a list with specific wishes for JavaScript improvements in IE. When it's done and when Microsoft starts thinking about the next version we can present it.
27 April 2006
Permalink | Coding techniques, Explorer | 13 comments (closed)
In a project I'm currently working on I encountered an Explorer bug that depends on the window you open a page with.
I post it here because I know that MSIE team members occasionally read my blog, and I have the faint hope that can they solve this bug, especially since it's messing up one of my projects (and, after all, what in the world is more important than my projects going smoothly <grin>, particularly when I have another important and exciting project that should be finished quickly but is held up by this bug).
Yesterday Microsoft released a new beta version of IE 7, confusingly called "IE 7 beta 2 preview - released on March 20th". I wish they'd named it beta 3.
Download it here. I haven't done any tests yet and I don't know when I'll be able to.
Despite being terrifyingly busy I found the time for some basic IE 7 beta checks this weekend. In general all CSS issues that Microsoft promised to solve have been solved, with the partial exception of the [attr] selector. The beta refuses to honour p[align=right] {font-style: italic;}. I updated my CSS compatibility table for the second time in two weeks.
I also went through all Explorer Windows bug reports and determined whether they were solved in the beta or not. I found that 58 old bugs have not been solved. See the Explorer 5-6 Windows and the Explorer 7 beta 2 category pages for more information. I also took the opportunity to remove a few reports that were orphaned for more than two months.
Finally, in JavaScript nothing much seems to have changed, although the crash on the normalize() method has been solved. I haven't yet done the rigourous DOM tests, that'll have to wait for another time.
The release of Explorer 7 beta 2 has raised some questions, especially about maintaining the various IE versions you may have on your computer. Basically the beta overwrites IE 6, and Joe Maddalone's Multiple IE instructions don't work, but you can uninstall the beta quite easily and IE 6 is restored to you.
I suppose I do a few people a favour when I write down clear installation and uninstallation descriptions and instructions. Here it goes:
Explorer 7 beta 2 seems to be available. I'm currently downloading it, so I have no test data yet.
I added an "Explorer 7 beta 2" category to the Bug Report. Please report any bug you find; the MSIE team needs you.
27 January 2006
Permalink | Coding techniques, Mozilla | 13 comments (closed)
One of my minor irritations with Mozilla is that it doesn't support a few DOM methods and properties that, though not officially a part of the spec, are nonetheless extremely useful and supported by all other browsers. I'm especially thinking of the contains() method and the children[] nodeList. While going through the more abstruse parts of the Level 3 Core spec today I found a way to add contains() to Mozilla.
24 January 2006
Permalink | Browsers, Content | 4 comments (closed)
iCab 3.0 is a surprisingly good, independent Mac (OS X and 9!) browser created by Alexander Clauss. It has good (though not perfect) CSS1 and DOM1 support, and to my surprise it even contains a speech browser. More than enough reason to recommend iCab to all Mac users that read my site, and to update my CSS compatibility table.
6 September 2005
Permalink | Coding techniques, Explorer | 21 comments (closed)
In a recent article on the IE Blog, Justin Rodgers talks about further CSS improvements in the ever more impatiently awaited IE 7 beta 2. His message is that CSS hacks will start to break in IE 7, and I fully agree.
Nearly two years ago I warned against the excessive use of CSS hacks, because I envisioned a situation like this. Web developers who rely on CSS hacks are going to have serious problems.
Apple just released Safari 1.3.1 without fuss. I found one important improvement over 1.3: the unload event, which was badly broken in 1.3, is now restored to its ancient reliability.
I didn't find any other significant updates in the CSS or JavaScript handling, but I did only a few very quick tests. If you found a change, please leave a comment.
Update: Safari used to download images with display: none only when they, or their parent element, were toggled to display: block. Unfortunately version 1.3.1 (and maybe 1.3) reverted to downloading the images anyway. Test page.
30 July 2005
Permalink | Explorer, WaSP | 33 comments (closed)
As everybody and his dog know by now, IE 7 Beta 1 has been released. Read Chris Wilson's entry over on the IE Blog for the details. Since I do not have a copy of it, I will not discuss it in detail. It is my strict policy to discuss only browser features and bugs I've actually seen for myself. Expect a full report as soon as I've got it installed on my computer, but not before.
The MSIE team seems to have used my site for bug testing, although almost all discussed bugs come from Position is Everything, and rightly so, since Big John and Holly Bergevin have far more interesting and detailed bug reports than my own CSS section.
Meanwhile this good news is being overshadowed by an apparently quite vicious campaign against Molly Holzschlag, who seems to have had the temerity to suggest that the IE 7 beta is actually good news for web developers and the standards movement in general, a message that encounters quite a bit of resistance among web standards fascists.
Over on the IE Blog Chris Wilson gives a few details on the upcoming Explorer 7 beta.
Two months ago I said that I didn't expect the Explorer 7 beta to contain solutions to CSS problems. Clearly I was wrong: Wilson announced support for alpha PNG channels and a solution for the Peekaboo and Guillotine bugs, and he indicated more goodies are to come.
So the Microsoft team is taking the opportunity to not only beef up security, but also CSS support. I'm curious, for one. Expect a full report on this site when the beta is available; and let's hope the CSS solutions we found for the Peekaboo and Guillotine bugs won't misfire in the new Explorer 7.
Opera 8 has been released. I tested it and found no differences with the beta I studied earlier.
Two days ago Apple's team launched Safari 1.3, being part of the OS X.3.9 upgrade (once again named after a fierce predator, but I forget which one). Despite numerous bug fixes, the new release is marred by extremely serious onunload problems.
In an interesting post in the IE Blog, lead program manager Chris Wilson explains the current state of affairs in the touchy realm of "IE and standards support". It's an interesting read, and he makes a few cogent points. He also calls for specific requests about standards IE should support, and I'm happy to oblige.
Today Microsoft, in fact Bill Gates himself, has officially announced Explorer 7, the fabled successor to Explorer 6 that everybody seems to have been talking about since 2002. Before jumping in the air from joy, let's see what Microsoft says and what it doesn't say.
24 January 2005
Permalink | Browsers, Content | 2 comments (closed)
I did the W3C DOM tests in Mozilla 1.75 and Opera 8b and updated the tables. Mozilla doesn't show much progress (then again, it doesn't have to show much, it's already the browser that supports the W3C DOM best). Opera is on the move again.
10 January 2005
Permalink | Content, Opera | 2 comments (closed)
I just downloaded Opera 8b (from this location), and since I now have two new browsers I updated a few compatibility tables.
I just downloaded and installed Mozilla 1.7.5, which, as far as I was able to determine, is the latest non-beta release. Over the next few weeks I'm going to go through the unenviable chore of updating all compatibility tables yet again. You may note that I did not download Firefox. In fact, I've downloaded it months ago and within a few minutes decided it's not going to become my default browser.
I thought I'd give you the current visitor stats for this site, gathered through the Reinvigorate system. Of course these figures are only valid for this site, and should never under any circumstance be used for any other site.
Category archives:
Monthlies: