<area> elements are not display:none
Reported by
bzbar...@mit.edu,
Feb 7 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0 Steps to reproduce the problem: 1. Load data:text/html,<map><area></map> 2. Examine the <area> element in the inspector. What is the expected behavior? It's display:none. What went wrong? It's display:inline. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 58.0.3000.4 (Official Build) dev (64-bit) Channel: n/a OS Version: OS X 10.12 Flash Version: https://html.spec.whatwg.org/multipage/rendering.html#hidden-elements is pretty clear: <area> is display:none by default.
,
Feb 9 2017
I am able to repro the issue on the latest canary(58.0.3006.0) on Windows-10, Mac OS 10.12.2 and Linux Ubuntu 14.04. Same behavior is seen on older chrome version as well. Not sure about the correct behavior here,hence marking this Untriaged for more inputs on this.
,
Feb 9 2017
,
Feb 9 2017
,
Feb 10 2017
Can reproduce this issue as well on MacOS 10.12.3 on Chrome 56.0.2924.87. As mentioned, the spec seems pretty clear that 'display:none' should be applied by default.
Worth noticing both Firefox Stable 51.0.1 and Firefox Nightly 53.0a1 set 'display:none' by default to <area>.
The problem is due to html.css setting the styles as :
area {
display: inline;
cursor: pointer;
}
,
Feb 21 2017
The <area> used to be a "display: none" tag before 2014 and it was changed to "display: inline" to fix bug 392759 . For more information, see: https://codereview.chromium.org/442563002#msg12 So what should we do next? Change it back and use nonRendererStyle() or keep it as-is?
,
Feb 22 2017
Per spec, getComputedStyle for <area> should act like it does for any other display:none element, note.
,
Oct 30 2017
I see this is marked as a good first bug, I'd love to get involved. Is there anyone available to mentor me through my first contribution?
,
Oct 30
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 5
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nyerramilli@chromium.org
, Feb 7 2017