Quote:
Originally Posted by DiapDealer
There is no switch we can throw to tell WebKit to be "less forgiving" about css syntax errors.
|
And this is the fundamental problem. The "viewer" software used by the consumer that purchases the book needs to be able to deal the best it can with whatever gets thrown at it.
But as a content creator, you want every potential problem revealed. There is really a need for two different types of e-pub renderers.
Are there other alternatives to WebKit? Or are they all targeted at the consumer?