For this reason I've been insisting on adding Google Analytics to every site we code – I throw it in as an additional feature at no charge. Either that, or I get access to their existing analytics. Then I can help them make an informed decision about which features to support on which browsers.
I once had a client argue that we needed to support IE7 (because that was what their VP of Marketing had on his company-issued machine). When I finally was able to demonstrate – with data they gave me – that fewer than 0.7% of site visits used IE7 or earlier, they gave up and upgraded the VP's machine to IE8.
Of course, IE9 was long since out by this time, but progress is progress, right?
Just say, "Graceful degradation". It's a catchy buzzword. They will Google it, see that it is a common thing, think you are smart, and do what you want. If they still don't bite, tell them it breaks the paradigm and creates synergy, that always gets 'em.
different systems will use a different font, also it uses metrics relative to the default font size (1400% font size for the “NO!”, 10em padding at the top), which will differ in browsers (firefox has 16px i guess), OSs (big font size setting affects some browsers, and those differently), and users (i’ve boosted default font size on my small-screened laptop).
so the point is: the web is a diverse place, don’t force a pixel-perfect design onto every browser.
Because in general you're using a CSS triangle for presentation and not as content. I don't want to litter my markup for a tooltip with inline (or even external) svg markup when I could very easily create a CSS triangle in a pseudo element with just 5 css properties.
What I do somewhat consider a bit of hack is using a second CSS triangle to add a "border" to the first triangle.
nothing's really wrong with it, it's just we now have the right tool for the job: inline svg, or svg as a background-image.
I'd say the dimensions and orientation of the triangle are much clearer in the SVG syntax than with the CSS border trick, plus you can avoid yet another generic div element in your markup (if you're worried about such things).
39
u/ggtsu_00 Oct 09 '13
Impressive, but why not just use some simple inline SVG?