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

[Po Lu]

Akira Kyle <akira@akirakyle.com> writes:

>> If you play a GIF that depicts a scrolling WebKitWebView, you can't
>> really "scroll" it independently either.  Ditto for xwidgets.

> I would argue that most users would expect scrolling an xwidget webkit
> buffer that is visible in two windows to behave like eww, not like
> advancing a frame in a GIF.  That paradigm being that each window is a
> separate view into a buffer where the position in the buffer that the
> window displays is independent of any other window (ie is window
> local).

The only paradigm I see is that a single glyph (such as an xwidget
glyph, produced by a display property) should be able to display in
multiple windows, which this implementation (and the GIF display as
well) fulfils.