Change in Drag and Drop between Chrome and FireFox?

Developers
#1

I recall dragging tiddlers from one wiki to another regardless of the browser in use.

  • The Same was also true dragging bookmarks and bookmarklets between browsers;
  • In windows I thought dragging over the browser in the toolbar would open the browser and I could then hover over the a tab to change tabs and drop in that tab. However this first step no longer works, I must have both browsers visible.

Chrome Version 104.0.5112.102 (Official Build) (64-bit)

FireFox 104.0 (64-bit)

  • Chrome seems to be the problem, or at least the way tiddlywiki responds in chrome.

  • Using Settings > Display tiddler titles as links

Chrome to FireFox

  • Tiddler is added to $:/Import process but only as a link in an untitled tiddler
    • Tiddler transfer Work around below
  • Drag a Chrome bookmarklet to FireFox favourites works but you need to supply the name otherwise the name will be the javascript code
  • Drag a bookmarklet to a tiddlywiki creates a tiddler in Firefox with an untitled name containing the bookmarklets code

FireFox to Chrome

  • Tiddler is added to $:/Import process correctly
  • Drag a FireFox bookmarklet to Chrome favourites works
  • Drag a bookmarklet to a tiddlywiki creates a tiddler in Chrome with a .URL
    • Containing an [InternetShortcut]
    • see “Tiddler transfer Work a around” to Move tiddlers from Chrome to FireFox

Tiddler transfer Work a around

  • Export tiddler or tiddlers to file in to a scratch folder
  • Once the download is complete from the downloads or bottom bar drag the download to the wiki in Fire Fox
#2

This also applies to plugins. For example, if the wiki is open in Firefox and the plugin page is open in Chrome, dragging the plugin from Chrome to Firefox fails.

Personally, this impacts me as I only use Firefox for TiddlyWiki. As the default Firefox page, it makes it simple to open my wiki. :slightly_smiling_face: However, the source of the plugin drag and drop failure isn’t obvious, especially for someone who never uses that functionality (such as me.)

#3

Some more details would be helpful:

  • What did you do? (Provide exact step-by-step descriptions… what did you click in Chrome to start dragging, where did you drop in Firefox, etc.
  • What response were you expecting from Firefox?
  • How do you know it didn’t work?
#4

@pearson as you know plugins are just tiddlers. If you look at my OT it covers all the different interactions between browsers. If you have something new please provide it.

@EricShulman regarding the OT what more would you like to know?

#5

@TW_Tones regardless of the info provided in your original post, my questions were specifically concerning @pearson’s report that “dragging the plugin from Chrome to Firefox fails”

#6

@EricShulman I understand but my OT was all about dragging Plugins and any other tiddler, so I can’t actually Imagin any different behaviour to that outlined in the OT.

  • Dragging a plugin from a Wiki in Chrome to Fire fox results in “untitled” containing the plugin name.
  • For example in chrome open Control panel Plugins tab, and drag a plugin to a wiki in Firefox and drop it.
    • The reverse works fine
  • I have the chrome browser set as the default browser for HTML and urls, but changing it to firefox did not change this behaviour.
  • Crome to Edge works, Edge to FireFox does the same thing.

This has being occurring for me since before the above OT, and still is, so if you have any ideas for both @pearson and myself I would be grateful.

#7

I think that’s discussed at a GH issue: [BUG] erratic drag and drop issue in Safari on OSX · Issue #7305 · Jermolene/TiddlyWiki5 · GitHub

#8

I had actually typed up the steps to reproduce the problem, but then discovered this thread and simplified my reply. :slightly_smiling_face:

I had a nice writeup for here, but as a new user I’m limited to 1 embedded image and 2 embedded links. So… please see the GitHub issue #7740.

Note that this problem only happens when dragging and dropping a plugin from Google Chrome to Firefox. It does not happen when dragging and dropping a plugin from Firefox to Google Chrome, or when dragging and dropping between two windows of the same browser.

#9

Yeah, I think you touch on the problem in one of your posts in that thread.

I won’t pretend to know anything about the internals of TiddlyWiki (I’m honestly very impressed that it works as well as it does!), but it strikes me that since Firefox is recognizing some content from the drag and drop (in my example, the import shows $:/plugins/kookma/section as the content if the title’s down arrow is pressed), the problem is probably solvable by encoding that content differently. But, again, I won’t pretend to know the complexities of actually doing that in this case. :slightly_smiling_face:

What might be a simple temporary solution would be to recognize that a plugin import is failing (perhaps by noting that the title is “Untitled” as well as the $:/plugins/ in the content), and to pop up a warning that Chrome to Firefox plugin drag and drop does not work. It’s not elegant, but such a warning would have saved me a lot of time – presumably it would do the same for others who have the bright idea of using Firefox for their wiki.

#10

You’re right, your original post does cover this case. That said, being new to TiddlyWiki, I didn’t recognize that fact when I first read your post. I’ve learned quite a bit about it in the last few days.

That said, my situation also points to a problem here for new users. As far as I was aware, I was following the instructions for installing a plugin. The instructions are simple enough, so the fact it was failing was a mystery.

As I suggested in my last reply to this thread, having some sort of warning of a failing plugin drag and drop could be very useful to those new to TiddlyWiki. This might seem like an edge case, but there must be others out there who have thought of using a different browser for their wikis. After all, it’s a very simple method of quickly popping your the up, and of preventing the search through browser windows to find the wiki.

#11

I would hope we can go directly to a solution, and avoid the warning message, but if no solution a warning may help, only how do we tell the difference from a ctrl-V ?

  • personaly I think there is a bug that tiddlywiki may be able to over come.
#12

@TW_Tones Can you test: https://tiddlywiki5-git-fork-pmario-fix-dnd-for-mobile-touch-jermolene.vercel.app/ if this still happens?

#13

Shall I run and test it in both chrome and firefox or just one side?

#14

Quick tests

The Bookmarklets draged from one Browser to another still behave as they used to

  • To Chrome becomes URL
  • To Firefox becomes untitled

Looks like you have solved it @pmario

#15

Do you have a link? … I’m not sure what you did test here?
Does it work?

Eg: If I drag & drop a plugin to the browser bookmarks area it works for me. The title needs to be adjusted, but if I drag a bookmark into TW it will be imported in the right way.

There may be a fix for the bookmark name, but that was not part of the PR

#16

Let us leave the bookmarklet issue for now, and revisit later. I did raise it in the OT but on rereading it adds some complexity.

Thanks for your work @pmario using FireFox and Chrome is part of my daily workflow and this has being a pain.

#17

@TW_Tones … Can you test again?

There have been some changes to the code. Just to be sure. See GH PR for details

Make sure that you SHIFT- reload the page, so browser caching is switched off

#18

It once again passes the test, noting that it depends on the test wiki being the source, so If I drag from tiddlywiki.com (vanilla) to the test wiki in FireFox it imports only as untitled. From the test wiki in chrome to the test wiki AND to tiddlywiki (vanilla also woks).

:+1: