For the past 6 or so years I’ve been maintaining the electron-to-chromium package and I realise I never wrote a blog post about it. Electron-to-chromium is an NPM package that maps Electron versions to Chromium versions so you can input e.g. Electron 32 and get back Chrome 128.
I’ve been a fan of Tejas’ podcast since he started it. He is an extremely gracious host that asks interesting questions and brings out the best in the people he has on. I was thrilled when he asked me to record an episode with him.
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.
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.