Closed Bug 93538 Opened 23 years ago Closed 23 years ago

spt.com - should not use a space in image map name

Categories

(Tech Evangelism Graveyard :: English US, defect, P3)

Product:
Tech Evangelism Graveyard
Component:
English US
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: neel, Assigned: doronr)

References

(
URL
)

Details

(Whiteboard: [SYNTAX-HTML] [Works in Moz 20011120 and newer] aok)

Navigation image map in the middle of the page does not work, though the mouse pointer changes to "link" style when passed over this map. To reproduce: go to http://www.spt.com, try to click on the large image map in center of page (Homeimg.jpg). Possible duplicate of bug #74867 ?
The tag for the map is <map name="Home image"> so in case of dupping it's against 84252 due to the space in the name for the map. The other option is to move this to evangelism.
evang sounds good to me.
Assignee: asa → bclary
Component: Browser-General → Evangelism
QA Contact: doronr → zach
Summary: Image map does not work; works fine in NS 4.78 → Image map w/ space in name does not work; works fine in NS 4.78
->NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Changing summary to reflect the intent of this bug.
Summary: Image map w/ space in name does not work; works fine in NS 4.78 → www.spt.com should not use a space in image map name
Whiteboard: [SYNTAX-HTML]
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Priority: -- → P3
Summary: www.spt.com should not use a space in image map name → spt.com - should not use a space in image map name
This is a duplicate of bug 87050, and should not be evanged unless that bug is also wontfixed.
Why isn't this example failing the W3C HTML Validation Service (at least for that reason). I have the same issue with www.bnc.ca . How do you expect to evangelize this if it doesn't fail W3C validation? I understand that HTML 4 mentions the valid characters and doesn't included spaces, but 3.2 didn't seem to be so specific.
The W3 validation service uses SGML and probably can't catch attribute problems. The same is true of case Class names and attributes. For better or worse we are pretty strict about what we will accept.
*** This bug has been marked as a duplicate of 87050 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
this is not a duplicate. Evangelism bugs are filed against sites who exhibit bad coding practices.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I think this should have been left as a dup because: a) Bug 87050 is going to be fixed soon. b) Several other evangelism bugs, including one I filed, were marked as dups of bug 87050 and bug 1882.
Fixed soon on the trunk still means many people will be using versions of browsers based upon Mozilla that do not have the fix. That means that this is still an evangelism issue. This is not the highest priority issue facing us, but it is still something we can do to help improve the experience of users of browsers based upon Mozilla. As for the other bugs that have been duped, they should probably be reopened and assigned to evangelism.
As this works in newer Moz, added that to the whiteboard. To default assignee +aok
Assignee: bclary → doronr
Status: REOPENED → NEW
Whiteboard: [SYNTAX-HTML] → [SYNTAX-HTML] [Works in Moz 20011120 and newer] aok
any use on keeping this open? I don't think a "your HTML is bad" will do anythink. and btw. the imagemap is gone.
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.