Hmm... I need to find out myself. I don't know what is the answer to your question. I'll do some Googling and get back to you if I find an useful answer. You should email the people at iPage as they probably can help you..
I know I should wait more than just a day, but... oh well lol - i've helped about 7 people, 5 of them with detailed explanations/sample pages on my site,.
.... but I haven't gotten much help back..
I am by no means an expert on the subject of XHTML, but I'm trying to learn it. If I correctly understand what I read, the "usemap" attribute should directly reference an id, which is what IDREF stands for. If you look at.
The definition of IDREF in the XML 1.0 Recommendation.
You'll see that the IDREF value should be identical to the "id" value, which means no "#". So give that a try. I would be interested to know what browsers support this, though..
I hope you stick around and continue helping people. You give very good answers. Your question was quite a bit more advanced than a majority of the questions I see on this board...
Thankyou very much for your compliments, and for helping (or at least trying to help) me. I will go test if that works right now, it sounds formidable...
No luck. Thanks anyways.
I wonder how W3 is hoping to achieve backwards compatibility with this revision... every other tag is baskward compatible in some way. Something's not right here: there has to be an easy method to using image maps. At current status, I can't use <map> at all unless I use XHTML 1.0! Many others have complained and requested help in ther forums. I have seen a few solutions... dealing with DTD modulation that looks like this:.
However, this is what I see:.
It is way too complicated. I have a habit of not using things that I cannot decipher. As I said before, that whole DTD is foreign to me..
Nonetheless, I'll try the above right now, and report back in a moment what I get...
DEFINITELY DO NOT USE.
Caused 4 more errors than I needed pfft.
I've read more forums online, people are all staying with xhtml 1.0 ... if we don't find a good explanation for this, maybe we should start a petition or something and revert usemap back the way it used to be.
I mean, their still on their working drafts for 2.0, so maybe we can help some lives (like me).
Well whatever, I give up for now..
I have been doing a bit of digging and it seems that the change to IDREF broke a lot of browsers..
This decision is currently under consideration.
If you would rather not change the module yourself so that the map works all the time, then your best bet is to stick with XHTML 1.0 until the issue is resolved. As for XHTML 2.0, there will be absolutely no backwards compatability in that, so it will be interesting to see how that is accepted by the community...
Thanks for the update, doogxela i'll keep that in mind. i'll post any solutions I find on this forum as a new topic "XHTML 1.1 IDREF" (if I can get any)..