CSS
-
Or, “Always examine your linter defaults” I got a code review flag for using url() in an @import statement — apparently that’s not “modern.” But, my linter, stylelint, didn’t flag this in my linting phase. To be clear, both forms are completely valid in CSS; the spec doesn’t care. I went looking for a tiebreaker…
-
I needed a tool which could quickly and automatically tell me when my website, balkanheritage.info violates web accessibility standards. I chose pa11y, which is a command-line accessibility testing tool that runs automated checks against a URL using the well-known tool axe-core. But one problem surfaced rather quickly, which was that pa11y wasn’t actually using WCAG…
-
While I was reviewing Opera Next’s changelog (11.50b1), I noticed this tidbit: Start request for CSS resources now occurs during parsing. What this means is that as soon as Opera encounters a <link> tag referencing an external stylesheet, it will issue an HTTP GET for that stylesheet. Most browsers parse the entire HTML source before…
Mashq and Machine 