Closed Bug 1847067 Opened 1 year ago Closed 1 year ago

Opening Back/Forward dropdown by long-pressing, and select a session entry navigates wrong entry.

Categories

(Core :: DOM: Events, defect, P1)

Firefox 117
Desktop
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1846714

People

(Reporter: alice0775, Assigned: sefeng)

References

(Regression)

Details

(Keywords: nightly-community, regression)

[Tracking Requested - why for this release]:

#1 Steps to reproduce:
0. Navigate to several page in a tab.

  1. So, Suppose now that the session history looks like this
   page 5
   page 4
   ✔page 3  <--- current
   page 2
   page 1
   New Tab

Long-press on Back button, select "Page 5" while keeping the mouse button, then release the mouse button.

Actual Results:
Navigated to page 4

Expected Results:
Should navigate to the selected entry Page 5

#2 Steps to reproduce:

  1. Suppose now that the session history looks like this
   page 5
   page 4
   ✔page 3  <--- current
   page 2
   page 1
   New Tab

Long-press on Forward button, select "Page 1" while keeping the mouse button, then release the mouse button.

Actual Results:
Navigated to page 2

Expected Results:
Should navigate to the selected entry Page 1

It appears that the command of the long-pressed button is also executed after navigates the selected entry to change depending on the position of the current and selected entry and the long-pressed button.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=728f4a4d08f5b369ce5c7bea17a23cdfbb30f196&tochange=92ad9c748611fc9b5be547415a651f136a27346f

Regressed by Bug 1792110.

See Also: → 1846714

:sefeng, since you are the author of the regressor, bug 1792110, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(sefeng)

The bug is marked as tracked for firefox117 (beta) and tracked for firefox118 (nightly). However, the bug still isn't assigned.

:hsinyi, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(htsai)

Sean is tackling this along with bug 1846714.

Severity: -- → S2
Flags: needinfo?(htsai)
Priority: -- → P1

This is a reminder regarding comment #2!

The bug is marked as tracked for firefox117 (beta) and tracked for firefox118 (nightly). We have limited time to fix this, the soft freeze is in 13 days. However, the bug still isn't assigned.

Assignee: nobody → sefeng
Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1846714
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.