Adrián Pérez @aperezdc@mastodon.social

#TIL about CGA composite video, which is cool, very cool, for those times: https://m.youtube.com/watch?v=niKblgZupOc

Next up: updating the #Buildroot packages for both WebKit ports (GTK, WPE); currently running a smoke testing build. Which makes it the fourth complete rebuild of the day. No need to pay for heating, having a build machine crunching builds of gargantuan projects in the room 🔥 💻

Here it is #WPEWebKit 2.30.3 → https://wpewebkit.org/release/wpewebkit-2.30.3.html 🎉

The most visible improvements in this release are the fixes for the CSS backdrop filters and for scrolling <iframe> elements.

Prepping a new #WPEWebKit release, this will be 2.30.3 and include a few neat fixes.

I have used^W suffered #GitLab for years now and I can't still understand why the diff viewer randomly hides changes for some files without any apparent logic. It's bewildering.

One more multi monitor GNOME Shell problem: switcher popups shown when switching applications and virtual desktops are always shown in the so-called “primary” monitor. That sounds sensible, but if I am paying attention to windows in a “secondary” one and press e.g. Alt-Tab to bring up the window switcher I *want* to see it in front of my eyes in that secondary monitor, not in the primary one.

More multi monitor woes: GNOME Shell opens new windows in a seemingly random monitor. On a closer inspection, it always uses the one where the mouse cursor is. Which tends to NOT be the one I am looking at, because I use the keyboard to focus windows 90% of the time. If there has been only keyboard events and a new window shows up, it should go to the monitor containing the window that was receiving the key events.

It's 2020 and Firefox still has trouble choosing which monitor to use for context menus. Even on X11. I guess this is not the year of Linux in the desktop either 🤔