Simon Hausmann

> I noticed quite a large memory leak in an app I'm toying around with https://github.com/blquinn/trixie > > If you enable the femtovg backend, then try resizing the window a...

This is fixed in the master branch as of 0ce0fd80dde5656ae63690d2085f1dcc24054261 AFAICS. We don't use FemtoVG's shaper anymore, which had this word cache. The test in #9280 is also very useful...

I see two options: 1. We take an API like this, with a slightly more elaborate name, but keep it simple as a boolean property. The documentation needs to explain...

Sounds good, I'm fine with (1) and it can be incrementally improved :-). Naming wise I'd go for `set_window_background_blurred(bool)` and `is_window_background_blurred()`. What do the others think?

Oh, I didn't know about [window_vibrancy](https://docs.rs/window-vibrancy/0.5.0/window_vibrancy/) from the lovely Tauri folks. That's pretty cool! I'd still prefer to just have a boolean for a blur effect, instead of the whole...

> > Oh, I didn't know about [window_vibrancy](https://docs.rs/window-vibrancy/0.5.0/window_vibrancy/) from the lovely Tauri folks. That's pretty cool! > > I'd still prefer to just have a boolean for a blur effect,...

Meanwhile, it's now possible to use window_vibrancy with Slint via raw-window-handle: https://github.com/slint-ui/slint/pull/4918

We can reproduce this. The issue doesn't happen with Skia (that would be the recommendation), but it's visible with FemtoVG and according to your clip also with Qt.

Mysterious how it worked with gtk, but I’m relatively certain that it’s not skia related but more likely to the OpenGL context state. Does it help if you ensure your...

Can confirm. Foolishly I tried something like this, but that didn't work yet: ```patch @@ -89,6 +93,17 @@ pub fn create_layout( text_style.set_font_families(&[family_name.as_str()]); } + text_style.set_font_arguments(Some( + &skia_safe::FontArguments::new().set_variation_design_position( + skia_safe::font_arguments::VariationPosition {...