Folder commands missing from "background" right click when I click on empty space next to folder

Lukevan is trying to click in the empty space BELOW the file items and implies that dropbox broke it, not that updating to windows 11 broke it.

Hannah then immediately asks what happens when you click the "blank space next to it". Next to what? Hannah thinks we're trying to interact with a folder as an item in the directory and missing by clicking too far to the right. Lukevan then sends a video proving he's clicking in the empty space below the items (there are no items, so he is clicking below zero items).

Rich then talks a lot and shows a video of clicking to the right of items, not below, showing he missed the point entirely. He explains that because the item has been missed, it shows the options that appears when right-clicking in the directory itself. It's not clear how Rich got those options to show up. Old dropbox I guess. I daresay today Rich wouldn't get them. These options not existing on Lukevan's system is what Lukevan is complaining about.

Paltik then mentions he understands the problem but misattributes it to a change in Windows 11.

Walter then misses the point completely and asks why Paltik can't click on "test folder's name". Paltik said "EMPTY SPACE", not "ON NAME".

Paltik then repeats EMPTY SPACE and draws an arrow pointing at EMPTY SPACE (and misattributes the problem to Windows 11 again)

Jay then mumbles something about "this is not our problem".

OK, let me straighten all this out. Windows 10, Windows 11, doesn't matter. Right click in an empty folder controlled by dropbox. Dropbox options should appear. They don't. A dropbox update broke this at some point (so says Lukevan, but I don't know if it ever worked on Win10). It's possible (likely, I'd guess) that Microsoft changed something which you need to accommodate with Win10 or at some point in an update thereafter.

Windows 7 - works. Dropbox 194.4.6267.
Windows 10 - doesn't work. Dropbox 194.4.6267.
Windows 11 - doesn't work. Dropbox 194.4.6267.

Dropbox is correctly registering itself in HCKR\Directory\Background\shellex\ContextMenuHandlers\DropboxExt like it's supposed to, but the extension must be internally declining it for some reason.

Note, by contrast, TortoiseGit works like I expect. The relevant code is starting here, to save you time, but dropbox could surely be fouling up at a number of other points:

Is dropbox staff ever going to reply or do I need to make a new bug for this?

If there's no reply in another month, I will make a new bug.

This is a duplicate of another bug, since it's being ignored by dropbox staff now.

https://www.dropboxforum.com/t5/Apps-and-Installations/Folder-commands-missing-from-quot-background-quot-right-click/td-p/631188/page/2

I'll try to explain the problem again without referencing the prior issue, so that maybe I can find different words to describe it in a way that will be finally understood.

The problem is simple. On Windows 10, when right-clicking in the empty space in an explorer directory set to "Large Icons" view, no dropbox context menu appears. This is what most people would use to get the share URL for a directory they're working in. The context menu which should appear (and used to, and still does on Windows 7), is the one which is accessed by the following workaround:

1. Navigate up one directory

2. Rightclick on the entry for the directory you were just in.

To put it another way, the expected behavior is that the dropbox context menu for a directory be the same whether you right click on the directory item inside its parent directory, or in the empty space inside the directory itself

Cool, got attention from staff to merge it to the dead thread but not to respond to it. World class support.

---

mgambrell wrote:

Cool, got attention from staff to merge it to the dead thread but not to respond to it. World class support.

---

I merged it. Not the staff.

A two week clock for a response started from last wednesday before I do it again.

This is a duplicate of another bug, since it's being ignored by dropbox staff now.

Folder commands missing from "background" right click when I click on empty space next to folder | The Dropbox Community 

I'll try to explain the problem again without referencing the prior issue, so that maybe I can find different words to describe it in a way that will be finally understood.

The problem is simple. On Windows 10, when right-clicking in the empty space in an explorer directory set to "Large Icons" view, no dropbox context menu appears. This is what most people would use to get the share URL for a directory they're working in. The context menu which should appear (and used to, and still does on Windows 7), is the one which is accessed by the following workaround:

1. Navigate up one directory

2. Rightclick on the entry for the directory you were just in.

To put it another way, the expected behavior is that the dropbox context menu for a directory be the same whether you right click on the directory item inside its parent directory, or in the empty space inside the directory itself

---

mgambrell wrote:

The problem is simple. On Windows 10, when right-clicking in the empty space in an explorer directory set to "Large Icons" view, no dropbox context menu appears.

---

Windows 10. Explorer set to show large icons. Dropbox context menu options are visible when right-clicking the empty space.

Please show me exactly where you clicked. Presumably it's at the bottom left of the context menu, where there's nothing at all, which would be the right place to repro the problem; however the context menu you got has "version history" which implies it's targeting a file. Then again, "Manage hard drive space" implies you targeted the directory.  What would happen if you clicked "Version history" from here? What would it be the history of? I also don't have "Don't sync to Dropbox.com"; so in general I have a different menu from you in a number of different ways and any of the differences could be causing a problem. Is this due to it being a Business plan account?

Before I tested this just now, I uninstalled winrar, 7-zip, and open-shell to make sure none of those were causing incompatibilities. None of that helped, but I have other shell extensions that could still be conflicting.