Slashdot Mirror
Mozilla 0.9.7 Released!
Chezypewf writes: "The newest release from the Mozilla Dev team is out. This milestone features basic S/MIME support, favicon support and the Document Inspector, a tool to inspect and edit the live DOM of any web document or XUL application. You can grab it here: http://www.mozilla.org/releases "
Can you guess which one stops pop-ups?
Would a usability expert know what half these prefs mean?
Good job on the prefs, Moz-team, but please, hire Jakob Nielsen before 1.0 ships.
Honestly, I want the core frozen absolutely solid. Then declare 1.0. While I love all the features that have been put in to the UI, what really needs to happen for 1.0 in my opinion is to stabilize that API so people can start coding around the platform.
The original vision is still critical, and I want to see more projects like the fantastic pubmed. These things are going to be what really kicks mozilla in to high gear. I really believe that third party stuff like this will make mozilla worth having.
1.0 is all about stability. The browser itself is certainly stable enough to go 1.0. You can add the UI enhancements for 1.1, but make the core solid so people have the platform. Then we'll start to get the plugins that we so desperately need too.
"I may not have morals, but I have standards."
I've been using nightly builds and home cvs builds of Mozilla on Linux for some time now. It's support for CSS and the W3C box model leads a great deal of people into believing that Mozilla has many bugs because IE5/6 renders there pages fine. They don't realise it's IE5/6 rendering it wrong because their code doesn't do what they mean it to do...
If there is one thing I'd like to see improved in the next release of IE it's CSS selector support. CSS Selectors level 3 is basically finished, Mozilla supports most level 2 selectors, and yet IE6 trails with very limited support. Yes, you can select an element that is within another element (descendant selectors) but IE6 lacks support for a huge array of other selectors such as child, sibling and selectors based on attribute value(s).
This selectors point may seem very trivial to web authors used to writing for IE because they merely give an element a class and write a new rule for it. But that bloats the HTML/XML significantly, and can give the programmer a headache, not forgetting the problems of handling inheritance propeties.
With CSS2 selectors, I can say, td[class ~= "body"] > p:first-child { font-weight: bolder; } and have the first paragraph child of a table cell who's class attribute contains a value "body" go bolder. I can't do that in IE6 as effectively.
C'mon Microsoft, you helped create the selectors standard, now let's see you implement it!
Its always been relatively trivial to do that, I showed that more than a year ago and I know some have implemented similar techniques to prevent any window opening under any circumstances and show the link in the existing window.
The problem with the wording is not that its inaccurate, its entirely accurate. The problem is that the user is searching for something to stop windows opening and so naturally grabs at whatever seems reasonable. After that assumption is made they are going to be satisfied 80% of the time but consider the actual behaviour a bug because windows can still be opened.
Simon