The forth coming Firefox 3.5 brings with it a slew of DOM and CSS advances, while not forgetting to mention the rendering and JavaScript speed improvements. These improvements ratchet up the competition for Adobe’s Flash and Microsoft’s Silverlight. (Silverlight? I’ve never found a site that uses it yet.)

Firefox 3.5 adds support for the HTML 5 audio and video elements and now fully supports the HTML 5 offline resource specification. Rich internet applications here we come.

The full list of improvements can be found on the Mozilla page Firefox 3.5 for Developers.

Google Chrome Browser

The internet is a buzz since Google's release yesterday of its browser named Chrome. There are many wild predictions about its future, what it means for Microsoft and Firefox and a share of nay sayers. I downloaded and to it for a test drive myself. But I waited a day to see what reactions would be and if more detailed information came to light before I went shooting my mouth. Overall the reaction seems to be very positive.

A number of things stand out about Chrome.

1. On the surface, its page rendering seems fast. It uses WebKit
2. Browser tabs are spawned as separate tasks. This the most talked about feature so far, because it means that if one website's scripts are running slow, the other tabs will not slow down. The problem child can then be killed off. This point gets my vote.
3. Chrome uses the V8 JavaScript engine. It means Chrome has speed advantages over many of the other browsers.

The general consensus seems to be that the new browser is clear pitched at web applications, and specifically web applications that continue to work when off line. Many see this as the way of the future, where applications are not tied to any one particular operating system, and are available anywhere, any time.

The browser then coupled with Google's Gears, a collection of web widgets, clearly puts in competition with Adobe's Air and Microsoft's Silverlight. As JavaScript engines become faster and if a standard HTML video element was adopted, the future looks dim for these two proprietary platforms. This is one point that seems to have garnered much applause from the technical community.

The next thing that seems to be rather sensational and wildly exaggerated, is that Chrome is Window's killer. As many people have pointed out, Chrome needs an operating system to support it. So Windows is not about to go away. But, where it does spell trouble for Microsoft, is when Chrome and other browsers create a fast, stable platform for web based productivity software, its Office cash cow is in serious trouble.

For me, it has been interesting to use Chrome for the past day, but four things stop me from using it more regularly.

1. No add ons – I love my Firefox ad blocker, Firebug development debugging tool, as a developer, I can't live without this one.
2. Its CSS rendering is not up to date. It fails the Acid 3 test. My WordPress admin theme does not work properly. So I'm using Firefox right now to write this.
3. There seems to be some JavaScipt incompatibility, some of the WordPress Editor Monkey features didn't work.
4. I can't install Flash. While this Chrome is meant to ultimately mean the demise of this platform, the nearly the whole internet still uses it. For instance, Google's own Analytics.

None of the other browsers are sitting still, so the competition is on. I believe we can expect to see some amazing developments from all of the browsers in the near future.

Firefox 3 is in its final stages of Alpha development with a host of new features and improvements.

Mozilla has unveiled for the first time several security features it's talked up for months. Among the security provisions are built-in anti-malware warnings and protection against rogue extension updates. 

Debuting is Places, the name given to the new unified history and bookmark manager. Unlike current browser bookmark tools, Places will use a database — the SQLite database engine powers it — so users can search for saved pages. Places will also support the use of tags, or user-defined labels that are applied to categorize bookmarks and make them easier to retrieve via searches.

On offer is also a new download manager that will integrate with third-party virus scanners and malware protection.

The graphical rendering of Firefox also gets an update with the Cairo rendering engine and animated PNG image files. The versatile Cairo graphics library is a vector-based drawing API that supports a wide variety of backends. Cairo can take advantage of hardware acceleration where available and simplifies cross-platform graphics application development by providing an internally consistent and cohesive framework that emphasizes platform-independence.

Thanks to this new graphics infrastructure, boxes with corners rounded by the pre-CSS 3 property border-radius are rendered with beautiful anti-aliasing (currently accessible as the non-standard -moz-border-radius and soon -webkit-border-radius). Cairo also provides smooth scaling of images. Up until now scaled images looked jagged.

The new improvements in Firefox 3 will finally enable it to pass the Acid 2 test, a CSS test case developed by the Web Standards Project to illuminate flaws in HTML/CSS rendering engines. To pass the Acid 2 test, browsers must comply with W3C standards and provide support for a wide variety of features that are considered relevant by web designers. The Acid 2 test has been passed by several other browsers, including Safari, Konqueror, and Opera, but not Internet Explorer. Passing Acid 2 is considered to be a significant milestone in Firefox development.

Firefox 3 has particular implications for the development of the Mac version of Firefox, as it provides support for the use of Cocoa Widgets.

One downside of Firefox 3 is that several older operating system versions are no longer supported: Windows 95, 98 and ME and OS X 10.2 Jaguar. 

Mozilla has not officially committed to a release date for the final version of Firefox 3.0. 

I'm a fan of WordPress. It produces clean extensible markup. It also has huge user base, and consequently a developer base also.

However, I've always found the admin rather ugly, and its navigation menu rather annoying, as I miss having the easy access to sub-pages via a drop down menu system. So after doing a little googling, I finally located two plugins which give me a look and feel that I've been craving. Tiger Style Administration by Steve Smith provided the slicker look, and Admin Drop Menus by Andy Staines provided the drop down menus

On first activation of both WordPress plugins, they don't appear compatible. After closer inspection, the solution to their happy co-existence lay in making modifications to the Tiger Style Administration CSS.

After activating the two plugins, and implimenting this modification, my client feedback was overwhelmingly positive, making WordPress far more intuitive to navigate.

 I'll post the CSS solution soon.