Hi,
I have a menu in my site that I use class ID for each link with different
menu button. It was validated until I added body#ID for persistent page
indicator.
Before persisten page indicator:
<.li>
After page indicator:
<.li id="home">
If I remove the ID in the a href, my button disappear
You cannot reuse IDs within a document. Each ID must have a unique value.
Have a look at
http://www.456bereastreet.com/archive/200503/setting_the_current_menu_state_with_css/
It has a good example of what you are trying to achieve.
Regards,
Jachin Sheehy
Senior Web Developer
InternetFiji.com
On
Hi Tee,
ID should be unique. That's it. Change IDs to be diferent or use classes instead
On Apr 5, 2005 12:37 PM, tee <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a menu in my site that I use class ID for each link with different
> menu button. It was validated until I added body#ID for persistent
It looks like you're defining the same element twice, but in a different
way and with a different background image. To me this makes sense why
this would conflict.
#siteOption li a#home { background: url(images/h_gb.gif) no-repeat; }
vs.
body#homepage li#home a { background: url(images/hhover
> It looks like you're defining the same element twice, but in a different
> way and with a different background image. To me this makes sense why
> this would conflict.
There are 8 buttons in the menu and each button with unique ID because each
button is different.
> #siteOption li a#home { bac
At 07:37 PM 4/4/2005, tee wrote:
I have a menu in my site that I use class ID for each link with different
menu button. It was validated until I added body#ID for persistent page
indicator.
Before persisten page indicator:
<.li>
After page indicator:
<.li id="home">
If I remove the ID in the a hr
tee,
your english is great. even those of us that grew up on the language
abuse it with regularity.
my only confusion comes from perhaps the 'persistent page indicator'.
i'm not sure how this second definition is only triggered when a user
visits the home page...irregardless, when the page load
Thank you everyone! The conflict solved after I change it to class.
> your english is great. even those of us that grew up on the language
> abuse it with regularity.
Diona, I was just being lame ;) Once I get myself comfortable in this list,
I probably will make no apology for my English lol.
>
: 150px;
}
What/where exactly should I change the id to class from above three?
tee
> From: diona kidd <[EMAIL PROTECTED]>
> Reply-To: wsg@webstandardsgroup.org
> Date: Mon, 04 Apr 2005 23:38:09 -0400
> To: wsg@webstandardsgroup.org
> Subject: Re: [WSG] ID conflicts
>
&g
tee wrote:
This is the page I'd working on now. The body and the menu buttons are in id
so it works but doesn't pass the validation of course.
http://www.lotusseeds.com/big5.htm
<.div id="siteOption">
Hi,
The problem is the still the same, but perhaps you missed the answers
ear
Hi Michael and Martin. Thanks for the reply.
A quick note first before I go playing with my code again.
> The problem is the still the same, but perhaps you missed the answers
> earlier.
>
> You can only use id="home" once on any page--one time and one time
> only--and never twice on the same pag
tee wrote:
Yes, I fully aware that ID can only apply one and one ONLY :)
I have to say I didn¹t' think ahead when making the menu. Having the button
set to ID was fine and passed the flying colors with validator. The issue
arise once I decided to have the 'current page' indicator. I did try to
chan
> Hi,
>
> Then why are you still using the same id for both your 's and your
> 's in #siteOption ul? If you know this is a no no, then the first
> thing you should do is fix it. You don't *have* to use a class and in
> this case a class makes less sense (to me at least) than a unique id.
>
Well!
tee wrote:
Yes Sir!
And thanks million for the fix. Came up a quick copy and paste test page. It
works beautifully. Will study your code thoroughly lately tonight to make
sure I understand everything.
http://www.lotusseeds.com/tryagain_michael.html
Looks nice,
Maybe you've already thought of this,
Tee,
Am Dienstag, 5. April 2005 um 15:47:49 haben Sie geschrieben:
t> This is the page I'd working on now. The body and the menu buttons are in id
t> so it works but doesn't pass the validation of course.
t> http://www.lotusseeds.com/big5.htm
t> <.div id="siteOption">
t>
t>>
t>
> Maybe you've already thought of this, but the list is useless without
> css support. I'd suggest putting list item name in the list
> items and then do something like
>
> |li a span {display:none}|
>
Thanks for the reminder. I did not think about this at all.
In IE, this doesn't seem to be a s
tee wrote:
For example:
The first button link:
#siteOption #homeLink {
background: url(images/bigmenu/big5_home.jpg) no-repeat;
height: 28px; width: 150px;
}
And the span has to be here so that it work in IE but creates 2 pixel white
space.
#siteOption #homeLink span {display: none; }
For
17 matches
Mail list logo
