Closed Bug 12721 Opened 25 years ago Closed 25 years ago

Client-side image maps with spaces in name ignore spaces

Categories

(Core :: Layout, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: run2000, Assigned: pnunn)

Details

(Whiteboard: [TESTCASE])

Attachments

(1 file)

This bug follows on from bug 11453.

Tested on:

Mozilla 1999082708, M10 build, Windows NT 4 Workstation.

Expected bahaviour:

For the test case attached, the client-side image map should not work. The map
name contains a space in the middle of it, while the usemap attribute of the
image does not contain this space.

Current bahaviour:

The image map works as if nothing is wrong.

Other browsers tested:

Opera 3.60 and Internet Explorer 5 behave as expected.

Other comments:

Be careful not to re-open bug 11453 when fixing this.
Whiteboard: [TESTCASE]
Assignee: vidur → chofmann
This isn't a DOM/vidur bug.  Calgon -- ahem, chofmann -- take me away!
Assignee: chofmann → pnunn
not sure if I understand why this is bad...
looks like a pretty good graceful failure.
maybe pnunn can figure out what to do.
Let me get this straight.
The complaint is that the image map works,
right?
-pn
Assignee: pnunn → troy
This apparently is a *feature* implemented in
nsImageFrame::GetImageMap(). usemap.StripWhitespace() is
called for a NAV quirk. See line 563 in nsImageFrame.cpp.

This isn't really an imglib problem. I'd be happy to take
this one, if you are short handed. Looks like Kipp did alot
of the work in this area.
Reassign back to me if you'd like.

-pn
Assignee: troy → pnunn
Yes, that would be a big help if you could take this one. Thanks Pam
Status: NEW → ASSIGNED
Target Milestone: M13
The question now is do we support the Nav quirk or not...
I have no strong feelings on the subject either way.
If communicator ignored spaces before, what is the advantage
to suddenly start paying attention to them?
-pn
Can anyone give me a reason to
not support the Nav quirk of ignoring
spaces in image map names?

Convince me or I mark the bug invalid.
-p
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
I'm closing as invalid.
Status: RESOLVED → VERIFIED
Marking verified invalid per last comments.
This bug has wrong resolution. This bug is not INVALID, it should be WONTFIX.

Aside from that, I am wondering if this should be fixed for strict mode. What 
does IE do? Adding harishd to CC.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: