Client-side imagemaps require default shape to be last

RESOLVED INVALID

Status

()

Core
Layout
P3
normal
RESOLVED INVALID
15 years ago
14 years ago

People

(Reporter: Lloyd Wood, Assigned: Marc Attinasi)

Tracking

Trunk
Future
All
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
Client-side imagemaps require default shape to be the last shape specified
to work correctly; any shapes specified after the default shape in the given
map used are ignored entirely. Example URL compares imagemaps with default shape
specified first in list (nothing works bar the default) and last in list
(everything works as specified.)

This shouldn't be order-dependent.

Handling of default shapes seems poor in general - see also bug 123800,
where not having a client-side default shape leads to poor fallthrough to
and display of server-side imagemaps.

Updated

15 years ago
Priority: -- → P3

Updated

15 years ago
Target Milestone: --- → Future

Comment 1

15 years ago
This is NOT a bug--it is order dependent, as per the specification:

"If two or more defined regions overlap, the region-defining element that
appears earliest in the document takes precedence (i.e., responds to user input)."

http://www.w3.org/TR/html401/struct/objects.html#h-13.6.1
(Reporter)

Comment 2

15 years ago
Sorry, this is a bug, as the specification cited indicates. From:

http://www.w3.org/TR/html401/struct/objects.html#h-13.6.1

"If two or more defined regions overlap, the region-defining element that
appears earliest in the document takes precedence (i.e., responds to user input)."

Note that it says *region-defining* element. Now look at how the elements
are introduced in that document:

"shape = default|rect|circle|poly [CI]
    This attribute specifies the shape of a region. Possible values:

        * default: Specifies the entire region.
        * rect: Define a rectangular region.
        * circle: Define a circular region.
        * poly: Define a polygonal region."

Note that default is not a region-defining element. It's a region-*specifying*
element that indicates a known unique region with special properties (you don't
have to define coordinates). Subtle difference, but a careful choice of words
that falls in line with what common sense would suggest.

Default is what you should fall back to, regardless of when it is specified.
As the term that introduces it indicates, it's a special case. Everything
else overlaps with default; regions other than default take precedence.

(I can, however, believe that if you accidentally include two default regions in
your imagemap, the first one should take precedence.)

cheers,

L.
Sorry, but I think you're reading more into the difference between "defining"
and "specifying" than is warranted....

The current behavior, as far as I can tell, follows the spec, is consistent
(earlier elements always override later ones) and most importantly is compatible
with other browser.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.