Linked by David Adams on Tue 23rd Sep 2008 00:57 UTC
From eWeek: "In a session billed as the browser wars up close and personal, key Microsoft, Mozilla and Google representatives spoke about the past present and future of the browser platform as they see it . . . one of the issues that stood out to me was that of developer discontent. When the Ajaxians opened up questioning to the audience, an attendee stood up and said Google's announcement of its new browser "was greeted with shock and horror," by him."
Thread beginning with comment 331305
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
SVG is an event scriptable 2D scene graph, and it can be parsed and rendered (with pixel precision if need be) as quickly as any other 2D scene graph, and faster than a 3D scene graph because 2D doesn't have to consider as many values. The problem so far has been that implementations suck.
In no way, shape, or form is this an advantage.
Not only that, but an SVG element can be made to model the Canvas behavior you described simply by setting overflow:hidden, which is even the DEFAULT if I'm not mistaken. On the other hand, it is not possible to get Canvas to model the behavior an SVG element has when set to overflow: visible|auto.
For the life of me, I cannot understand why the browser hasn't evolved into a generic scene graph renderer at this point.