On 5/13/12 5:44 AM, Anton Prowse wrote:
> There isn't much alternative to this,
Well, in fairness there is: Whenever such a limitation of CSS2.1 is hit,
errata CSS2.1 as needed and publish the updated version quickly. As in,
move it to more of a "living spec" model. As long as the changes are
just adding new definition hooks, this should be pretty safe in terms of
not making existing implementations non-compliant (a common complaint
about the "living spec" model), have low overhead, and not block other
specs too much.
-Boris