johannphilippe

Also in #125 you are talking about `element` object, and here it is about `window`, so I'm afraid it won't be the same process.

I also noticed that `input_box` text can overflow a little bit if the elements size is limited to some sizes. It did overflow for a x limit of 30, and...

The overflow seems to happen on master branch as well. It seems to only reproduce when the `input_box` is inside a `limit` with `view_limits.max.x < 40`. I tried to investigate,...

As a reminder, "f" characters are only displayed if impair number of f are typed. The issue seems related to the `text_layout::impl` class. In the constructor, the 'f' character generates...

> Same bug for succession of 'f' and 'i' chars. So that may indeed be related to ligatures !

> Nice hunting! I suspected something like this. I thought it might have something to do with F-ligatures: https://creativepro.com/typetalk-the-ins-and-outs-of-f-ligatures/ ```c++ void hb_buffer::shape(hb_font const& font) { hb_feature_t userfeatures[1]; userfeatures[0].tag = HB_TAG('l','i','g','a');...

So, the error occurs with OpenSans and DejaVu fonts, but not with Roboto it seems. Edit : Roboto has issues as well, but not for 'ff'. The disappearances happens with...

I wrote a class copying `dynamic_list` and adapting a few actions from `composite_base` (click and key). It works with a special `cell_composer` whose `compose` method returns an already created element....

This class would also need to manage all actions (scroll, drag, cursor...). So, there is still some work to be done here :)

> > It works with a special `cell_composer` whose `compose` method returns an already created element. > > I don't think this is necessary. `cell_composer` as-is can already do that....