; Minor fix for nsxwidget patch

* lisp/xwdget.el (xwidget-webkit-download-dir)
(xwidget-webkit-save-as-file): Set version to 28.1 because the patch
was introduced in Emacs 28.0.50.

* src/nsxwidget.m: Fix typo.

diff --git a/lisp/xwidget.el b/lisp/xwidget.el
index 074320855c5f726998aede12a633381142612141..e5c1b47f3b1190d59d102ead0f30b785da2b17ea 100644 (file)
--- a/lisp/xwidget.el
+++ b/lisp/xwidget.el
@@ -318,7 +318,7 @@ If non-nil, plugins are enabled.  Otherwise, disabled."))
 
 (defcustom xwidget-webkit-download-dir "~/Downloads/"
   "Directory where download file saved."
-  :version "27.1"
+  :version "28.1"
   :type 'file)
 
 (defun xwidget-webkit-save-as-file (url mime-type file-name)
@@ -348,7 +348,7 @@ If non-nil, use a new xwidget webkit session after bookmark jump.
 Otherwise, it will use `xwidget-webkit-last-session'.
 When you set this variable to nil, consider further customization with
 `xwidget-webkit-last-session-buffer'."
-  :version "27.1"
+  :version "28.1"
   :type 'boolean)
 
 (defun xwidget-webkit-bookmark-make-record ()

diff --git a/src/nsxwidget.m b/src/nsxwidget.m
index e81ca7fc0cb541cee267925ca1dda4ffc640c441..2910d97225a9a461f5d2b4557ae99e466d305c15 100644 (file)
--- a/src/nsxwidget.m
+++ b/src/nsxwidget.m
@@ -33,14 +33,14 @@ along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.  */
 /* Thoughts on NS Cocoa xwidget and webkit2:
 
    Webkit2 process architecture seems to be very hostile for offscreen
-   rendering techniques, which is used by GTK xwiget implementation;
+   rendering techniques, which is used by GTK xwidget implementation;
    Specifically NSView level view sharing / copying is not working.
 
    *** So only one view can be associcated with a model. ***
 
    With this decision, implementation is plain and can expect best out
    of webkit2's rationale.  But process and session structures will
-   diverge from GTK xwiget.  Though, cosmetically similar usages can
+   diverge from GTK xwidget.  Though, cosmetically similar usages can
    be presented and will be preferred, if agreeable.
 
    For other widget types, OSR seems possible, but will not care for a