3 ms·
Although this is true, I've been bitten by issues where the browser 'supports' the feature, but it's still broken in comparison to other browsers, resulting in
by ezekg 10y ago
Although this is true, I've been bitten by issues where the browser 'supports' the feature, but it's still broken in comparison to other browsers, resulting in having to disable the feature for that given browser via browser detection. The most recent issue was `clip-path` in FF; it behaves _very_ weirdly compared to other browsers (Chrome, Safari).
- tedmiston 10y agoWere you using a vendor prefix by chance?
- ezekg 10y agoYeah, there is a -webkit prefix there as well for Chrome and Safari, which it works fine in.
- Manishearth 10y agoIIRC the main difference between FF clip-path and others is that FF clip-path's basic shape support is disabled by default. I recently added rounded corner support for inset clip paths, so FF (nightly) should have it too. Could you provide a specific example as to how it was broken?
- ezekg 10y agoI was trying to do something like, @supports (clip-path: inset(0 50px 0 50px)) { selector { clip-path: inset(0 5px 0 50px); } } where the clip path was animated. The @supports block would run, but the clip-path property would give an invalid property error. There was additional code within the @supports block related to displaying the animation. I ended up having to detect FF so that I could disable it, since it behaved differently than Chrome/Safari which use the webkit prefix.