{"id":275322,"date":"2018-08-24T07:02:22","date_gmt":"2018-08-24T14:02:22","guid":{"rendered":"http:\/\/css-tricks.com\/?p=275322"},"modified":"2018-08-24T07:02:22","modified_gmt":"2018-08-24T14:02:22","slug":"using-css-clip-path-to-create-interactive-effects-part-ii","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/using-css-clip-path-to-create-interactive-effects-part-ii\/","title":{"rendered":"Using CSS Clip Path to Create Interactive Effects, Part II"},"content":{"rendered":"
This is a follow up to my previous post<\/a> looking into clip paths. Last time around, we dug into the fundamentals of clipping and how to get started. We looked at some ideas to exemplify what we can do with clipping. We\u2019re going to take things a step further in this post and look at different examples, discuss alternative techniques, and consider how to approach our work to be cross-browser compatible.<\/p>\n <\/p>\n One of the biggest drawbacks of CSS clipping, at the time of writing, is browser support. Not having 100% browser coverage means different experiences for viewers in different browsers. We, as developers, can\u2019t control what browsers support \u2014 browser vendors are the ones who implement the spec and different vendors will have different agendas.<\/p>\n One thing we can do to overcome inconsistencies is use alternative technologies. The feature set of CSS and SVG sometimes overlap. What works in one may work in the other and vice versa. As it happens, the concept of clipping exists in both CSS and SVG<\/a>. The SVG clipping syntax is quite different, but it works the same. The good thing about SVG clipping compared to CSS is its maturity level. Support is good all the way back to old IE browsers. Most bugs are fixed by now (or at least one hope they are).<\/p>\n This is what the SVG clipping support looks like:<\/p>\n This browser support data is from Caniuse<\/a>, which has more detail. A number indicates that browser supports the feature at that version and up.<\/p><\/div>Desktop<\/h4>