all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sat, 28 Dec 2024 19:25:04 +0530	[thread overview]
Message-ID: <877c7jq5dz.fsf@gmail.com> (raw)
In-Reply-To: <eedf34d6-070d-471f-a9f5-626d7bc86f91@gmail.com> (Max Nikulin's message of "Thu, 26 Dec 2024 23:49:39 +0700")

Max Nikulin <manikulin@gmail.com> writes:
> 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.

I am not sure what I could add as my knowledge of what constitues
correct browser behavior is limited. Feel free to do so on my behalf.



>> 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.

Not sure what to say or do about this, but thanks for letting me know. I
suppose it means that we should expect some further disruptive behavior
to extensions (not just the insecure bookmarklets) using Org-protocol,
but as you indicate it sounds like it is a wider problem.



  reply	other threads:[~2024-12-28 14:04 UTC|newest]

Thread overview: 20+ 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
2024-12-29 11:45                       ` Max Nikulin
     [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
2024-12-28 13:55   ` Rehan Deen [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877c7jq5dz.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.