← Feed

Posts

• Post #2106332

  I just released Polypane 28.0.1 with some bug fixes and nice quality-of-life improvements! Full changelog: https://polypane.app/blog/polypane-28-project-improvements-elements-panel-updates-and-chromium-146/#polypane-2801-changelog

• Post #1590303

  I joined the Podrocket podcast recently to chat about the INTL library and what motivated me to do a conference talk about a single browser API. Check it out here: https://podrocket.logrocket.com/the-browser-apis-youre-shipping-libraries-to-replace-with-kilian-valkhof

• Post #1590301

  I sometimes get asked to implement a screen reader emulator into Polypane.app and while that sounds cool, it would cause people to focus on and test the wrong things. Thanks to @yatil I now have a good resource to point to when they ask why: https://yatil.net/blog/screen-readers-are-not-testing-tools

• Post #1590300

  Brb, on my way to Budapest for Webkonf.hu!

• Post #1100759

  I make good use of the Intl API in Polypane and on its website, so it was high time I did a Polypane-style deep-dive on it. Check out our new article, play around with the interactive examples or hear me yap about it on video. Whatever works for you! https://polypane.app/blog/the-intl-api-the-best-browser-api-youre-not-using/

• Post #876244

  I just released Polypane 28.0.2 with many bugfixes, big performance improvements throughout the app, 25% smaller installer size, new warnings in the outline and meta panels and a fix for macOS autoupdate. 🥳 Except the fix for macOS autoupdate didn't work. 😬 so I also released 28.0.3 to fix that 😎 Wasn't stressful at all. nope.

• Post #876243

  Due to the new NPM publishing rules I've been modernising the electron-to-chromium publishing logic. I still use DigitalOcean infra (Thx for sponsoring!) for building new versions, and GH actions to publish. It doesn't quite work yet 🥴 because like everything NPM it's woefully uderdocumented, but I'll get it eventually. https://github.com/Kilian/electron-to-chromium/

• Post #876242

  RE: https://mastodon.social/@tylergaw/116289921834353921 People have been writing about this, making really strong cases for it, for 4+ years now (including yours truly, like https://kilianvalkhof.com/2024/css-html/your-page-cant-change-media-features/ and https://kilianvalkhof.com/2022/css-html/on-better-browsers-arbitrary-media-queries-and-browser-uis/ ) So naturally the major innovation in browsers recently has been to *checks notes* rewrite tab titles with AI

• Post #811174

  Did you know I wrote a deep dive on offset parents and stacking context? Two essential concepts when it comes to positioning in all three dimensions. They're hard to debug, but not with Polypane! Contexts are just listed in our elements panel, easy peasy. Read here: https://polypane.app/blog/offset-parent-and-stacking-context-positioning-elements-in-all-three-dimensions/