98102 - Percentage coordinates not supported for imagemaps

Status: NEW

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[Peder Stray]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808
BuildID:    2001080814

COORDS="0%,0%,50%,100%" is trated like the % were not there instead of
calculating the real lengths from the image. a imagemap like the one below
should cover the whole image but only coers th upper left block of 100x100 pixels.

<MAP NAME="nav">
  <AREA COORDS="0%,0%,50%,100%" ...>
  <AREA COORDS="50%,0%,100%,100%" ...>
</MAP>

this is fully walid HTML from th 4.01 spec

Reproducible: Always
Steps to Reproduce:
use the imagemap included in the description

Actual Results:  all percentual lengths are treated like pixellengths

Expected Results:  the percentual lengths should get calculated from the size of
the image using the imagemap

Comment 1

[Boris Zbarsky [:bzbarsky]]

Over to layout. Reporter, could you attach a testcase?

Comment 2

[Peder Stray]

added url to testcase

Comment 3

[anthonyd]

not a table specific bug, over to core owner

Comment 4

[Peder Stray]

Still isn't fixed in Mozilla 1.2

Comment 5

[Peder Stray]

Still not fixed in 1.3...

Comment 6

[Peder Stray]

Still not fixed in 1.4 either... and I really would like a browser that managed
to do this...

Comment 7

[Boris Zbarsky [:bzbarsky]]

Yes, we're aware that it's still not fixed; that's why this bug is still open. 
No need to keep reminding... ;)

Comment 8

[Christopher Hoess (gone)]

->Image: Layout

Comment 9

[Boris Zbarsky [:bzbarsky]]

Whoever decides to work on this needs to keep in mind that a rect spec like:

  "10,200,10%,10%"

Is either valid or not depending on the size of the image.  Which means you need
to either stop fixing up broken rect specs, start doing it on every single
click/mousemove, or something....

Comment 10

[Peder Stray]

over 3 years and counting. it this really that hard to fix? Updated the testcase
url.

Comment 11

[Boris Zbarsky [:bzbarsky]]

> it this really that hard to fix?

Yes.  See comment 9, for example.

Also, imagemaps are currently shared by multiple images that reference them. 
Implementing this bug would mean getting rid of imagemap sharing, which would be
a fairly major structural change to that code.

Add to this the fact that this is nearly unused, and there's just not that much
desire to implement it.

Comment 12

[florida_jin]

> Add to this the fact that this is nearly unused, and there's just not that much
> desire to implement it.

Well, of course it isn't used... it can't be used because it's never been
implemented. Just because there aren't currently any pages using it (no doubt
because it isn't supported) doesn't mean there's no demand for it. This lack of
support for standards (HTML 4.01, XHTML) really holds people back from being
able to write versatile web pages that can be accessed from various screen
resolutions or even devices (PDAs and high resolution cell phones come to mind.)
I appreciate the work being done here as much as anyone else, but "it isn't
used" isn't a good reason because any number of features weren't in use before
they were made available.

Comment 14

[ard jonker]

Bug 394124 also related on other tags where percentages are not properly interpreted. So it partly duplicated 98102 but was more extended.

Comment 15

[jag (Peter Annema)]

Attachment: Test with both <img> and <object> and percent and px <area>s.

Comment 16

[[e-mail]]

A solution ?

Comment 17

[[e-mail]]

http://jsfiddle.net/V3XyK/202/ <== Found my solution here

Comment 18

[[e-mail]]

http://jsfiddle.net/V3XyK/203/ <== More expressive

Comment 19

[ard jonker]

@jrgazay: Using percentage coordinates, both the image map and the image itself are shown as percentage width (and height) of parent and everything scales accordingly when the parent scales. The two 'solutions' you give do not address this desired behaviour.
A workaround that serves me well is to drop image maps all together and use .svg instead. SVG has matured sufficiently since 2001 when the percentage bug was first reported.