One cannot simply add a gradient as a fill to an SVG <symbol> (or anything inside it) — which would be a part of a sprite. It won't be working in Chrome! Never expected that. Love u FF.
Meh.
https://t.co/LAuI752CAf
@pepelsbey_ Thank you Vadim 🙂 All the defs though are exactly one level up. This morning I found out that it’s working fine if I put hidden SVG code right into the markup. But if it’s a separate file, then probably there’s a problem with accessing “outer” defs.
Completely different case is when you get a task from someone else. You simply have to solve it, whatever it takes. That is what perfects your skill slamming you with a straight-out real life.
A tricky thing about our mind: when you learn a new feature on your own and make up tasks to yourself, your brain may unnoticeably look for (and find) ways around really hard ones forcing you to think, "Ah, let's try it otherwise, I figured out something nicer". Don't trust it.
#svg experts, please, any idea why some icons after being packed into a sprite (using svgstore) get some unwanted black fill? See the picture attached.
@pepelsbey_ The thing is, I even tried to paste a broken SVG manually into the sprite code, but it didn’t do the trick. Will try to build a whole sprite this way. Thank you for the guess!
How nice is that to copy something to a clipboard without warning? You click some element — and all of a sudden it pops in your SYSTEM clipboard removing anything being kept there previously. Encountered this hundreds times on the web but only now I understand how creepy this is.
Tossing between paranoid and esoteric feelings. 2 weeks ago it dawned upon me: what I really wanna learn deeply now is animation. And BAM 💥 I got an Instagram ad from beloved @htmlacademy_en: a new animation course is about to start. It's today! I could barely sleep, can't wait!
📢 If you use system fonts, you might want to temporarily remove BlinkMacSystemFont from your font stack. Chrome currently ignores font-weight declarations on text rendered in the San Francisco system font.
🐞 The bug to follow: https://t.co/Opva7CT4Dv
https://t.co/4fnWKHyFKX
Doing nothing is also an option. The sign in/up flow has to be as smooth and pleasant as it can be. So we definitely must help users where we can. But sometimes it's too much, and processing possible typos feels like we sort of overdo it. Not sure. So best practices are welcome!
Is there another best practice, regarding email verification to prevent users from misprints like "gnail"? To me, it's not an option to consider such cases invalid and prohibit customers to enter such emails — who knows, it's a website domain after all, why can't it be "gnail"?
For now I see the only solution (apart from doing nothing) — to warn a user they might have made a typo and show an unobtrusive message "Are you sure you meant gnail?" which would not require any action like extra click to dismiss it and proceed.
Appears to be that such a little thing as mailto:/tel: links in HTML are misleading — or not working at all — in many many cases. Gotta not only beware of using them but figure out a better way to deal with ones not confusing users. If you have any best practice, please share😉
Got doubts regarding transfonter or fontsquirrel ability to convert a variable TTF to in-the-same-way-variable WOFF, and was right. It's the first time I had a chance to work with one, and it appears to be I should use CLI instead of web tools.
pyftsubset is what does the trick!