I was invited to the JS Party podcast to talk about all things Polypane, from the business side of things to nitty-gritty features that I’ve been working on. I had a lot of fun and I think Nick and Jerod did as well.
As someone building a browser I need to parse a lot of URLs. Partially to validate them, but also to normalize them or get specific parts out of the URL. The URL API in browsers lets you do that, but it’s ergonomics aren’t ideal.
Yesterday on Mastodon we had a short discussion about the (terribly named) overflow media feature. Because it has the same name as a CSS property it’s easy to think it has more power than it really does. Underlying that is the issue that your page can’t change the value of a media feature: media features say something about the medium: the device, browser or user preferences.
I've written before about the problems you can run into with CSS nesting (keep in mind that article uses an older syntax but the point still stands) and the question that @ChallengeCSS tweeted out today made me realize there's actually a few more gotcha's.
Most developers prefer to keep all their CSS custom properties in one place, and a pattern that has emerged in recent years is to put those on :root, a pseudo-class that targets the topmost element in your document (so that's always <html> on web pages). But just because they're in one place and in the topmost element, it doesn't mean they're global.
Hi, I'm Kilian. I make Polypane, the
browser for responsive web development and design. If you're reading this site, that's probably
interesting to you. Try it out!
Use the design system you already have
A cross-platform, simple and smart autosaving scratchpad.
Go on a text adventure in Facebook Messenger.
Browser extensions that automatically fix accessibility issues.
Drag-and-drop lossless compression of PNG and JPG images for web.
Demo your (bot) interactions on Messenger.