What an absurd case, so glad it would found in Eyeo's favour.
> More dangerous still, any developer who writes code for an offending browser feature could be liable to pay damages
If you take this one step further, any browser vendor would be liable for changes to their product if that change broke a person's site, i.e. deprecation of any features. The mind boggles at how horrific it could've been for the future of the web.
And worse yet, imagine you're liable for not supporting each and every new web standard that there is 100%, right away. Just to illustrate how absurd such a ruling would have been.
> More dangerous still, any developer who writes code for an offending browser feature could be liable to pay damages
If you take this one step further, any browser vendor would be liable for changes to their product if that change broke a person's site, i.e. deprecation of any features. The mind boggles at how horrific it could've been for the future of the web.