"report a bug" link in the involvement portlet on bug listings is broken

Bug #1024866 reported by Ohadcn
50
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Richard Harding

Bug Description

the "report a bug" link on the bug listing page is not working, it does appear but clicking it has no effect.

the page source:

<a id="yui_3_2_0_1_1342333262361752" class="first js-action inactive" href="#"><a id="yui_3_2_0_1_1342333262361751" href="+filebug" class="menu-link-filebug sprite bugs">
              Report a bug
            </a></a>

using FF or Chromium.

Related branches

Revision history for this message
Curtis Hovey (sinzui) wrote :

The markup you show is invalid. It has a anchor in an anchor. Can you provide the URL of the page you saw this link on? The outer link implies you should not be able to use the link, such as when the project dose not use Launchpad to track bugs.

Changed in launchpad:
status: New → Incomplete
status: Incomplete → Triaged
tags: added: markup
Changed in launchpad:
importance: Undecided → Critical
Revision history for this message
Curtis Hovey (sinzui) wrote :

Okay I see this. markup on the involvement section of the bug listing page.

summary: - "report a bug" link is not working
+ "report a bug" link in the involvement portlet on bug listings is broken
description: updated
tags: added: regression
Curtis Hovey (sinzui)
tags: added: javascript
Revision history for this message
Curtis Hovey (sinzui) wrote :

Something is converting the <li class="first"> into an bogus anchor like <a class="first js-action inactive" href="#">.

Revision history for this message
Curtis Hovey (sinzui) wrote :

The navigator in buglisting.js assumes all nodes with the "first" class are navigator nodes. "First" is also a YUI grids class for setting the order of nodes. Since the initial load the bug-listing page is the first page, the navigator want to disable the first link, but it also disables converts all first nodes into anchors and disabled them too.

tags: added: bug-columns
Curtis Hovey (sinzui)
description: updated
Revision history for this message
Richard Harding (rharding) wrote :

This looks like it might be

module.linkify_navigation #523 in the listing_navigator.js and should be fixable by adding an ancestor to the Y.all() For example:

#bugs-table-listing .(first, last, prev, next)

Revision history for this message
Michael Moroni (airon90) wrote :

Strange, it works for me

Changed in launchpad:
assignee: nobody → Richard Harding (rharding)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Ian Booth (wallyworld) wrote :

I marked this as qa-ok but set back to In Progress since for some reason it doesn't fix qastaging but seems to work ok in dev

tags: added: qa-ok
removed: qa-needstesting
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Curtis Hovey (sinzui) wrote :

Something is still messing the with <li> of the first link in the column. The js-action and inactive class are being added to code that is not related to js.

tags: removed: qa-ok
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.