Introduce "killed" state for xwidgets (Re: shr using `make-xwidget' incorrectly)

[Po Lu]

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> I think the best thing to do in this case would be to introduce a
>> `dead' state for xwidgets, not unlike killed buffers and dead frames,
>> which an xwidget is set to after being killed.
>>
>> Then, performing any sort of operation on a killed xwidget can either
>> throw an error, or do nothing.

> Sounds good to me.

0001-Prevent-crashes-in-xwidgets-whose-buffers-have-been-.patch
Description: Text Data

Thanks, how does this look to you?  And perhaps Eli has something to
say about it as well.

Thanks in advance.