Elements are not closed on bug page source

Bug #728609 reported by James Ferguson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Unassigned
lazr.restful
Fix Released
Critical
Unassigned

Bug Description

As of 2011-03-02, the bug page source has unclosed elements. The xhtml in the json is not escaped.

Any bug page is a good example. e.g. https://bugs.launchpad.net/linux/+bug/651785

This is a significant new issue because some browser user scripts fetch bug pages using XMLHttpRequest objects and then make use of the .responseXML member. This member is now null, presumably because the bug pages cannot be parsed as XML. Formerly working script is attached to this bug (comment #2)

These user scripts are an integral part of our process in the OEM Mainstream systems team, so this is a very important issue for us. Workarounds would include either allowing the user selection of columns in bug searches, or help developing user scripts which use the Launchpad API rather than doing full bug page gets and extracting data from them...

Thanks.

Related branches

Steve Magoun (smagoun)
tags: added: oem-services
Revision history for this message
Robert Collins (lifeless) wrote :

Escalated via stakeholders list.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
tags: added: escalated
Revision history for this message
James Ferguson (jamesf) wrote :

This script worked on 2011-03-01 (unless I'm mistaken and it was the day before)

If someone knowledgeable can show me how to use the API in such a script instead, that would be great too.

description: updated
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
Revision history for this message
Curtis Hovey (sinzui) wrote :

The project is the xhtml in the javascript. All angle-brackets and ampersands must be escaped in attributes and script blocks. We can try to place the scripts in <![CDATA[...]]> which kills the TAL engine or address bug 684430.

The link elements in the head are fine. I believe you save the page from your browser. Firefox and Chromium rewrite empty tags to make them suck.

description: updated
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 728609] Re: Elements are not closed on bug page source

On Fri, Mar 4, 2011 at 10:09 AM, Curtis Hovey
<email address hidden> wrote:
> The project is the xhtml in the javascript. All angle-brackets and
> ampersands must be escaped in attributes and script blocks. We can try
> to place the scripts in <![CDATA[...]]> which kills the TAL engine or
> address bug 684430.

the xhtml is new, lets drop it.

Curtis Hovey (sinzui)
Changed in launchpad:
status: Triaged → In Progress
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: none → 11.03
Revision history for this message
Curtis Hovey (sinzui) wrote :

This is fixed in lazr.restful 0.17.3. We need a new egg to release this fix.

Changed in launchpad:
status: In Progress → Fix Committed
Changed in lazr.restful:
status: New → Fix Committed
Changed in launchpad:
status: Fix Committed → In Progress
Changed in lazr.restful:
assignee: nobody → Curtis Hovey (sinzui)
importance: Undecided → Critical
Revision history for this message
Robert Collins (lifeless) wrote :

I've updated the metadata to reflect the two projects involved here.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad:
status: In Progress → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
Changed in lazr.restful:
milestone: none → 0.17.4
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
James Ferguson (jamesf) wrote :

Perhaps this is what I get for trying to report a bug with some analysis. The bug from my (user) perspective is that user (greasemonkey) scripts can no longer be used to fetch LP bug pages via XMLHttpRequest, and that bug remains. The bug page is not parseable so the DOM object is null and can't be used.

Changed in launchpad:
status: Fix Released → Fix Committed
Changed in lazr.restful:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: 11.03 → 11.04
Revision history for this message
James Ferguson (jamesf) wrote :

Ignore comment #8. The issue is fixed, but I was mislead by a mistake in the bug status, expecting it to be visible in LP. The issue is fixed in qastaging.launchpad.net.

Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: Curtis Hovey (sinzui) → nobody
Changed in lazr.restful:
assignee: Curtis Hovey (sinzui) → nobody
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.