[css-d] Relative paths for images not working
Hi all,
Having a little problem with image paths.
I want to use:
.header h2 a {
background: url(/library/images/linkArrow.gif) right no-repeat;
}
but this does not work.
But when I use the following below, it does work.
.header h2 a {
background: url(../../library/images/linkArrow.gif) right
no-repeat;
}
What might I be doing wrong here?
My folder structure is: library folder holds css folder and images folder.
Can I use a relative path or just use the dots?
--
Regards
Karl
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Relative paths for images not working
Karl Bedingfield wrote:
Having a little problem with image paths.
[...]
My folder structure is: library folder holds css folder and images
folder.
Since css folder and image folder are in same folder, try the short and
direct...
.header h2 a {
background: url(images/linkArrow.gif) right no-repeat;
}
regards
Georg
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Relative paths for images not working
2010/1/17 Karl Bedingfield k...@bedingfield.biz: background: url(/library/images/linkArrow.gif) right no-repeat; this does not work. But when I use the following below, it does work. background: url(../../library/images/linkArrow.gif) right no-repeat; What might I be doing wrong here? Presumably, the library directory isn't a subdirectory in the root directory for the site. -- David Dorward http://dorward.me.ukhttp://blog.dorward.me.uk __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] table or not to table, was 4 part question about lining up boxes
Thanks for all the replies concerning the previous thread. I have been trying out some of the css from some of the references suggested and having some sucess. What started me thinking though was Georg's last suggestion that this type of information would be suitable for a table if time is tight, which it is. Do others on this list agree that this type of information, ie image logo, name of company and website link is suitable data for a table? I would like to agree because i am more comfortable with the old tables for layout but before it was mentioned i hadn't even thought of it because i was only thinking of presentation and not the actual content. Or should i bash on and find a host of work arounds for ie6 that i must support? Thanks in advance. Lisa __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] table or not to table, was 4 part question about lining up boxes
Lisa Frost wrote: What started me thinking though was Georg's last suggestion that this type of information would be suitable for a table... Thanks in advance. Lisa At this time, with the particular situation at hand, Georg's suggestion might be best for the software, the client, and you. Best, ~d -- desktop http://chelseacreekstudio.com/ mobile http://chelseacreekstudio.mobi/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to spell the letters. Considering CPU (or else) as both an acronym and initialism would allow two different pronunciations. Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
On Sun, 17 Jan 2010, Bob Rosenberg wrote: At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to spell the letters. Considering CPU (or else) as both an acronym and initialism would allow two different pronunciations. Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. You have that backwards. Acronyms are a subset of initialisms; not all initialisms are acronyms. -- Chris F.A. Johnson http://cfajohnson.com === Author: Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress) Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress) __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
I do believe Eric himself shut this conversation down a couple of days ago. It's not in any way related to CSS. Theresa On Jan 17, 2010, at 12:45 PM, Bob Rosenberg wrote: At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to spell the letters. Considering CPU (or else) as both an acronym and initialism would allow two different pronunciations. Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. You have that backwards. Acronyms are a subset of initialisms; not all initialisms are acronyms. That means that Merriam-Webster's Collegiate also has it wrong with their entries of: INITIALISM : an *acronym* formed from initial letters ACRONYM : a word (as NATO, radar, or snafu) formed from the initial letter or letters of each of the successive parts or major parts of a compound term I'm not going to labor the point, but I stick with my original assertion that initialisms are acronyms, but not all acronyms are initialisms. Rob Emenecker @ Hairy Dog Digital www.hairydogdigital.com Please note: Return e-mail messages are only accepted from discussion groups that this e-mail address subscribes to. All other messages are automatically deleted. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
You're right. Sorry. He did. Rob Emenecker @ Hairy Dog Digital www.hairydogdigital.com Please note: Return e-mail messages are only accepted from discussion groups that this e-mail address subscribes to. All other messages are automatically deleted. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
On Sun, 17 Jan 2010, Rob Emenecker wrote: Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. You have that backwards. Acronyms are a subset of initialisms; not all initialisms are acronyms. That means that Merriam-Webster's Collegiate also has it wrong It wouldn't be the first time. with their entries of: INITIALISM : an *acronym* formed from initial letters If that definition is correct, then FBI, RCMP, etc. are not initialism because they are not words. ACRONYM : a word (as NATO, radar, or snafu) formed from the initial letter or letters of each of the successive parts or major parts of a compound term I'm not going to labor the point, but I stick with my original assertion that initialisms are acronyms, but not all acronyms are initialisms. -- Chris F.A. Johnson http://cfajohnson.com === Author: Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress) Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress) __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
