Modify ↓
Opened 18 years ago
Closed 18 years ago
#5371 closed defect (duplicate)
Failure to browse file - XML signature?
| Reported by: | anonymous | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control/browser | Version: | 0.10.4 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Works: http://trac.arantius.com/browser/extension/resurrect/content/resurrect.js?rev=109
Broken: http://trac.arantius.com/browser/extension/resurrect/content/resurrect.js?rev=110
Diff: http://trac.arantius.com/changeset/110
The file browser appears to break when, it seems, there's an XML signature in the source file?
Trace:
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "/usr/lib64/python2.4/site-packages/trac/web/main.py", line 244, in dispatch
req.display(template, content_type or 'text/html')
File "/usr/lib64/python2.4/site-packages/trac/web/api.py", line 358, in display
data = self.hdf.render(template, form_token)
File "/usr/lib64/python2.4/site-packages/trac/web/clearsilver.py", line 296, in render
injector.feed(template.render())
File "/usr/lib64/python2.4/HTMLParser.py", line 108, in feed
self.goahead(0)
File "/usr/lib64/python2.4/HTMLParser.py", line 148, in goahead
k = self.parse_starttag(i)
File "/usr/lib64/python2.4/HTMLParser.py", line 226, in parse_starttag
endpos = self.check_for_whole_start_tag(i)
File "/usr/lib64/python2.4/HTMLParser.py", line 301, in check_for_whole_start_tag
self.error("malformed start tag")
File "/usr/lib64/python2.4/HTMLParser.py", line 115, in error
raise HTMLParseError(message, self.getpos())
HTMLParseError: malformed start tag, at line 347, column 883
Attachments (0)
Note:
See TracTickets
for help on using tickets.



This is a known defect of 0.10, it can't cope with malformed HTML produced by content renderers and/or macros.
See e.g. #4365.
(we won't fix it for 0.10, but 0.11 doesn't suffer from this problem)