News for hackers. Stuff that matters.

A comment on The birth of Microsoft's new web rendering engine. Parent comment

Re:The birth of Microsoft's new web rendering engine by joshuacc on Thursday February 26, 2015 @02:35PM (#9114827)
Because the vendors sometimes proposed incompatible variants of the same feature before it was standardized. And they would implement it behind their individual prefixes so that you could experiment with both the IE and FF variants, for example.
[ Parent | on HN ]
Re:The birth of Microsoft's new web rendering engine by bsimpson on Thursday February 26, 2015 @04:58PM (#9115831)
If you don't implement the same spec, bump the version. This is not a complicated idea.

Instead of -webkit-mask-image and -moz-mask-image, have -beta-mask-image and -gamma-mask-image. When IE comes along and wants to play with WebKit's implementation, they implement -beta-mask-image and all the sites that use it get IE support for free.

[ Parent | on HN ]
Re:The birth of Microsoft's new web rendering engine by adrianpike on Thursday February 26, 2015 @05:25PM (#9115990)
They did.

-moz and -webkit and -ms and -o.

Unless we're actively working in synchrony, your "beta" won't be my "beta".

[ Parent | on HN ]