hmac-secret-mc extension from CTAP 2.2 to improve passkey credential handling in Chromium.Talks will be recorded and published on the official BlinkOn YouTube channel after the event concludes.
We always look forward to talking with fellow Chromium contributors, and we hope to see you there!
Updated 20 April 2026 to add a talk that was accepted at the last minute.
The new kernel version is out, this time with an increased major number. As usual, despite the perceived importance of the version number, this is just one release more. That means no spectacular announcements; just consistent work, more features, more fixes, better support.
A couple of non-technical changes stand out in this release: Rust is no longer considered experimental in the kernel, and there is now an official policy on tool-generated content. The kernel keeps evolving and this will surely pave the way for future development in the coming years.
For a detailed list of changes, you can check the KernelNewbies ChangeLog.
At Igalia, the Linux kernel is one of ever-present work areas and interests and we keep contributing to it on many fronts. Here’s our list of contributions and patches for this release.
Our work on the DRM (Direct Rendering Manager) continues. Being one of our biggest areas of contribution, in this release we once again provided improvements.
In the AMD display driver, we fixed unexpected color results reported by SteamOS/Gamescope users. These were related to incorrect mapping of color values made by the AMD color module when programming some color transformations into the hardware. We also improved the support for newer hardware families by exposing missing plane color blocks.
Further, we provided many assorted patches to do various cleanups in the TTM layer and multiple small (but important!) fixes in the AMD, Intel and v3d drivers, as well as a fix for the framebuffer probing on the Valve Steam Deck.
For the past couple of years, we’ve been consistently contributing to sched_ext and, in particular, to the scx_lavd scheduler to enhance the gaming experience in Linux, improving the latency and interactivity under gaming workloads.
In this release, we introduced a set of BPF helper APIs –bpf_in_nmi(), bpf_in_hardirq(), bpf_in_serving_softirq(), and bpf_in_task() – along with their corresponding self-tests. These helpers allow BPF programs to precisely detect their execution context. This capability is particularly valuable for sched_ext schedulers; for instance, a BPF scheduler like scx_lavd can now distinguish whether a task was woken up by another process or via an interrupt, enabling more informed scheduling decisions.
In our ongoing effort to improve Raspberry Pi devices, we addressed several issues related to the RPi 4 power domain, fixing system hangs during power transitions and correcting a broken reset status read. Additionally, on the RPi 3, we resolved a couple of memory leaks, race conditions, and PM reference imbalances, improving overall reliability for RPi users.
As usual, we helped with the never-ending task of fixing bugs, this time clearing up a few of them in the Bluetooth stack and the DRM TTM.
We determined the root cause of two race conditions in the thermal subsystem’s core that could potentially cause a system crash, and developed synthetic reproducers for it. Even though the approach selected to address the issue was not our proposed fix, we contributed to its code review and testing with our specific understanding of the issue and synthetic reproducers, improving the overall quality of the fix.
Another important and often overlooked type of contribution is the refactoring of code to make it more maintainable. In this case, by replacing deprecated APIs and legacy macros. We submitted some patches to do this kind of update in parts of the DRM subsystem and the v3d driver.
As with every release, we helped with assorted janitor tasks such as documentation fixes and cleanups — specifically improving the exportfs and DRM documentation — as well as the usual share of reviews and tests.
Changwoo Min and Gavin Guo will share lessons learned from evolving scx_lavd (Latency-Aware Virtual Deadline), a sched_ex scheduler, to support strict container isolation, complex server topologies, and energy-aware scheduling.
The talk will happen on the second day of the summit, on Wednesday, 15th April. We hope to see you there!
]]>Eurosky’s mission is to establish independent social media infrastructure operating in Europe, where Igalia is headquartered, and governed by European law. Our shared goal is to work together to develop core components and tools for the AT Protocol and its overall ecosystem. The fruits of this collaboration will be placed under an MIT License, ensuring that our work remains freely available for developers and organizations building on the open social web.
We at Igalia are excited to be a part of this effort and its vision of a more open, pluralistic, and resilient social web in which users, developers, and communities have genuine choice over the platforms and services they use.
Eurosky is a public interest, non-profit, technology organization working towards a thriving open social web for Europe. We build and maintain shared infrastructure on open protocols that enable European entrepreneurs, businesses, and organizations to launch social applications faster and more affordably. We build apps and solutions for people that prioritize interoperability, user control, and democratic values. All our technology solutions are hosted in Europe and governed by European law. Eurosky is an initiative of the Modal Foundation, a non-profit organization headquartered in the Netherlands.
Igalia is a leading open source consultancy with 25 years of experience, headquartered in Europe but operating with a global reach. As an organization deeply committed to the open source philosophy, Igalia has built its reputation on technical excellence and collaborative development, working with clients and partners across the world. Igalia is best known for the development of open web standards and browser engines, including Chromium, WebKit, and Gecko, where it stands out as the largest contributor to all major web engines second only to their primary developers. Beyond the browser, Igalia’s engineers are active contributors to a broad spectrum of technologies, including compilers, multimedia frameworks, graphics systems, and the Linux kernel, among others. Igalia is committed not just to any single technology, but to the health and advancement of the open source ecosystem as a whole.
]]>Several current and former Igalians contributed to Temporal. Ms2ger brought years of careful spec writing and vital review work; Philip Chimento and Ujjwal Sharma co-championed the proposal. Aditi Singh, Ben Allen, Cam Tenny, Dan Ehrenberg, Eric Meyer, Guillaume Emont, Ioanna Dimitriou, Jesse Alama, Romulo Cintra, Sarah Groff Hennigh-Palermo, and Tim Chevalier all contributed throughout the project’s life. Bloomberg, whose collaboration with us first got us working on it, funded the work and contributed engineering directly.
Besides its default ISO 8601 calendar, Temporal also supports a number of regional calendars — Gregorian, Japanese, Hebrew, Persian, Chinese, Islamic, and others. To ensure these work consistently across implementations, a companion ECMA-402 proposal was also needed. The Intl.era and Intl.monthCode proposal specifies the details Temporal deliberately leaves open: the valid era codes, eraYear semantics, and monthCode values for each of those calendars. We worked on this as part of our long-running collaboration with Google’s i18n team, with Ben Allen, Philip Chimento, and Ujjwal Sharma as the main contributors from our side.
Igalia also ended up working on RFC 9557, the Internet Extended Date/Time Format (IXDTF). Temporal needs a standard way to serialize timestamps with timezone and calendar information, but the conventions in wide use — like appending IANA timezone names to timestamps — had never been on a formal standards track. RFC 9557 fixes that, and also defines the new syntax for calendar annotations ([u-ca=hebrew] and similar) that Temporal requires for round-tripping dates across calendar systems.
Temporal adds immutable date/time types, explicit timezone handling, support for a variety of international calendars, and nanosecond precision. It ships with around 4,500 test262 tests — Date, for comparison, has 594. Firefox v139, Chrome v144, Edge v144, and TypeScript 6.0 beta already include it. If none of these are available, you may also use Temporal from a polyfill, including the reference polyfill developed by the champions initially.
Back when Temporal reached Stage 3 in 2021, we recorded an Igalia Chat on the proposal with Brian Kardell, Philip Chimento, Maggie Johnson-Pint (Moment.js), and Philipp Dunkel (Bloomberg). A lot has changed since then — and we just sat down together with Philip, Nicolò Ribaudo, and Bloomberg’s Jason Williams to talk about the Stage 4 advancement!
Congratulations to everyone who kept this moving. It took nine years and a lot of people, and hopefully will improve the lives of JavaScript developers. We’re looking forward to seeing more robust date handling deployed on the Web and beyond!
]]>Today we are announcing the launch of Moonforge, a new Linux distribution based on the Yocto and OpenEmbedded projects and designed to provide a fully open-source, production-ready foundation for building embedded and device operating systems.
Moonforge focuses on extensibility, flexibility, and long-term maintainability, enabling developers and system integrators to create custom operating system images while relying on well-established industry tooling and best practices.
The project is available as open-source on GitHub and welcomes community contributions.
Moonforge is an operating system framework for Linux devices that simplifies the process of building and maintaining custom operating systems.
It provides a curated collection of Yocto layers and configuration files that help developers generate immutable, maintainable, and easily updatable operating system images.
The goal is to offer the best possible developer experience for teams building embedded Linux products. Moonforge handles the complex aspects of operating system creation, such as system integration, security, updates, and infrastructure, so developers can focus on building and deploying their applications or devices.
Using Moonforge, developers can:
Moonforge is designed around three core principles: balance, separation, and best practices.
Creating a Linux distribution typically requires significant integration work: selecting components, configuring build systems, and aligning the system architecture. Moonforge reduces this duplicated effort by providing sensible defaults and core architectural decisions, while still allowing teams to customize and extend the system for their own products.
The project combines Yocto layers together with extensive use of kas, a tool for managing configuration in a declarative way using YAML. By assembling layers and configuration fragments, developers can easily create different operating system variants and product configurations tailored to their needs. This modular approach encourages reuse of common components while allowing teams to maintaine full control over the final system.
Moonforge is structured to maintain a clear separation between upstream and downstream components, making it easier for organizations to build derivative products. Existing Moonforge layers cover common use cases, while the Yocto layer architecture allows vendors and developers to add their own functionality when needed.
Kas configuration fragments are used to handle tasks such as:
This structure ensures predictable builds and simplifies release management for derivative systems.
Moonforge adopts established best practices for building Linux-based operating systems. It relies on proven tools and technologies like BitBake for image creation and kas for build configuration and reproducibility.
Modern development workflows are supported out-of-the-box by providing CI/CD pipelines to automatically build and publish:
Moonforge is also capable of integrating with different deployment and update mechanisms, like systemd, RAUC, or Mender.
The project is designed to support build environments across public cloud, private infrastructure, and local development systems, ensuring teams can adopt it within their existing workflows.
Moonforge is developed as an open-source project and aims to support a wide range of Linux devices and embedded products. Additional layers, features, and hardware platforms will continue to be added as the project evolves. Contributions from the community are encouraged.
Developers interested in building their own Linux operating systems or extending Moonforge can explore the project and contribute on GitHub.
]]>We always enjoy talking with people, so if you find yourself at one of the above events, please take a moment to say hi! And if you have any questions regarding any of our talks, are interested in having an Igalian bring a talk to an upcoming event, or you’d just like to learn more about Igalia, please feel free to reach out.
]]>CE participants receive financial compensation of €7,000 for 450 hours of work time over a period of either 3 or 6 months, on a schedule that works best for you. Each CE participant is mentored by one of Igalia’s outstanding open source contributors, and acquire knowledge and skills that will benefit them well beyond the program. The Coding Experience is remote-friendly, in keeping with Igalia’s fully-remote structure.
Applicants to the program can be students enrolled in an official education program, such as a college degree program, or can be students in alternative learning itineraries (e.g., self-learning). The CE program is also open to people who are in a later stage of their professional career, do not have experience working in tech fields, and are willing to refocus.
Igalia welcomes all applicants regardless of their age, disability, gender, race, marital status, religion, sexual orientation, or any other marginalized identity. Due to our strong commitment to diversity and inclusion, we would like to expressly invite individuals from underrepresented communities in our industry to apply.
The application period is open through April 3rd, 2026, with applicants being informed of their acceptance status by mid-May. If you’re interested in learning more about the Coding Experience program or you are ready to apply, please visit the Igalia Coding Experience page.
]]>The Interop 2025 results were outstanding, with the overall interoperability score of its focus areas climbing from 28 to 95 in the course of the year; this has further moved up to a score of 97 in the month since the end of 2025. We’re excited about the prospect of similar improvements in this year’s focus areas!
At the markup layer, there wasn’t one proposal that stood out, but rather a collection of a few proposals related to dialogs and popovers — not just the <dialog> element and the popover attribute, but also the :open pseudo-class in CSS. There were some things still missing in implementations, and others that weren’t handled consistently. The Interop team combined the proposals into a single HTML focus area.
As is often the case, the presentation layer got a lot of attention from proposers, which led to eleven focus areas rooted in CSS. These are:
At the scripting layer, the Interop team chose these seven focus areas:
While all of Interop can be considered a web compat effort, there are always a few areas where the amount of work to achieve full alignment is small, but worth taking on as official focus areas. Sometimes, this can mean getting clarification from relevant W3C working groups, or doing origin trials to make sure the change is sufficiently low-impact. This year, work will focus on web compatibility issues with:
Each year, the Interop team chooses a small number of areas to investigate how to get the proposals into future Interop years. This is usually done for proposals that lack the tests, or the testing infrastructure, to qualify as official focus areas. The 2026 investigations will be:
If you’d like to read more about Interop 2026, see the articles published today by Apple, Google, Microsoft, and Mozilla.
Igalia is proud to once again be part of the Interop process, and to champion a few proposals that are particularly close to our interests. We look forward to seeing all the progress this year will bring.
]]>Following the TAG’s recent election results, the W3C Team has chosen and the Advisory Board and Technical Architecture Group have ratified our very own Brian Kardell for the 2026-28 term as one of the two appointments they will make for this term.
Brian, who started hacking on the web as early as 1996, has well over a decade of experience working in web standards and core technologies, contributing to its continued development, whether it be through championing for important yet underappreciated features or through advocating for the platform at large.
All in all, we believe Brian will be an excellent addition to the group and a champion for a free and extensible web. Congratulations to Brian as well as the W3C TAG on this appointment!
]]>