Open Bug 284238 Opened 20 years ago Updated 3 years ago

map a:hover fails (in the image as well as in displayed links

Categories

(Core :: Layout, defect)

x86
Windows 2000
defect

Tracking

()

People

(Reporter: mail, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1 When moving the mouse pointer over the link or the appropriate area of the img, the link text should be red but stays blue (other properties do not react as well, color is just an example in the code provided) map a { color:blue; } map a:hover { color:red; } with <map name="foobar"><p><a href="#" shape="rect" coords="0,0,50,50">foo</a></p></map> <img src="bar.png" alt="map" usemap="#foobar"> Reproducible: Always Steps to Reproduce: 1. use code given above 2a. move mouse pointer over link text 2b. move mouse pointer over image area Actual Results: no change in display (color) apart from link url is shown in status bar Expected Results: change the color resp. change properties as given in CSS (and show link url in status bar) Happens in Firefox 1.0.1 and Mozilla 1.7.3 Opera 7.53 behaves correctly. Internet Explorer 6.0 reacts when hovering the text link but completely fails to recognize the image map areas if given as a elements.
Not a CSS issue. The <a> is not inside the <map> when you look at the DOM, because the parser only allows <area> inside <map>. Over to parser, but this may end up being wontfix depending on how many sites fixing it would break...
Assignee: dbaron → parser
Component: Style System (CSS) → HTML: Parser
QA Contact: ian → mrbkap
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Reopening. This needs a real call. What does IE do with this markup?
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Keywords: testcase
Attached file Testcase
What happens in IE 6 is basically what comment 0 says, the link turns red when hovering, but the image map fails
The question was what DOM IE produces.
(In reply to comment #6) > The question was what DOM IE produces. > <HTML><HEAD><TITLE></TITLE> <STYLE type=text/css> map a { color:blue; } map a:hover { color:red; } </STYLE> </HEAD> <BODY><MAP name=foobar> <P><A href="http://www.mozilla.org" shape=rect coords=0,0,50,50>foo</A></P></MAP><IMG alt=map src="http://www.mozilla.org/images/ff_shirt.jpg" useMap=#foobar></BODY></HTML>
So the parentNode of the <p> is the <map> in IE's DOM?
Yes, correct (also double-checked with IE:s Dev. Toolbar)
In that case we should think about allowing random stuff inside <map>...
Status: UNCONFIRMED → NEW
Ever confirmed: true
The parser seems to be doing the right thing now (the document structure looks right), sending this over to layout.
Assignee: parser → nobody
Component: HTML: Parser → Layout
QA Contact: mrbkap → layout
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: