emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Rehan Deen <rehan.deen@gmail.com>, 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: Thu, 26 Dec 2024 23:49:39 +0700	[thread overview]
Message-ID: <eedf34d6-070d-471f-a9f5-626d7bc86f91@gmail.com> (raw)
In-Reply-To: <87pllx7219.fsf@gmail.com>

On 12/12/2024 15:12, Rehan Deen wrote:
> on the webpage https://orgmode.org/, Emacs is able to capture the link
> and title ("Org mode for GNU Emacs") as desired, but the browser
> displays a blank page with the following text:
> 
>      org-protocol://store-link?url=https%3A%2F%2Forgmode.org%2F&title=Org+mode+for+GNU+Emacs
> 
> I have to hit refresh to redisplay the original webpage.

Have you considered reporting a bug to Firefox?

I have tried year old versions of Chromium and Firefox and have realized 
that e.g. javascript:a="test" consistently replaces document content. 
Chromium still discards expression value in the case of assignment to 
"location". So the change is specific to Firefox (including ESR channel) 
and perhaps an unintentional side effect of another fix, likely a 
security one.

> Interestingly, the `org-capture` extension for Firefox from
> https://github.com/sprig/org-capture-extension continues to work without
> producing this issue (i.e. the link is captured and the webpage
> continues to be displayed properly).

So Firefox and Chromium behavior content scripts has diverged. Chromium 
asks permission on behalf of the current web page while Firefox treats 
as the add-on permission. Likely it is a result of
<https://bugzilla.mozilla.org/1792138>
"(CVE-2023-25729) Extensions are not prompted before opening external 
schemes, leading to security issues"

Treatment of external protocol handlers is rather inconsistent in 
browsers and it is unstable.


  parent reply	other threads:[~2024-12-26 16:50 UTC|newest]

Thread overview: 19+ 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
2024-12-16 16:01       ` [PATCH] org-protocol: Add void() to bookmarklets Max Nikulin
2024-12-16 16:40         ` Max Nikulin
2024-12-22 12:43           ` Ihor Radchenko
2024-12-22 12:42         ` Ihor Radchenko
2024-12-24 14:14           ` Max Nikulin
2024-12-24 14:23             ` Ihor Radchenko
2024-12-27 16:48               ` [PATCH v2] " Max Nikulin
2024-12-27 18:13                 ` Ihor Radchenko
2024-12-28 15:50                   ` [PATCH] etc/ORG-NEWS: Clarify org-protocol bookmarklet issue Max Nikulin
2024-12-28 16:58                     ` Ihor Radchenko
     [not found]   ` <875xnp6qin.fsf@gmail.com>
2024-12-12 17:15     ` [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-26 16:49 ` Max Nikulin [this message]
2024-12-28 13:55   ` Rehan Deen
2024-12-28 16:05     ` Max Nikulin

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=eedf34d6-070d-471f-a9f5-626d7bc86f91@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).