- From: Gareth Hay <gazhay@gmail.com>
- Date: Fri, 27 Apr 2007 15:48:31 +0100
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, Doug Schepers <doug.schepers@vectoreal.com>, public-html@w3.org
On 27 Apr 2007, at 15:35, Henri Sivonen wrote: > >> Surely any browser manufacturer is always going to have a mode >> that will render older pages. >> What is preventing them having an HTML5 mode, which may or may not >> build upon their previous engine. > ... >> Why is this a problem? > > The problem from the browser vendor point of view is the increased > cost of code development and the increased cost of quality assurance. > Ok, I 've asked before, so I'll ask again, how? option 1. Add HTML5 on top of current code, adding more complexity to current code base. option 2. stop existing code. Begin HTML5 parser (starting from what we have, but forking) I don't see either being a signifignatly different cost.
Received on Friday, 27 April 2007 14:48:46 UTC