BlinkGTK 1.2.3-build1 Release Notes

Release date: 2026-09-24 / Chromium: 154.0.8037.57 / Language: 日本語 | English

The rendering engine is updated to Chromium 154.

What you can do with build1

Turning JavaScript, images and localStorage off now takes effect

Settings such as blink_web_view_set_javascript_enabled() are now applied to the page.
Up to 1.2.2 the value was only stored: page scripts still ran after passing FALSE.

If your application must keep scripts from running on some pages, update to this release.
set_default_encoding() will be investigated and handled in a later release.

Custom schemes accept the usual web-development forms

• A handler can return out_mime with parameters, such as "text/html; charset=utf-8",
  and the page is shown as HTML. Up to 1.2.2 it was shown as <pre> text.
  The charset you give is used as is
• Pages can call fetch() on schemes listed in BLINKGTK_EXTRA_SCHEMES. Up to 1.2.2 only
  the five built-in schemes (app / blinkgtk / res / resource / ebook) allowed it

Packaged builds start without naming the resource directory

Without blink_gtk_set_resources_path(), BlinkGTK now also looks for icudtl.dat and the
other resources next to libblinkgtk. Up to 1.2.2 it only looked next to the executable, so
applications built against the rpm / deb packages stopped with an ICU error.
The search order is:

1. The executable's directory
2. <libdir>/blinkgtk-0.1/chromium/ (rpm / deb)
3. <libdir>/chromium/ (tarball)
4. <libdir>/

Applications that set the path keep working as before.

The input method follows GTK's choice

BlinkGTK no longer picks the Japanese input path itself; it leaves the choice to GTK.
On Wayland this is GTK4's default text-input path, which is also what the input method
side (IBus) recommends. On real Fedora 45 / GNOME hardware we confirmed, with this path
selected, that conversion mode works and that closing views repeatedly produces no input
method warnings (measured by selecting the same path through the switch added in 1.2.2).

To get the 1.2.2 behaviour (naming IBus), set BLINKGTK_IM_MODULE=ibus. It affects
BlinkGTK's views only. blink_gtk_get_im_module() returns the value currently applied
(an empty string by default, meaning GTK decides).

Put your own markers on the part you want to measure

blink_gtk_trace_mark("name") puts a marker in the trace. The event is named after the
marker, the same shape as the web's performance.mark().

// Start with: --trace-startup=toplevel,blink.user_timing
blink_gtk_trace_mark("workload_ready");
/* ... the part to measure ... */
blink_gtk_trace_mark("idle_static_ready");

Without the blink.user_timing category the call does nothing.

Features enabled by default in Chromium 154

• CSS text-decoration-inset — pull underlines, overlines and line-throughs in from
  the text edges, or extend them outward. In vertical writing the underline is the side line
• Responsively-sized <iframe> — the embedding page can size an iframe to its content
  (only when requested)
• font-width descriptor in @font-face — an alias of font-stretch

The feature list is Chromium 154's list on chromestatus.com. What we measured ourselves
covers rendering, input and startup, not these typography features.

What build1 fixes

• The workaround added in 1.2.1 (a vertical line breaking half-way when a closing bracket
  falls at the line end) is removed. Chromium 153 fixed the same symptom upstream; we
  kept the workaround in 1.2.2 after measuring that it no longer changed the result

• The header comment of the load-failed signal did not match the implementation. The
  correct handler signature is (the signal itself is unchanged):

  static void on_load_failed (BlinkWebView *web_view, BlinkLoadError error_code,
                              const char *failing_uri, gpointer user_data);

• The header said blink_gtk_init_with_sandbox() was not in the shared library yet, but it
  has been since 1.2.2-build4. On Linux, passing NULL behaves exactly like blink_gtk_init()

What does not change

• No public API is removed. Applications built for the previous release keep working
• The default rendering path (software / EGL) and how to switch it are the same

What behaves differently

• The input method default (above). BLINKGTK_IM_MODULE=ibus restores the old behaviour
• Four settings that had no effect up to 1.2.2 now take effect. Applications that passed
  FALSE will see page scripts or images stop

What we verified

• EGL path: passes the check that judges white screens, shrunken rendering and abnormal
  exit from the logs
• Settings: on the shipped build, set_javascript_enabled(FALSE) stops page scripts
  (the same check fails on 1.2.2). Images, localStorage and the default font size were also
  checked on the shipped build; the default encoding was confirmed not to take effect
• Custom schemes and resource detection: MIME parameters, fetch() and starting without
  a resource path were checked on the shipped build (all three fail on 1.2.2)
• Input method: on real Fedora 45 / GNOME hardware, 40 view closures on each of the two
  paths (measured by selecting the path with the 1.2.2 switch; that 1.2.3's default selects
  that path is confirmed from the startup log)
• Markers: in one trace, markers from both blink_gtk_trace_mark() and
  performance.mark() appear as events named after the marker