If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Composer Image Map tool icons are missing

RESOLVED EXPIRED

Status

SeaMonkey
Themes
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: John Dobbins, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
EdImageMap.css and EdImageMapPage.css in the Modern and Classic themes have
referances to images that are no longer there.

For Example these lines in EdImageMap.css set the icon for the pointer button in
the Classic theme.

#pointerButton {
  list-style-image:url("chrome://editor/skin/images/Map_pointerTool.gif");
}

The old images directory was eliminated in the December Chrome reorganization.
The Map tools icons are not in the new icons directory or in btn1.gif or btn2.gif.

In Modern the pointer button icon is set by these lines in EdImageMap.css

#pointerButton {
  list-style-image: url("chrome://editor/skin/btn1/map-pointerTool.gif");
}

Again the old directory was eliminated and the icons weren't transfered to the
new icons directory or to the large gifs.

All 10 of the maptool icons are missing from both themes.

Updated

16 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Updated

9 years ago
Product: Core → SeaMonkey
Assignee: hewitt → nobody
QA Contact: pmac → themes

Comment 1

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 2

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.