Neil <[EMAIL PROTECTED]> schrieb in im Newsbeitrag:
[EMAIL PROTECTED]
> Martin Kutschker wrote
>
> >I am writing a little app and I have created specific CSS for different
Mozilla skin. For now I did modern and classic. Styling works nicely for
these two skin as I know in advance which colours look fine with them. But
if the user chooses any other skin eg the ones from NS6 themeing contest,
then he or she runs into the problem that Mozilla chooses what seems to be
the default skin for Communicator. So the UI "breaks" (ugly colours and
stuff).
> >
> >So I'd like to create a "save skin" for my app, which doesn't set colours
and fonts etc.. This "save skin" shall be used as the "default skin" if the
user chooses a skin for Mozilla for which no skinning is done for my app. Is
there a way to do this?
> >
> You can install a skin that only applies to your package.
I have tried that. But there is an UI issue that Mozilla presents this skin
to the user as selectable for Communcator. Perhaps there is already some way
to prohibit this in contents.rdf of the skin. If not I'd guess some
attribute "private" or "communicator" (defaulting to true) is all that's
needed.
> You still have to contend with the global and/or communicator skins,
should you wish to
> use them.
Huh? Do we understand each other? I have created extra stuff for my app that
goes nicely with the shipped skins (have a look at the memory buttons of
mozCalc: http://mozcalc.mozdev.org - old XUL syntax!). This works really
fine. The problem is when the user switches to another skin (eg Golf,
Mozillium, whatever). In this case Mozilla applies the user selected skin
AND some random/default skin of my package to the app! It would be better
not using any skin CSS at all, than using the wrong one (again, look at
mozcalc).
So If I could create a specific "default skin" that's only applied if there
is no package specific skin matching the Mozilla skin this would be great.
Masi
PS: Shall I file a RFE?
