A new draft of the Compound Document Framework and WICD Profiles was released last week by the W3C and is available here. CDF/WICD (or whatever they end up calling it) is an important specification that will help to define how browsers should deal with "compound documents". An example is an XHTML document that has SVG elements embedded in it. As XML continues to replace HTML as the language of the web, such a specification becomes more and more important.
And it's great bedside reading, too!
Via the Yahoo! SVG Developer mailing list.
Now that Firefox 1.5 Beta 1 is making its way to the more general public, an increasing number of people are wondering why they are not able to see some SVG content in the Firefox browser. Apparently the SVG examples on Adobe's SVG Zone are the biggest culprits, with a Mozilla representative stating that they are non-compliant, yet are rendered by the less-strict Adobe SVG Viewer. An Adobe representative has admitted that the SVG content on their websites are largely non-compliant, that they had been informed several months ago but have not been able to update the content to make it compliant. Read the rest of this entry ...
The Mozilla SVG project is again calling for testing of another patch for SVG functionality:
It looks like SVG Events made it into Firefox 1.5, but it's not clear whether textPath or filters would make it into the branch (Firefox 1.5) or if it would just remain in the trunk (Firefox 2.0 development branch). Go download the latest nightly trunk build (i.e. Firefox 2.0 development branch) and test it out.
Looks like Firefox 1.5 Beta 1 (supporting a large portion of SVG 1.1 Full) will be released in less than a week: September 8th.
Also, the Renesis Viewer Beta 1 (supporting at least SVG 1.2 Mobile) will likely happen in November timeframe, with a stretch goal of October.
The Mozilla SVG project is calling for testing of two patches for SVG functionality:
Feedback will help determine whether this functionality makes it into Firefox 1.5, so if you're brave, go download the latest nightly trunk build (i.e. Firefox 2.0 development branch) and test the functionality out.