Re: Removing the `window-id' frame parameter on non-Core Input platforms

[Po Lu]

Akira Kyle <akira@akirakyle.com> writes:

> emacs-webkit uses the pointer obtained via 'window-id' on pgtk builds
> to help identify the correct gtk container widget containing contents
> of the emacs frame that should become the parent of the webkit widget.
> It's a bit of a hack but would be potentially more difficult without
> this pointer.

I'm not sure we want to allow direct access to the innards of how Emacs
utilises GTK widgets.  That way lies madness.

> I also know that EAF uses the 'widow-id' parameter on x+gtk builds in
> order to allow Qt widgets to be reparented onto emacs frames.

I've already discussed this with the EAF developers.  Until Qt gains the
ability to not select for TouchBegin, TouchUpdate and TouchEnd, EAF will
likely not work on XInput2 builds.

> Also a slight tangent, but Po, do you plan to make xwidgets work on
> pgtk? I'm wondering that since you've been trying to revive the
> xwidget code and fixed the flickering issues on x+gtk, that xwidgets
> are looking more like they are here to stay as a potentially
> non-experimental feature? If that's the case, then I think I'd like to
> then just integrate the work I've done on emacs-webkit into a pgtk
> version of xwidgets? I think one of the key differences between the
> codes are the osr versus one-to-one buffer-webkit view models.

I will work on it eventually, which will be before the release of Emacs
29.