* bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support
@ 2024-11-10 15:13 Andrew De Angelis
2024-11-14 8:22 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Andrew De Angelis @ 2024-11-10 15:13 UTC (permalink / raw)
To: 74295
[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]
Hello everyone.
I have a question and a possible patch to contribute.
For context: the most glaring issues with xwidget support of NS have been
fixed: I contributed a patch to get rid of memory leaks a while ago, under:
"bug#60703 Patches to xwidget code".
I've just noticed that I forgot to update the TODO file, so it still
mentions crashes:
> trying to display a xwidget in the "killed" state will make Emacs crash.
I've used the xwidget feature extensively and in my experience, xwidgets do
not crash Emacs anymore.
Question:
- Could someone clarify what we mean by displaying a xwidget in the
"killed" state? I want to make sure I understand the problem and it's fixed
Possible patch (if the problem is indeed fixed):
Attached. Remove the mention of crashes, and clarify which features are
still missing from the NS port.
Thanks for all your work!
[-- Attachment #1.2: Type: text/html, Size: 1142 bytes --]
[-- Attachment #2: update-todo-for-xwidget-ns.patch --]
[-- Type: application/octet-stream, Size: 1011 bytes --]
diff --git a/etc/TODO b/etc/TODO
index f9918fede38..fa19d9f96d9 100644
--- a/etc/TODO
+++ b/etc/TODO
@@ -955,13 +955,13 @@ This sections contains features found in other official Emacs ports.
Emacs 25 has support for xwidgets, a system to include WebKit widgets
into an Emacs buffer.
-They work on NS, but not very well. For example, trying to display a
-xwidget in the "killed" state will make Emacs crash. This is because
-the NS code has not been updated to keep with recent changes to the
-X11 and GTK code.
+They work on NS, but not very well. This is because the NS code has
+not been updated to keep with recent changes to the X11 and GTK code.
-Many features such as xwidget-webkit-edit-mode do not work correctly
-on NS either.
+Many features do not work correctly on NS, such as:
+ - xwidget-webkit-edit-mode
+ - xwidget-webkit-isearch-mode
+ - xwidget-webkit-browse-history.
**** Respect 'frame-inhibit-implied-resize'
When the variable 'frame-inhibit-implied-resize' is non-nil, frames
^ permalink raw reply related [flat|nested] 4+ messages in thread
* bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support
2024-11-10 15:13 bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support Andrew De Angelis
@ 2024-11-14 8:22 ` Eli Zaretskii
2024-11-30 9:46 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2024-11-14 8:22 UTC (permalink / raw)
To: Andrew De Angelis, Po Lu; +Cc: 74295
> From: Andrew De Angelis <bobodeangelis@gmail.com>
> Date: Sun, 10 Nov 2024 10:13:17 -0500
>
> I have a question and a possible patch to contribute.
> For context: the most glaring issues with xwidget support of NS have been fixed: I contributed a patch to get
> rid of memory leaks a while ago, under: "bug#60703 Patches to xwidget code".
>
> I've just noticed that I forgot to update the TODO file, so it still mentions crashes:
> > trying to display a xwidget in the "killed" state will make Emacs crash.
>
> I've used the xwidget feature extensively and in my experience, xwidgets do not crash Emacs anymore.
>
> Question:
> - Could someone clarify what we mean by displaying a xwidget in the "killed" state? I want to make sure I
> understand the problem and it's fixed
Can someone who knows about this (Po Lu?) answer Andrew's question?
> Possible patch (if the problem is indeed fixed):
> Attached. Remove the mention of crashes, and clarify which features are still missing from the NS port.
I installed that on the emacs-30 release branch, thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support
2024-11-14 8:22 ` Eli Zaretskii
@ 2024-11-30 9:46 ` Eli Zaretskii
2024-12-14 9:32 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2024-11-30 9:46 UTC (permalink / raw)
To: luangruo; +Cc: bobodeangelis, 74295
Ping!
> Cc: 74295@debbugs.gnu.org
> Date: Thu, 14 Nov 2024 10:22:21 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Andrew De Angelis <bobodeangelis@gmail.com>
> > Date: Sun, 10 Nov 2024 10:13:17 -0500
> >
> > I have a question and a possible patch to contribute.
> > For context: the most glaring issues with xwidget support of NS have been fixed: I contributed a patch to get
> > rid of memory leaks a while ago, under: "bug#60703 Patches to xwidget code".
> >
> > I've just noticed that I forgot to update the TODO file, so it still mentions crashes:
> > > trying to display a xwidget in the "killed" state will make Emacs crash.
> >
> > I've used the xwidget feature extensively and in my experience, xwidgets do not crash Emacs anymore.
> >
> > Question:
> > - Could someone clarify what we mean by displaying a xwidget in the "killed" state? I want to make sure I
> > understand the problem and it's fixed
>
> Can someone who knows about this (Po Lu?) answer Andrew's question?
>
> > Possible patch (if the problem is indeed fixed):
> > Attached. Remove the mention of crashes, and clarify which features are still missing from the NS port.
>
> I installed that on the emacs-30 release branch, thanks.
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support
2024-11-30 9:46 ` Eli Zaretskii
@ 2024-12-14 9:32 ` Eli Zaretskii
0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2024-12-14 9:32 UTC (permalink / raw)
To: luangruo; +Cc: bobodeangelis, 74295
Ping! Ping! Po Lu, can you please answer Andrew's question, if you
know the answer?
> Cc: bobodeangelis@gmail.com, 74295@debbugs.gnu.org
> Date: Sat, 30 Nov 2024 11:46:19 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> Ping!
>
> > Cc: 74295@debbugs.gnu.org
> > Date: Thu, 14 Nov 2024 10:22:21 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > > From: Andrew De Angelis <bobodeangelis@gmail.com>
> > > Date: Sun, 10 Nov 2024 10:13:17 -0500
> > >
> > > I have a question and a possible patch to contribute.
> > > For context: the most glaring issues with xwidget support of NS have been fixed: I contributed a patch to get
> > > rid of memory leaks a while ago, under: "bug#60703 Patches to xwidget code".
> > >
> > > I've just noticed that I forgot to update the TODO file, so it still mentions crashes:
> > > > trying to display a xwidget in the "killed" state will make Emacs crash.
> > >
> > > I've used the xwidget feature extensively and in my experience, xwidgets do not crash Emacs anymore.
> > >
> > > Question:
> > > - Could someone clarify what we mean by displaying a xwidget in the "killed" state? I want to make sure I
> > > understand the problem and it's fixed
> >
> > Can someone who knows about this (Po Lu?) answer Andrew's question?
> >
> > > Possible patch (if the problem is indeed fixed):
> > > Attached. Remove the mention of crashes, and clarify which features are still missing from the NS port.
> >
> > I installed that on the emacs-30 release branch, thanks.
> >
> >
> >
> >
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-12-14 9:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-11-10 15:13 bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support Andrew De Angelis
2024-11-14 8:22 ` Eli Zaretskii
2024-11-30 9:46 ` Eli Zaretskii
2024-12-14 9:32 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).