Version: 1.2.5-build5 / Language: English | 日本語
Which BlinkGTK release is built on which Chromium. To find out when a
feature became
available, first check which Chromium version introduced it in
Chromium 147 → 151, then
look up the corresponding
BlinkGTK release here.
| BlinkGTK | Released | Chromium | What happened in this release |
|---|---|---|---|
| v1.2.5-build5 ← current | 2026-11-01 | 156.0.8078.79 | Fixed a crash of the application when a page calls the file picker APIs (build2 to build4). File System Access now stops sensitive locations (the four FileSystem CVE fixes take effect from this build). Removed one startup improvement (startup is about 0.3 s slower) |
| v1.2.5-build4 | 2026-11-01 | 156.0.8078.79 | Incorporated the 21 security fixes in Chromium 156.0.8078.79 (the four FileSystem fixes take effect in BlinkGTK from build5) |
| v1.2.5-build3 | 2026-10-29 | 156.0.8078.73 | Incorporated the security fixes in Chromium 156.0.8078.73 |
| v1.2.5-build2 | 2026-10-27 | 156.0.8078.47 | The page color scheme (light / dark) now follows the GTK theme, including switches while the app runs. Startup is faster (no wait for the child-process helper, fewer symbol lookups, no probe of unused GPU devices, and only the Vulkan drivers for the GPUs present are loaded). |
| v1.2.5-build1 | 2026-10-22 | 156.0.8078.47 | The rendering engine is updated to Chromium 156. BlinkGTK can now be used from Python (PyGObject); the launcher blinkgtk-run is included. set_user_agent() now applies to pages opened with load_uri(), the zoom level is treated as a factor (1.0 = 100%), and is-loading returns to False when loading finishes. |
| v1.2.4-build4 | 2026-10-14 | 155.0.8059.39 | Fixed a crash when clicking the page after a navigation, and the app no longer stops responding when navigating with accessibility enabled. The DEB file names in the bundled INSTALL and README are corrected. |
| v1.2.4-build3 | 2026-10-14 | 155.0.8059.39 | Inline cutting notes (warichu) that fit on one line can now be set (-blinkgtk-warichu). Static-page captures that timed out but left a file (software async capture), and render path switches that always rolled back on white pages, are fixed; the built-in AI APIs now report that they are unavailable. |
| v1.2.4-build2 | 2026-10-11 | 155.0.8059.39 | The update notice (BLINKGTK_UPDATE_CHECK=1, off by default) always failed because the release list was larger than the receive limit; this is fixed. Without the notice enabled, behavior is the same as build1. |
| v1.2.4-build1 | 2026-10-07 | 155.0.8059.39 | Chromium 155. RPMs are for Fedora 45 or later only (Fedora 44 up to v1.2.3). On scale-1 displays software rendering is received through a path without capture (no capture requests or readback), and static pages are no longer redrawn continuously. Fixes EGL memory growth and accessibility with at-spi2-core 2.61. Includes upstream Japanese typesetting changes such as the fix for lines after ruby shifting up |
| v1.2.3-build4 | 2026-09-28 | 154.0.8037.57 | Software rendering no longer copies every frame, so animations run about 24% more often at scale 2. Also fixes load_html not applying base_uri, a first paint delayed by about 25 seconds when the accessibility bus does not respond, stored permissions being read on the UI thread, and GTK warnings with ibus when a view is closed |
| v1.2.3-build3 | 2026-09-26 | 154.0.8037.57 | Opening audio of 5 MB or more served over a custom scheme (such as ebook://) with |
| v1.2.3-build2 | 2026-09-25 | 154.0.8037.57 | Pages can now be written to PDF files. Saving downloads, deciding where links and new windows open, the camera and microphone, answering HTTP authentication, remembering permission decisions, and choosing default fonts and a minimum font size are added too. swiftshader mode showing nothing on screen is fixed |
| v1.2.3-build1 | 2026-09-24 | 154.0.8037.57 | The rendering engine is updated to Chromium 154. Turning off JavaScript, images and localStorage, and the default font size, now take effect on the page (up to 1.2.2 the value was only stored), and the input method follows GTK's choice. Fedora 45 RPMs are also provided |
| v1.2.2-build6 | 2026-09-19 | 153.0.8010.36 | Views can now have their own profile and cache (blink_web_view_new_with_profile), so opening the same page in several views no longer serves all but the first from a shared cache |
| v1.2.2-build5 | 2026-09-14 | 153.0.8010.36 | The rendering path can now be chosen from the API. Call blink_gtk_set_gpu_mode() before blink_gtk_init() and the engine starts on that path. Until now, asking for EGL through blink_web_view_new_with_gpu_mode() did not change the path. The rendering path is settled during engine initialisation, together with the startup flags handed to the GPU process, so it can no longer be changed by the time a WebView is created. The startup log named EGL in both cases, so there was no way to tell from outside whether the request had taken effect. Without also setting BLINKGTK_GPU_MODE, applications asking for EGL were running on the CPU pixel path. blink_web_view_get_gpu_mode() now reports the path actually in use after initialisation, and the startup log names it as well. |
| v1.2.2-build4 | 2026-09-13 | 153.0.8010.36 | Fixed a problem where the EGL mode stayed blank from start to finish on systems using a Virtio GPU (virtual machines and the like). The engine reads the image from the CPU side to decide whether a frame is empty, but on this kind of GPU the drawing happens outside the machine, so that read sees nothing. Frames that did have content were judged empty and withheld from display. Pages without animation were the most affected, staying blank for as long as they were open. Assistive technology started after the application now reaches the content as well; previously a screen reader had to be running before launch. |
| v1.2.2-build3 | 2026-09-11 | 153.0.8010.36 | Closing the window while a navigation was still in flight no longer crashes. While the page container was being torn down, a notification was delivered to a handler that was already looking at something released. Opening a book and closing it right away triggered it. This build also adds a diagnostic that asks the compositor whether a frame reached the screen (printed only with BLINKGTK_GX_LOG=1; nothing changes by default), which distinguishes "the content was empty" from "the content was there but never displayed". A record that said "not displaying" for frames past the eighth while in fact displaying them has been corrected |
| v1.2.2-build1 | 2026-09-10 | 153.0.8010.36 | The rendering engine is updated to Chromium 153. In vertical writing, a line no longer breaks half-way when a closing bracket falls at the line end (a line with room for 35 characters held only 17, and text-align: justify then doubled the inter-character advance). Of 13 configurations, 8 exhibited it and all are now fixed. It does not occur in horizontal writing. We reported this upstream (crbug 542686223) and Chromium fixed it; our own workaround (17 to 34 characters) is still included in this release, but with the upstream fix in place it does not change the result in the range we measured |
| v1.2.1-build3 | 2026-09-08 | 152.0.7977.64 | The build number is now available at run time when reporting a problem (blink_gtk_get_version_full / blink_gtk_get_build; behaviour can differ between builds of one version, and until now only the package file name identified a build). The frame-delivery log records the operation actually performed and the Wayland buffer id, and the measurement caps can be raised. Live render-path switching now covers the EGL path (when started under EGL) |
| v1.2.1-build2 | 2026-08-30 | 152.0.7977.64 | Where the GPU path is unavailable, BlinkGTK now falls back to software rendering and keeps drawing. It switches when no frame arrives within five seconds and writes the reason to standard error, and it does not switch where the GPU path works. Captured screenshots no longer come out with red and blue exchanged |
| v1.2.1-build1 | 2026-08-27 | 152.0.7977.64 | The rendering engine is updated to Chromium 152. Vertical lines no longer break half-way (a line with room for 34 characters held only 17 when a closing bracket fell at the line end), and columns in multi-column layout now fill to capacity. The line grid is also preserved when direction: rtl is combined with vertical writing |
| v1.2.0-build9 | 2026-08-16 | 151.0.7922.108 | Render paths can now be switched live without restarting (BlinkShift public API — a switch takes a few hundred milliseconds and rolls back automatically on failure). Added blink_gtk_application_run() for correct GtkApplication integration and a presentation-policy API to declare when a view need not be presented. Fixed large user scripts never reaching the renderer |
| v1.2.0-build8 | 2026-08-12 | 151.0.7922.108 | Applied the results of a security review. Per-site process isolation is now on by default (which can increase memory use), sandbox detection is measured rather than inferred, and an API to query the sandbox state was added. A reference page for environment variables is now published |
| v1.2.0-build7 | 2026-08-12 | 151.0.7922.108 | Corrected the version macros in the header shipped with the development package; build1-6 claimed the previous release (1.1.0 / Chromium 150). The runtime API was always correct, so only compile-time macros were affected. The runtime itself is identical to build6 |
| v1.2.0-build6 | 2026-08-11 | 151.0.7922.108 | Updated to Chromium 151.0.7922.108; user scripts now run before the page's own scripts, and JavaScript results are returned as JSON |
| v1.2.0-build5 | 2026-08-10 | 151.0.7922.71 | Western hyphenation (hyphens: auto) now works; abnormal exit on shutdown and stray diagnostic PNGs fixed |
| v1.2.0-build4 | 2026-08-08 | 151.0.7922.71 | Install and update with dnf; continuously animating pages no longer freeze |
| v1.2.0-build3 | 2026-08-08 | 151.0.7922.71 | GPU rendering works with a single environment variable, and text no longer appears doubled while resizing (withdrawn) |
| v1.2.0-build2 | 2026-08-03 | 151.0.7922.71 | The engine now reports its real version, and vertical layout metrics are readable from JavaScript |
| v1.2.0-build1 | 2026-08-01 | 151.0.7922.71 | Emphasis marks no longer grow the line pitch, and ruby overhang behaves as specified (moved to Chromium 151) |
| v1.1.0-build6 | 2026-07-29 | 150.0.7871.46 | Bundled documentation corrected throughout, with machine checks that documentation matches the implementation |
| v1.1.0-build5 | 2026-07-29 | 150.0.7871.46 | Bundled samples consolidated into one. Superseded by build6 (withdrawn) |
| v1.1.0-build4 | 2026-07-29 | 150.0.7871.46 | UA / cookie / permission APIs added. Superseded by build5 (withdrawn) |
| v1.1.0-build3 | 2026-07-23 | 150.0.7871.46 | RPM dependency names corrected to Fedora's naming (reported by a user) |
| v1.1.0-build2 | 2026-07-21 | 150.0.7871.46 | Idle CPU usage brought to zero; blank-page issue on font-size change resolved |
| v1.1.0-build1 | 2026-07-07 | 150.0.7871.46 | Distribution reshaped (runtime / development / GObject Introspection split). Vertical multi-column fragmentation, wheel scrolling, input after navigation |
| v1.0.11-dev | 2026-06 | 148.0.7778.167 | Moved to Chromium 148 (also tracking 149). Linking requirements for embedding applications settled |
| v1.0.10-build16 | 2026-05-16 | 147.0.7727.55 | Rendering regressions removed; quality confirmed on real hardware |
| v1.0.10 | 2026-04-21 | 147.0.7727.55 | Stabilisation |
| v1.0.9 | 2026-04-18 | 147.0.7727.55 | Consumer-facing polish; reported defects resolved in one pass |
| v1.0.8 | 2026-04-14 | 147.0.7727.55 | Language bindings unified, API strengthened |
| v1.0.7 | 2026-04-13 | 147.0.7727.55 | Input method (IME) fixes |
| v1.0.6 | 2026-04-12 | 147.0.7727.55 | Moved to Chromium 147 |
| v1.0.5 | 2026-04-10 | 146.0.7680.177 | Tracked the Chromium 146 update |
| v1.0.3 | 2026-04-07 | 146.0.7680.71 | Improved font rendering on HiDPI |
| v1.0.2 | 2026-04-07 | 146.0.7680.71 | Per-WebView GPU mode API |
| v1.0.1 | 2026-04-03 | 146.0.7680.71 | Bug fixes (no packages published) |
| v1.0.0 | 2026-04-03 | 146.0.7680.71 | First stable release |
| v1.0.0-rc1 | 2026-03-18 | 145 (estimated) | Release candidate |
Two notes. v1.0.4 was skipped (v1.0.3 is followed by
v1.0.5). And v1.1.0-build4 and
build5 have been withdrawn, superseded by build6. Withdrawn
releases are not deleted from
this history: being able to trace which release you were running matters
more.
| Chromium | BlinkGTK | Period |
|---|---|---|
| 145 | v1.0.0-rc1 | 2026-03 |
| 146 | v1.0.0 – v1.0.5 | 2026-04-03 – 04-10 |
| 147 | v1.0.6 – v1.0.10-build16 | 2026-04-12 – 05-16 |
| 148 / 149 | v1.0.11-dev | 2026-06 |
| 150 | v1.1.0-build1 – build6 | 2026-07-07 – 07-29 |
| 151 | migration in progress | 2026-08 – |
v1.1.0-build6 has two parts.
1.1.0 — the product version. It rises
on feature additions or incompatible changesbuild6 — how many times that product
version has been rebuilt. It rises on defectThe same 1.1.0 with a different build number is
different code. When reporting a defect,
please include the build number.
Separately, the 0.1 that appears in
package names and paths
(libblinkgtk-0.1.so.0,
/usr/share/doc/blinkgtk-0.1/) is the API version and
is
independent of the product version — the same convention as GTK4's
gtk-4.0 and
WebKitGTK's webkitgtk-6.0. It changes only on incompatible
API revisions.