Retweeted
Today I learnt: “The <noscript> element is just not an appropriate way to cover the something-went-wrong-with-JavaScript problem. Progressive enhancement—that is, feature detection—is the only way to do that.” – @adambsilver
Today I learnt: “The <noscript> element is just not an appropriate way to cover the something-went-wrong-with-JavaScript problem. Progressive enhancement—that is, feature detection—is the only way to do that.” – @adambsilver
@morgaaaan
Frontend developer (HTML/CSS/JS) / Learning a11y + inclusive design / Vimmer / GTDer / Music addict / Amateur photographer