54172 - Chrome registry needs better methods of debugging

Status: RESOLVED FIXED

(Core Graveyard :: RDF, defect, P3)

Description

[Pete Collins (MDG)]

Currently I can get content to register and to run, no probs.
However i can *not* get a stand alone skin to work for an external package.
I haven't seen anyone do this yet. Every other external package uses existing
skins like modern etc . . . AFAICT

Now this wouldn't be such a big deal if there were ways to debug this.

Right now i get a stupid error.

CSSLoaderImpl::DidLoadStyle: Load of URL 'chrome://theme_builder/skin/' failed. 
Error code: 16389

It would be nice to see the real or resource path it is actually trying to load.
I have sliced this six ways till sunday and nothing I do is working!
It looks correct in my all-skins.rdf. I even jared up the skin directory in the
hopes i can get it to work.
No go.

We need more DEBUG printfs here.

*** Chrome Registration of package: Checking for contents.rdf at
resource:/chrome/theme_builder/theme_builder/content/
*** Chrome Registration of skin: Checking for contents.rdf at
jar:resource:/chrome/chameleon.jar!/skin/chameleon/theme_builder/

Is not good enough.

How about some real paths here so i can debug this.

Also is there a way to print out the chrome registry from js or something? (Like
a for in loop)
As to the mappings of where it thinks everything actually is located?

Stuff like this would be timelessly useful.

If anyone has gotten a skin to register and work for an external package w/out
using the existing skins please let me know how you did this.

I am filing a bug on this.

thank you

--pete

Comment 1

[Chris Waterson]

I blame hyatt. hyatt, give it to whoever deserves it most.

Comment 2

[Pete Collins (MDG)]

I have things working again.

But it was PAINFUL!!!!!!!!!!

Did i say it was PAAAAAAAAAIIIIIIIIIIIINNNNNNNNNNNNNFFFFFUUUUUULLLLLL!!!!!!!!!


Yes, PAINFUL indeed.

To get a skin to work:

I had to manually edit "user-skins.rdf" in my mozilla home
default/chrome directory.

I made this change:

  <RDF:Description about="urn:mozilla:package:theme_builder">
    <NS16:selectedSkin
resource="urn:mozilla:skin:theme_builder/:theme_builder"/>
  </RDF:Description>

A am now changing all of the DTD entity paths.

This is a seriously major change!

Man

--pete

Comment 3

[Peter Trudelle]

->future

Comment 4

[David Hyatt]

Eh, it's not going to change any more.

Comment 5

[benc]

Pete's problem sounds fixed, but the debugging issue sounds like it remains 
open.

Comment 6

[benc]

tever is not RDF QA anymore

Comment 7

[Tracy Walker [:tracy]]

mass remove verifyme requests greater than 4 months old