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: Fri, 13 Dec 2024 18:09:02 +0700 [thread overview]
Message-ID: <127c2db1-889f-4937-ab7a-767ef69facdd@gmail.com> (raw)
In-Reply-To: <878qsk68ma.fsf@gmail.com>
On 13/12/2024 01:47, Rehan Deen wrote:
>> I forgot about
>> "+new", so it should be with another variant of parenthesis:
>> javascript:void(location.href='org-protocol:...)
>
> Thanks, that works and is consistent with what I thought was happening
Thanks, so now it is known which way docs should be updated.
> Not sure what upgrade to the browser has
> caused this string to be rendered now ...
New behavior is more correct. It is consistent with <a
href="javascript:..."> links and allows to generate a HTML document to
display.
> That extension looks useful -- though I am currently interested in
> extracting only a certain amount of information from pages.
You may create your own extension. Unfortunately Firefox releases for
users require signing of extensions. Chromium is more liberal, after
enabling developer mode it is possible to install unpacked extensions.
In Firefox it can be only temporary loaded for the current session.
Some people publish extension code, but not its signed package:
<https://github.com/Stebalien/org-capture-extension/>
next prev parent reply other threads:[~2024-12-13 11:37 UTC|newest]
Thread overview: 6+ 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
2024-12-13 11:09 ` Max Nikulin [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=127c2db1-889f-4937-ab7a-767ef69facdd@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).