Closed Bug 1607030 Opened 10 months ago Closed 10 months ago

Selecting a most-used component goes into a loop when switching from guided bug entry form


( :: Bug Creation/Editing, defect)

Not set





(Reporter: Nick_Levinson, Assigned: kohei.yoshino)





(1 file)

46 bytes, text/x-github-pull-request
Details | Review

Under my login, when I wanted to report a bug today, a page asked for a most-used component and I clicked the link for "Firefox :: Tabbed Browser". This entered a loop that seemed endless. The solution was to pick from "the following selections", in that case Firefox.

The link URL or its destination should be repaired.

Only slightly relevant: bug 103722.

Please provide a clear list of steps to reproduce, step by step, including URLs. Thanks!

Flags: needinfo?(Nick_Levinson)
  1. Log into Mozilla Bugzilla.

  2. Click the New Bug icon.

  3. Click the "Switch to the standard bug entry form" link at the bottom.

  4. This takes you to and now look at "Choose from your most-used components".

  5. Click the "Firefox :: Tabbed Browser" link.

Actual result: The link takes the intending-reporter to the page the visitor is alaready on, thus looping, although the URL eventually becomes much longer on the trailing end (part is the same as the URL in step 4).

Expected result: The link should bring up the next page in the process for reporting a bug, probably with the program and component already selected.

Additional info: The destination URLs seem to have repetition of parameter/s.

Flags: needinfo?(Nick_Levinson)

Thanks Nick for the report. I implemented the most-used component section and can reproduce the issue with any component. Fix coming shortly.

Assignee: nobody → kohei.yoshino
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Summary: Firefox "most-used component" as "Firefox :: Tabbed Browser" loops → Selecting a most-used component goes into a loop when switching from guided bug entry form
Attached file GitHub Pull Request

Merged to master.

Closed: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.