RFE: Display source XML when no stylesheet is available for an XML document

VERIFIED FIXED in M11

Status

()

Core
XML
P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: Roland Mainz, Assigned: Nisheeth Ranjan)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Both apprunner and viewer are NOT able to view plane XML (e.g. XML not
assicioated with a CSS etc.).
Today I've heared the xxxx-time that the most advantage of IE 5 during XML
application development is this feature (e.g. view plane XML structured and
colored)...

No more comment... Simply DO IT (please) quickly !!!!

Updated

19 years ago
Assignee: don → nisheeth
Component: Apprunner → XML
QA Contact: 3853 → 3849
(Assignee)

Comment 1

19 years ago
This is actually a feature request.  Marking as such.  CCing Vidur for comments.
Status: NEW → ASSIGNED
Summary: Apprunner/viewer does not display plane XML !!! → RFE: Display source XML when no stylesheet is available for an XML document

Comment 2

19 years ago
A good idea. Should be simple to do. CCing RickG.
(Reporter)

Comment 3

19 years ago
Did someone wrote the feature request, or would this be my work ?

----

I'd like to make a XML workshop including XUL etc. in three weeks.
Is it possible that someone has implemented this feature in that time ?
(Assignee)

Comment 4

19 years ago
Setting target milestone to M7 for now...
(Assignee)

Updated

19 years ago
Target Milestone: M7
(Assignee)

Updated

19 years ago
Target Milestone: M7 → M9
(Assignee)

Comment 5

19 years ago
Moving out to M9...
(Reporter)

Comment 6

19 years ago
Sorry for the following flame, but...
...WHY moving this feature from one milestone to a higher one each time it
reaches it's target milestone ?
You are LOOSING developers (which are currently much more important than future
customers) !!

----

Please try a simple solution first, single-node hiding/unhiding can be
implemented later by someone else (maybe by me if you give me a stone to build
my house on...)
A question:  what defines no stylesheet being available?  With namespaces, the
UA may have some knowledge (in the form of a UA stylesheet) about how to display
parts of the document, or maybe even all of it.  What says that it should go
into a source view instead?  (The UA stylesheet could even be changed by the
user or by a third party upgrade to recognize something you don't yet know it
will recognize.)

I tend to think something like this would be better off as an extension of
view-source.  Right now XML with no stylesheet is displayed as the CSS spec
describes.  In the interests of extensibility this may be a good thing.
(Reporter)

Comment 8

19 years ago
MicroOffs's IE5 displays XML documents without stylesheets in a tree view; each
tree node representsa XML/DOM tree node.
The request here is to make something simmilar. Add a menu boolean item which
enabled/disabled this feature. But simply ADD this ASAP because this is a very
usefull feature. In fact, this is (mainly) the ONLY reason we installed IE5 on
our PC boxes - simple handling of XML documents/data.
Doesn't alecf's DOM viewer do this?  ("DOM Viewer" on n.p.m.rdf and
n.p.m.xpfe).  It's not by default on a page w/o a stylesheet, but if the spec
says it shouldn't and the functionality is there at your choice, this might be
the way to go.

I think he said it only works for XUL and HTML at the moment, but I guess that
could be changed.  Then, all that is needed is to hook it up onto the menu.
(Assignee)

Comment 10

19 years ago
Alec, please tell us more about this "DOM viewer" mentioned by matty in
his earlier post.  Thanks.

Comment 11

19 years ago
Sorry for the delay - I was on vacation. Anyway, I put the dom viewer in
mozilla/rdf/tests/domds - it consists of a datasource which you point at a DOM,
and some XUL which points a tree at the DOMDS...

when waterson adds RDF resource factories again, then I have a less
memory-intensive way of doing the viewer.
(Reporter)

Comment 12

19 years ago
Can you add a menu item for the DOM viewer, please (e.g. below the "View
Source..." menu item ?

Comment 13

19 years ago
The dom viewer is by no means a scheduled feature, it was more of a fun hack I
was hoping someone might like to use and extend.
If the editor or layout teams want to pick up some of the slack (like adding it
to the windows/mac build) I'm more than willing to pitch in a whole bunch of my
time to improving this thing.
(Reporter)

Comment 14

19 years ago
The DOM viewer would be a great feature for all people which do some XML
development...
Please make it a scheduled feature !
(Assignee)

Updated

19 years ago
Severity: critical → normal
Target Milestone: M9 → M11
(Assignee)

Comment 15

19 years ago
Alec, lets work together during M10 to get the DOM viewer callable from an
apprunner menu item.  I can help you with enabling the DOM viewer on windows and
mac.  I've opened bug 11369 to track that effort and assigned it to you.  I'm
moving this bug to M11.

Comment 16

19 years ago
ok, great!
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 17

19 years ago
Alecf has checked in the DOM viewer, so I'm marking this bug fixed.
(Reporter)

Comment 18

19 years ago
We are still missing a prefs-option which switches from correct CSS behaviour
(blank page if no stylesheet) to
- view source (colored)
OR
- start DOM tree viewer

e.g.
a three-choice widget:
Title: View XML documents without stylesheet
- as is (e.g. blank page) *default
- as DOM tree
- as source

Should I file a RFE for this ?
(Assignee)

Comment 19

19 years ago
Yes, please file a separate bug for that and assign it to me.

Updated

19 years ago
QA Contact: beppe → chrisd

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 20

19 years ago
Based on 9/22 comments from reporter and the fact that he will write new bug up
for remaining issues, verifying this bug fixed.
(Reporter)

Comment 21

19 years ago
As far as I can remeber I filed this bug, right !?
You need to log in before you can comment on or make changes to this bug.