From: Unknown <unknown@unknown.invalid>
To: "Paul Magwene, Ph.D." <paul.magwene@duke.edu>
Cc: Alan Third <alan@idiocy.org>,
43470@debbugs.gnu.org,
"43470-done@debbugs.gnu.org" <43470-done@debbugs.gnu.org>
Subject: bug#43470: 27.1; Drag and Drop not working properly in 27.1 on OSX
Date: Sat, 19 Sep 2020 13:02:15 +0200 [thread overview]
Message-ID: <m1363e113c.fsf@yahoo.es> (raw)
In-Reply-To: <C82E3069-899F-42DF-A966-775144058F8C@duke.edu> (Paul Magwene's message of "Fri, 18 Sep 2020 23:22:46 +0000")
"Paul Magwene, Ph.D." <paul.magwene@duke.edu> writes:
>
> My testing suggests that there's still source application specific behavior.
>
> * Simple drag of images works when Safari or Chrome is the web browser.
>
> * No combination of Option, Command, or Control seems to work in Firefox; the drag behavior always produces a URL.
>
Thank you for the additional testing. I can reproduce the drag behavior
differences between 26.3 and 27.1, and also the Firefox vs. other
browsers difference.
I'm familiarizing with that part of the codebase and I'll prepare a
patch that will keep the same default drag behavior as in 26.3.
Thanks.
next prev parent reply other threads:[~2020-09-19 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:27 bug#43470: 27.1; Drag and Drop not working properly in 27.1 on OSX Paul Magwene, Ph.D.
2020-09-17 17:46 ` Alan Third
2020-09-17 18:12 ` Unknown
2020-09-17 19:46 ` Alan Third
2020-09-18 12:00 ` Unknown
2020-09-18 12:54 ` Alan Third
2020-09-18 18:34 ` Unknown
2020-09-18 19:11 ` Alan Third
2020-09-18 21:27 ` Paul Magwene
2020-09-18 22:15 ` Alan Third
2020-09-18 23:22 ` Paul Magwene, Ph.D.
2020-09-19 11:02 ` Unknown [this message]
2020-09-19 12:45 ` Unknown
2020-09-22 12:24 ` Alan Third
2020-09-26 11:39 ` Unknown
2020-09-27 9:59 ` Alan Third
2020-09-27 22:22 ` Unknown
2020-10-03 14:43 ` Alan Third
2020-09-26 11:39 ` Unknown
2020-09-19 14:08 ` Alan Third
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=m1363e113c.fsf@yahoo.es \
--to=unknown@unknown.invalid \
--cc=43470-done@debbugs.gnu.org \
--cc=43470@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=paul.magwene@duke.edu \
/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.