Project

General

Profile

Actions

Patch #42440

closed

Fix project selector focus by explicitly targeting the first selected item

Added by [Agileware]Haruka Asakura 10 days ago. Updated 3 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Projects
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

The current implementation in application.js attempts to focus on all elements matching .drdn-items a.selected when the project jump dropdown is expanded. This can cause unpredictable behavior if multiple elements match this selector, as only one element should receive focus.

This patch modifies the code to explicitly focus only on the first selected element by adding the .first() method before calling .focus(). This ensures consistent behavior when navigating the project selector dropdown.

In the project selection dropdown in the upper right corner, when you open a bookmarked project, the project that gets selected is not the one in the bookmark area but the one in the list below. I believe this degrades the usability when switching between bookmarked projects during work.

Steps to reproduce:

1. Have multiple projects that could be selected in the project jump dropdown
2. Bookmark one
3. Open the project selector dropdown
4. Select the bookmarked project and see the selected position

This is a simple fix that improves the reliability of the project navigation interface.


Files

Actions #1

Updated by Mizuki ISHIKAWA 10 days ago

I was able to reproduce the issue.

Just to be sure, I checked the case when there is no selected element, and confirmed that selected.first().focus(); does not cause any errors in that case.
The patch fix looks good to me.

Actions #2

Updated by Go MAEDA 5 days ago

  • Category set to Projects
  • Target version set to 6.0.5

Setting the target version to 6.0.5.

Actions #3

Updated by Go MAEDA 4 days ago

  • Subject changed from Fix project selector focus when multiple elements are selected to Fix project selector focus by explicitly targeting the first selected item
  • Status changed from New to Resolved
  • Assignee set to Go MAEDA

Committed the fix in r23558. Thank you for your contribution.

Actions #4

Updated by Go MAEDA 3 days ago

  • Status changed from Resolved to Closed

Merged the fix into 6.0-stable branch in r23574.

Actions

Also available in: Atom PDF