GNOME Bugzilla – Bug 773354
"name" attribute of image map not urlencoded, not working in Chrome
Last modified: 2016-12-29 18:45:40 UTC
I have some class hierarchy in PHP, with namespaces. Generated inheritance diagrams link to particular classes in FF 23 and IE 10 but not in newest Chrome. Part of HTML source: Inheritance diagram for my\name\space\interface:</div> <div class="dyncontent"> <div class="center"> <img src="interface_my_1_1_name_1_1_space_1_1_interface.png" usemap="#my_5Cname_5Cspace_5Cinterface_map" alt=""/> <map id="my_5Cname_5Cspace_5Cinterface_map" name="my\name\space\interface_map"> When I made the "name" attribute identical to "id", classes became clickable on the image.
- Did the changed version also work under the newest FF (as far as I know 49, 23 seems quite old already) and IE 10? - What happens when you replace the backslash characters (\) by forwards slashes (/) with all 3 mentioned browsers? Can you please attach a (small) self-contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
Created attachment 338278 [details] a minimal bunch of *.php files and the Doxyfile According to http://stackoverflow.com/questions/5527290/image-map-support-in-firefox-chrome-and-other-browsers , Chrome uses the "name" attribute while others use "id". Ergo, attributes should be identical. If I copy "id" to "name" (both become urlencoded), then the map is clickable in FF 49 and 23, IE 10 and 8, Chrome 54. No idea why you need to keep slashes in "name". If I copy "name" to "id" (both contain slashes), convert backslashes to forward slashes and update the corresponding "usemap" attribute, then links work in all browsers above. Without the conversion Chrome still ignores the map. Also my favorite text editor highlights any kind of slashes in "id" as invalid characters. Looks like they are allowed only in HTML5-compliant source (http://xahlee.info/js/html_allowed_chars_in_attribute.html).
Confirmed. Should be fixed in the next GIT update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.13. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant (preferably in the form of a self-contained example).