Anthony Ricaud
https:/
relying on solutions provided natively by browsers enables you to benefit at low cost from the expertise of the community creating web standards. These solutions generally have the advantage of using less code, thus reducing maintenance efforts for a development team (for example, no need to update the libraries used).
67 Weird Debugging Tricks Your Browser Doesn't Want You to Know
A list of useful, not-obvious hacks to get the most out of your browser’s1 debugger. Assumes an intermediate-level-or-higher understanding of the…
Educational Sensational Inspirational Foundational
A historical record of foundational web development blog posts. I've already read most of these great articles, and will of course read the few missing.…
3 Methods for Scoped Styles in Web Components That Work Everywhere
WebC allows folks to broaden access to things built with web components without the drawbacks of other methods I really have to try WebC more seriously,…
While we wait for browsers to implement the text-wrap: balance; #CSS property and value for text (pleeeeeease! 🙏), I may have created a silly — and probably sub-optimal — function to do it with HTML block elements:
https://codepen.io/nhoizey/pen/mdjbrVx
Tell me what you think!
But why? Just because a colleague needed it, we could not find a solution in pure CSS, and I like challenges… 😅
Many of the latest additions to HTML, CSS, and JavaScript first existed as JavaScript libraries or frameworks or pre-processors or polyfills and then…
Alan Norbauer
Zach Leatherman
Matthias Ott