bozz:
Do you have a security error in the Error Console like I have (see my post on the previous page)?
Do you see the image rule in the DOM Inspector (CSS Style Rules)?
"Doesn't the idea of making nature against the law seem to you a bit... unnatural ?" - Bill Hicks "Money is the Schrodinger's Cat of economics." - Robert Anton Wilson "It's not a bug, it's two features having a fight in the pub car-park." - Me
My problem is not the path: if I put the path I see in the Error Console in the url bar then the image displays fine.
It is a security (CAPS) problem as I wrote:
Security Error: Content at about:blank may not load or link to ...
Try uploading the image to <a href="http://software.hixie.ch/utilities/cgi/data/data">this page</a> and use the code it gives you, instead of the path to the image.
It is a background image meant for the browser window and thus can be quite large and converting it to base64 makes it even larger.
Isn't it possible to put a pref (capability.policy) in user.js to allow access to that image?
The reason I have my code working, without the above pref set, is that I use NoScript which has a "Allow Local Links" option. The CAPS pref above works on my Minefield build which doesn't have NoScript installed.
[edit] Check out my post below for a better set of prefs
Last edited by RaiseMachine on March 26th, 2007, 2:47 am, edited 2 times in total.
"Doesn't the idea of making nature against the law seem to you a bit... unnatural ?" - Bill Hicks "Money is the Schrodinger's Cat of economics." - Robert Anton Wilson "It's not a bug, it's two features having a fight in the pub car-park." - Me
Your first pref is allowing all sites to load local content. Your second pref isn't doing anything. The sites preference value needs URLs of the sites allowed to access local content, not the content itself. Also, default policies do not use sites preference:
The Default Security Policy
The syntax is exactly the same as if you were using one of your own named policies, except it doesn't need a "capability.policy.default.sites" preference.
you could simply download a theme that's already skinned as I have and edit the bitmaps with that. if you're really interested, look at its coding and see how it does it. i, myself, don't believe i've ever honestly coded anything, but i can edit photo's with the best of them.
if you open the jar with winzip, you can extract the global file and edit the background images located within as I have (but you probably already knew that...)
here's a screenie of my skin i made doing just that:
good luck!
^Not what the OP is asking for. This relates to changing the background for blank (about:blank) pages.
Anonymous wrote:Your first pref is allowing all sites to load local content. Your second pref isn't doing anything. The sites preference value needs URLs of the sites allowed to access local content, not the content itself. Also, default policies do not use sites preference:
The Default Security Policy
The syntax is exactly the same as if you were using one of your own named policies, except it doesn't need a "capability.policy.default.sites" preference.
"Doesn't the idea of making nature against the law seem to you a bit... unnatural ?" - Bill Hicks "Money is the Schrodinger's Cat of economics." - Robert Anton Wilson "It's not a bug, it's two features having a fight in the pub car-park." - Me
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.