bug page html is unparseable by XMLHttpRequest

Bug #918901 reported by James Ferguson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Ian Booth

Bug Description

Browser: chromium 16.0.912.75 and Firefox 9.0.1

This is a newly introduced bug in the bug page HTML, e.g.: https://bugs.launchpad.net/jockey/+bug/293399

Using greasemonkey scripts (from the bug search results page) which fetch a bug page via XMLHttpRequest, they get a responseXML which is null, (I think) because it's no longer parseable as XML. The bug page HTML has changed recently.

This is a problem which has happened (and been resolved) before, so I think some LP people are familiar with it?

To really see the problem, I'll attach a sample GM script which can be loaded into Chromium or Firefox, and then if you load a bug listing page like https://bugs.launchpad.net/jockey, the script will fail (unpopulated fields, javascript errors "142Uncaught TypeError: Cannot read property 'documentElement' of null")

Thanks

Related branches

Ian Booth (wallyworld)
Changed in launchpad:
status: New → In Progress
importance: Undecided → Critical
tags: added: javascript regression
Changed in launchpad:
assignee: nobody → Ian Booth (wallyworld)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
Ian Booth (wallyworld)
Changed in launchpad:
status: In Progress → 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.