Last modified: 2008-12-19 07:03:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T18471, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16471 - conflicting usemaps if MediaWiki:Sitenotice uses <imagemap> as well
conflicting usemaps if MediaWiki:Sitenotice uses <imagemap> as well
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ImageMap (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-27 05:44 UTC by S Page
Modified: 2008-12-19 07:03 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description S Page 2008-11-27 05:44:20 UTC
If your MediaWiki:Sitenotice uses <imagemap> and then you use <imagemap> on a page, in the generated HTML both get assigned usemap="#ImageMap_1" and so (in Firefox 3.1 at least) the same imagemap applies to both images.

If both imagemaps are in the body, the generated HTML correctly gives the second one usemap="#ImageMap_2". I guess the different contexts of the two fragments lead to the overlap.  Looking at the code there's no way to override the 
  $mapName = "ImageMap_" . ++self::$id; 
assignment.

You can temporarily see this at http://wiki.laptop.org/go/Upgrading_the_XO (until we fix the Sitenotice to use alternative HTML+CSS. ;-)
Comment 1 Tim Starling 2008-12-19 07:03:37 UTC
Fixed in r44794.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links