Recent list ignores a click if the pointer moves 1 pixel between press and release

5 replies
37 views
Translate

Home screen: Recent list ignores a click if the pointer moves 1 pixel between press and release

Premiere Pro 26.5.2, macOS 27.2, Mac Studio (Apple Silicon), Anker Mouse.
Home Screen plugin com.adobe.ccx.start 10.16.4.

Problem
Opening a project from the Recent list on Home usually takes three or four clicks.

Cause, reproduced with scripted mouse events
1. Home screen settled, press and release at exactly the same point on a row: the project opens. 3 of 3 tries.
2. Press on the row, move the pointer 4 pixels, release on the same row: nothing happens.
3. Same with a 1 pixel move: nothing happens.
4. A still click at the same point right afterwards opens the project.

So the list treats any pointer movement during the click as a drag and drops the click. The row highlights and the path tooltip shows, but the project does not open. With a wired mouse, a 1 to 2 pixel move during a click is normal, so most clicks are lost.

Second, smaller issue
After a fresh launch, a still click 2 to 5 seconds after Home appeared did nothing. The same click about 8 seconds later opened the project (one test). The UXP log shows the Recents component re-rendering about 5 seconds after its first render, when the avatar loads, on every launch (10 of 10 logs), and often again about 10 seconds later.

Expected
A click whose press and release land on the same row should open the project, with a normal drag tolerance of a few pixels, as in Finder.

Workarounds
File > Open Recent, or opening the .prproj from Finder.

Ruled out
Row hit area (the whole row responds), the tooltip, third-party mouse drivers (none installed), screen overlay utilities (still clicks work with them running).

KatieToo

Community Manager

Hi @Yeaton Studios

Welcome back to the Premiere forums and thanks for giving us this very detailed report about the Recent Projects issue you’re having.

You mentioned reproducing this with “scripted mouse events.” Were those automated events, or have you also reproduced the missed click using a physical mouse? If you tested with a physical mouse, could you confirm whether the Anker mouse is wired or wireless, and roughly how often the click fails?

You also mentioned UXP logs showing the Recent component re-rendering. How did you capture those logs? If possible, could you share the relevant timestamped excerpt and clarify whether it explicitly records a re-render or whether that’s your interpretation of the timing? If the logs may contain private information, let us know and we can provide a private upload link. I can send you that in a DM so keep an eye out for that.

Separately, you mentioned that a click shortly after launch can sometimes be missed. Is that repeatable, and if so, about how often does it happen since it sounds less frequently?

Hope to help!
Katie

Translate

Y

Yeaton StudiosAuthor

Participating Frequently

Thanks for the quick reply. Answers in order.

1. Scripted versus physical mouse
The numbered steps in my report were automated: mouse down, move and mouse up events posted at the OS level, so I could control the movement to the pixel. That is how I could tell a 1 pixel move apart from a still click.
With a physical mouse it is the everyday problem that made me look into this: it usually takes me three or four clicks to open a recent project. The mouse is wired anker model A7851. By hand I can't tell whether a given miss was caused by movement, but if I deliberately hold the mouse still and click, it opens.

2. The UXP logs
I did not capture them specially. Premiere writes them on every launch to:
~/Library/Logs/Adobe/Adobe Premiere Pro 2026/UXPLogs_<date>_<time>.log
The re-render is recorded explicitly. The Home Screen plugin logs a "Recents rendering" line each time, and a mobx.trace line saying render was invalidated by a change in recentsProps. What is my interpretation is the link between those re-renders and the missed click after launch. Excerpt from one launch (file path removed from the avatar line):

[2026-11-13_11-03-25] [HS] [Drover] CCX-Start-Drover : Home screen visibility set to visible without back button.
[2026-11-13_11-03-25] [HS] [Drover] PPRO: Recent files provided. No. of items = 10
[2026-11-13_11-03-25] [HS] [Recents] [Performance] Recents rendering 5187
[2026-11-13_11-03-25] [HS] [Recents] [Recents#render] elements= 10 assets= 0
[2026-11-13_11-03-25] [HS] [Performance] 1018 PERF - UI Ready
[2026-11-13_11-03-30] [HS] [AvatarDataLoader] Avatar Loader: Avatar file found and set using File Accessor.
[2026-11-13_11-03-30] [console] [mobx.trace] 'Po.render()' is invalidated due to a change in: 'Po@1250.recentsProps'
[2026-11-13_11-03-30] [HS] [Recents] [Performance] Recents rendering 10397
[2026-11-13_11-03-30] [console] [mobx.trace] 'Po.render()' is invalidated due to a change in: 'Po@1250.recentsProps'
[2026-11-13_11-03-30] [HS] [Recents] [Performance] Recents rendering 10432

The same 5 second gap followed by two re-renders is in all 10 launch logs I checked. I'm happy to send full logs through a private upload link.

3. The missed click right after launch
Honestly, I only tested that one once, so I can't tell you how often it happens. I clicked a few seconds after Home came up and nothing happened, then clicked again a few seconds later and the project opened. It could be a fluke. The movement issue is the one I can make happen every time, so I'd focus there but just wanted to mention as the screen does seem to have a loading period where it doesn’t accept click in my general use case.

Translate

O

Oliver5EDD

Participant

Second that. This was bothering me for the lasst few versions. Pretty hard for graphic tablet users

Translate

KatieToo

Community Manager

@Oliver5EDD Could we get some additional details for our bug report about your specs and in which Premiere? Are you also using a similar mouse and what type?

Premiere Version: What is the exact Premiere version and build you’re using? Help > About Premiere or Premiere > About Premiere
Setup/OS: Please specify Windows 11/10 or Mac, plus what macOS, along with driver version/build.
- GPU Driver version/build(Windows only): We recommend updating to the most recent version; for NVIDIA users, we strongly recommend the Studio version of the driver.
- Mac Chip (Mac Only): what M-series chip? If Intel, please include GPU.
Media Files: video, images, etc. and what types (can check under Media Properties)
Project Size: About how big is your project file? Is it in a Production or Multicam? Approximately how many clips are involved in a rough estimate
Media Storage: Are your Scratch Disks set to your Documents folder or the same as project, and is this the same as the Media drive?

Also, please let us know the following for helpful context:

Does it affect all projects or only some? What about new projects with a few sample clips?
Do you recall which Premiere this was last working in, when It started, and what might have changed? Any plugins, OS update, drivers, etc.
Are you also using third party plugins and/or extensions, and if so, which ones and are they currently up to date?

Screen Recording: If possible, include a recording of your screen with Premiere in full, showing the issue as that helps us see exactly what might be happening.

That would be much appreciated!
Katie

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.