They may have arrived late to the party, but Microsoft are keen to make their presence known, and in an effort to show just how engaged with the web standards community they are, or perhaps more a chance to try and gain one up on the competition, have published a set of results (on the 5th may) outlining not only how great IE9’s performance in a number of test cases is, but also just how badly the competition compare.
A recent editors draft of the CSS3 Background and Borders module (published on 5th may) indicates that the box-shadow property could be set to make a reappearance before the specification is released as a Proposed Recommendation.
The specification also features several other updates including the addition of a ‘content-box’ value to the background-clip property, changes to the background shorthand syntax for background-clip and background-origin, and the removal of a recommendation to use gradients for color transitions when border-radius produces a curve, further details below.
Last week also saw the release of an updated working draft of the CSS3 Template Layout module, read on for further details.
The platform preview, downloadable from the Internet Explorer website, comes with a number of demonstrations including those for CSS3 border-radius and selectors. The preview also scores an impressive 578/578 on our CSS3 Selectors Test and an improved 55/100 on the Acid 3 test, with further improvements promised before the final release.
CSS3 Please!, produced by Paul Irish and Jonathon Neal, aims to simplify the design process by allowing designers to enter one value, and have this instantly synced and normalised for each vendor-specific prefix, with the corresponding code generated automatically.
The tool offers support for border-radius, box-shadow, linear-gradients, rotation, rgba colors and @font-face, with work underway on support for skew and scale. In some circumstances the tool also offers support for Internet Explorer using IE filters to replicate the same effects as achieved by CSS3 properties. CSS3 Please! has been gaining a significant amount of interest around the blogosphere since its launch earlier this week.
The announcement of our redesign last month received an overwhelming number of comments, with the majority expressing negative feedback. The main concerns raised were that the new design was too dark, lifeless / boring and lacking in fun, spirit and character.
As previously stated, the main reason for the redesign was from a functional perspective to allow us to expand the site and take it forward. The reason that the old design was removed, and not simply recoded to make the functional changes required, was in fact due to a number of negative comments I had received about the previous design since taking over the site in July 2009, however following the large number of comments received over the last three weeks in support of the previous design, it is now apparent that these negative comments were not representative of the views of the majority of our readers. With this in mind I have made the decision to temporarily reinstate the old design whilst considering the best way to move forward with the site.
Research in Motion, manufacturers of the popular BlackBerry smart phone series, have announced plans to launch a new web browser for their phones based on the open source WebKit layout engine, and offered delegates at this weeks Mobile World Congress a sneak peak (see the video at the end of this post).
His ie-css3.js project (currently in beta) allows Internet Explorer, versions 5 through 8, to identify CSS3 pseudo-class selectors and render any style rules defined with them. All this is achieved by simply including the script, along with Robert Nyman’s DomAssistant, within the head element of your web pages.
As you may (or may not) know, I’m an Invited Expert on the CSS Working Group at W3C. Mostly I talk about specs. But today, I’m going to talk about testing.
W3C is working on test suites for the CSS specs, and I wanted us to have more web authors involved. Many of you have been frustrated with the inconsistent levels of CSS support across browsers, and I believe collaborative testing is one of the major ways we can improve the situation.