Closed Bug 330251 Opened 14 years ago Closed Last year

Let DOM Inspector take external viewers

Categories

(Other Applications :: DOM Inspector, enhancement)

enhancement
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: allan, Unassigned)

Details

Right now DOM Inspector only supports its own viewers. It would be nice to support external viewers for custom content. SVG, MathML, XForms, whatever...

As far as I can see, to support it ViewerRegistry.js "just" needs to fixes:
1) Check for absolute URLs for viewers and load them from there instead of assuming "chrome://inspector/content/viewers/" + uri.

2) Figure out a mechanism for extending the viewer-registry.rdf, to let the external views to register themselves.

I do not know a lot about rdf, so I'm sure how to do 2) smartest...
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
Assignee: nobody → Sevenspade
Unassigning.  I decided to just start on DOMi 3 instead.  This will be possible there from the start.
Assignee: Sevenspade → nobody
(In reply to Colby Russell :crussell from comment #1)
> Unassigning.  I decided to just start on DOMi 3 instead.  This will be
> possible there from the start.

curious will it inherit all a11y stuff the DOMi has?
No.  It's inheriting nothing, since the interfaces between all the parts are different.  I did think about the possibility yesterday of having a compatibility layer.  I may or may not do that.

I'll bring up this topic at the next SeaMonkey status meeting (June 11) to see what the general feeling is with Neil and other SeaMonkeyers.  Sometime before then, I'll file a proper meta bug regarding the idea of DOMi 3 and update w.m.o wrt sepsis-inspector.  <https://wiki.mozilla.org/Sepsis#Inspector>
Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → INCOMPLETE
Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
You need to log in before you can comment on or make changes to this bug.