From: Rehan Deen <rehan.deen@gmail.com>
To: emacs-orgmode@gnu.org
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: Fri, 13 Dec 2024 00:17:57 +0530 [thread overview]
Message-ID: <878qsk68ma.fsf@gmail.com> (raw)
In-Reply-To: <366e2a83-3703-40fd-b8eb-f5746a17864d@gmail.com> (Max Nikulin's message of "Thu, 12 Dec 2024 21:14:26 +0700")
> Please, reply to the list.
Apologies.
> I hope, you used the full expression instead of ellipsis.
Yes, I doubt it would have "worked" otherwise (in the sense that the
link would not have been captured).
> 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.
Thanks, that works and is consistent with what I thought was happening
-- I was unsure of the syntax here. Yes, the "fix" I had before did
produce errors in the console, which presumably also displaced the
'org-protocol:...' string. Not sure what upgrade to the browser has
caused this string to be rendered now ...
> 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.
That extension looks useful -- though I am currently interested in
extracting only a certain amount of information from pages. But I take
your point about the security risk.
next prev parent reply other threads:[~2024-12-12 18:48 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
2024-12-12 18:47 ` Rehan Deen [this message]
[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=878qsk68ma.fsf@gmail.com \
--to=rehan.deen@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).