Closed Bug 437033 Opened 16 years ago Closed 6 years ago

Redirect necessary CSS for source views through x-jsd instead of opening up all of venkman for content

Categories

(Other Applications Graveyard :: Venkman JS Debugger, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: Gijs, Assigned: rginda)

References

Details

As in summary. Spinoff from bug 428848, please see discussion there.

--> Future, as there's nobody to work on this. Please feel free to take and appropriately adjust target milestone.
To say it another way:
*you want to make the x-jsd protocol able to load css files.
*you don't want a solution as in bug 428996 for example.

Is that it ?
(In reply to comment #1)
> To say it another way:
> *you want to make the x-jsd protocol able to load css files.
> *you don't want a solution as in bug 428996 for example.
> 
> Is that it ?
> 

Well, a solution like in bug 428996 is not straightforwardly possible here.

To my knowledge contents.rdf files cannot do chrome registry overrides. So, suppose we would apply the same fix, then in SeaMonkey trunk and Firefox 1.5, 2 and 3, we would have a working Venkman.

However, in current stable SeaMonkey (and older Firefox versions) we would not have a "venkmanbody" package, or, if we managed to do that, it would not have any content (because we can't override anything) - unless we actually added a bunch of directories and contents.rdf files, or ship the CSS file twice using jar.mn, all of which sucks quite a lot. The alternative would be adding the CSS at runtime, and picking the right URL there, which is also involved (how do we properly detect what will work?) and makes the whole solution kind of stink. So, it is not as easy as the patch in bug 428996, at all.

If someone is willing to go through that mess and properly test it, I won't at this point rule out taking a patch. But I don't have the time to pursue anything myself, I'm in the middle of a thesis project. Both of these solutions are non-trivial, as far as I can tell.
Component is obsolete so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.