From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Rehan Deen <rehan.deen@gmail.com>
Subject: Re: [BUG] Org-protocol bookmarklets in Firefox behaving badly after recent upgrade [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.4/lisp/org/)]
Date: Thu, 12 Dec 2024 21:14:26 +0700 [thread overview]
Message-ID: <366e2a83-3703-40fd-b8eb-f5746a17864d@gmail.com> (raw)
In-Reply-To: <9aea6ebe-66a2-47d6-a7cc-a7ad9e8af284@gmail.com>
Please, reply to the list.
On 12/12/2024 17:34, Max Nikulin wrote:
> On 12/12/2024 15:12, Rehan Deen wrote:
>> javascript:location.href='org-protocol://store-link?'+new
>> URLSearchParams({url:location.href, title:document.title});
>
> Try to add "(void)"
> javascript:(void)location.href='org-protocol:...
I hope, you used the full expression instead of ellipsis. I forgot about
"+new", so it should be with another variant of parenthesis:
javascript:void(location.href='org-protocol:...)
The idea is to discard a string returned by the assignment operator.
Try to open web developer tools [F12] and switch to console. You might
notice some error messages.
> However bookmarklets are unsafe, you have to allow *web page* to launch
> a handler. In the case of an extension this permission may be given to
> the extension (but sprig/org-capture-extension still use the unsafe way).
You may try
https://github.com/vifon/org-protocol-for-firefox/
that uses another method to launch external protocol handler.
Personally I am interested in extracting as much page metadata as
possible, so bookmarklets and simple extensions is not an option.
In future, I hope, it is better to avoid org-protocol.el hack with an
advice and rely on the new `server-eval-args-left' feature.
next prev parent reply other threads:[~2024-12-12 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 8:12 [BUG] Org-protocol bookmarklets in Firefox behaving badly after recent upgrade [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.4/lisp/org/)] Rehan Deen
2024-12-12 10:34 ` Max Nikulin
2024-12-12 14:14 ` Max Nikulin [this message]
2024-12-12 18:47 ` Rehan Deen
[not found] ` <875xnp6qin.fsf@gmail.com>
2024-12-12 17:15 ` Rehan Deen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=366e2a83-3703-40fd-b8eb-f5746a17864d@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rehan.deen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).