Closed
Bug 252217
Opened 21 years ago
Closed 21 years ago
XML Pretty Printing is Broken, and doesn't happen. Mozilla 1.7.1 Debian/1.7.1-1
Categories
(Core :: XML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: acanon, Assigned: hjtoi-bugzilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.1) Gecko/20040715 Debian/1.7.1-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.1) Gecko/20040715 Debian/1.7.1-1
The Pretty Printing of XML files is broken. It works when I regress to Mozilla
1.6, but doesn't work in 1.7.1,
Here's a sample XML file my non working, non XML rendering Mozilla browser can't
render, when it tries to render it. I'll see if I can upload it as an attachment.
<?xml version="1.0" ?>
<yaya>
<smallberries>
Many Jars
</smallberries>
</yaya>
Reproducible: Always
Steps to Reproduce:
1. Make an xml file.
2. Browse it with Mozilla 1.7.1, either locally or through a web server, with
either application/xml or text/xml mime types. (Tried AddType text/xml in apache
just to see if it was a mime type problem: it isn't.)
3. See no nice pretty-printing tree view.
Actual Results:
The browser canvas is blank. I can see the XML source if I View Source. But
there is no nice tree view of the XML as there was with Mozilla 1.6. I removed
Mozilla 1.7.1 and downgraded to 1.6, with the result that Mozilla 1.6 could
render the tree view of the file just fine. All this under Debian Sid 20-Jul-2004.
Expected Results:
When opening an XML file, either locally or through http: (to the localhost),
Mozilla ordinarily displays the XML file as a tree-structured widget, giving the
user the ability to expand and collapse branches of the tree representing the
XML document.
| Reporter | ||
Comment 1•21 years ago
|
||
I did not find this problem under Win2K with the following build:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707
However, returning to Linux where original problem manifested, I downloaded the
debian source packages and compiled them like the following, and still couldn't
browse XML files in a tree view:
apt-get --compile source mozilla
dpkg -i *.deb
The Debian Unstable package for mozilla-firefox also appears to have this
problem (not rendering XML in treeview.)
Comment 2•21 years ago
|
||
Is this a problem with mozilla.org builds? The debian builds have a rather
large number of patches applied to them, and usually one or two things get
broken by those patches...
| Reporter | ||
Comment 3•21 years ago
|
||
(In reply to comment #2)
> Is this a problem with mozilla.org builds? The debian builds have a rather
> large number of patches applied to them, and usually one or two things get
> broken by those patches...
I guess it's not a problem with the mozilla.org builds. Last night I downloaded
the generic x86 Linux binary installer for Mozilla 1.7 from mozilla.org, instead
of the debian Mozilla 1.7.1 package, and it worked fine (for XML tree rendering,
anyway.)
Then I downloaded/built/installed the source code for Mozilla 1.7.1 from
Mozilla.org, and it, too, worked just fine as far as the XML tree rendering is
concerned.
So, it looks like this is a problem introduced by the Debian patches to the
Debian packages. Should I change the status of this bug to "INVALID," and go
complain to Debian? It sounds as if I may have jumped the gun in registering the
bug with Bugzilla here at Mozilla.org.
| Assignee | ||
Comment 4•21 years ago
|
||
Alan, please file the bug with Debian. I'm closing this as invalid. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 5•21 years ago
|
||
I do not think the problem is Debian specific. I tried with two mozilla.org 1.7
builds:
- with the standard build (no XFT) the XML pretty printing works.
- with the GTK2/XFT/Pango build, XML is not displayed correctly. It seems that
the browser incorrectly thinks a stylesheet is provided, and visualizes one
after the other all the strings in the source file.
The same problem I have with the FireFox 0.9.1 build from mozilla.prg, while
everything was OK with Mozilla 1.6.x and Firefox 0.8.x.
Comment 6•20 years ago
|
||
The problem definitively disappeared in Mozilla 1.7.5
You need to log in
before you can comment on or make changes to this bug.
Description
•