Complex pages do not properly display in "Show All Tags" view - some tags are not accessible

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
18 years ago
9 years ago

People

(Reporter: TucsonTester2, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
Build ID: 20010924

In composer if you edit the page www.nvidia.com and switch to "Show all Tags"
view then you will see that you can not double-click on some of the tags.

Reproducible: Always

Steps to Reproduce:
1.Open Browser and go to http://www.nvidia.com
2.Click on File->edit page
3.Switch to "Show all tags" view

Actual Results:
The biggest problem is with the tags in the top left.  A few stack up on top of
each other and you can not edit all of the tags.  As you can see the body tag is
not accessible.

Expected Results:
I would expect that I would be able to edit all of the tags and that they would
all viewable in "Show All Tags" view.

Comment 1

17 years ago
Confirmed on Win 2k using build 20011003, and Mac OSX using build 20011004.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

17 years ago
Status: NEW → ASSIGNED

Comment 2

17 years ago
-->glazman
Assignee: syd → glazman
Status: ASSIGNED → NEW
milstone bulk change
Target Milestone: --- → mozilla1.0.1

Comment 4

16 years ago
*** Bug 178076 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: daniel → nobody
QA Contact: sujay → composer
Target Milestone: mozilla1.0.1 → ---

Comment 5

10 years ago
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 6

9 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: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.