3 ms·
oh god, vendors implementing each other vendor prefixes sounds insane. I dont think -draft1-border-radius is the same problem as -webkit-border-radius, I am pr
by daleharvey 15y ago
oh god, vendors implementing each other vendor prefixes sounds insane.
I dont think -draft1-border-radius is the same problem as -webkit-border-radius, I am pretty sure its how I would like these things to be developed, it allows the vendors to work together on the same specification, with opportunity for others to diverge, but web developers only need to know the particular draft, not each various browsers implementation.
I also think that by the time vendors are implementing other vendors prefixes, they should just be pushing to drop the prefix, that is the point
- Wilduck 15y ago> I also think that by the time vendors are implementing other vendors prefixes, they should just be pushing to drop the prefix, that is the point I think tantek advocates this approach, but in a different order. First make sure you can support the feature without a prefix, and then support both. tantek: One possible proposal is to only parse other vendors' prefixes in conjunction with parsing unprefixed. tantek: e.g. with -webkit-transform. We wouldn't parse that until we also parse transform
- Someone 15y agoI think the 'fun' starts when the vendor syntaxes and/or semantics are slightly different and/or have different bugs. For example, the syntax gradients in WebKit at one time were different from those in the HTML spec.