Closed
Bug 202892
Opened 22 years ago
Closed 15 years ago
Double clicking table tag in HTMLTags view brings up the cell dialog
Categories
(SeaMonkey :: Composer, defect)
SeaMonkey
Composer
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: ansum, Unassigned)
Details
(Keywords: helpwanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
It seems like the editor is confused if tags are chained without any text
between them.
Reproducible: Always
Steps to Reproduce:
1. Load the example into editor:
<html>
<head>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<title></title>
</head>
<body>
<table cellpadding="2" cellspacing="2" border="1"
style="text-align: left; margin-left: auto; margin-right: auto; width: 100%;">
<tbody>
<tr>
<td style="vertical-align: top;">doubleclicking the adjacent td
symbol will bring up the table cell dialog. (that is what I would
expect)</td>
<td style="vertical-align: top;"><a href="http://www.mozilla.org/">double
clicking the adjacent td symbol will bring up the link properties dialog</a><br>
(Which does not seem quite right)<br>
</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>
2. goto HTML-Tags view
3. Double click the td tags and see which dialogs pop up.
Note: A double click on the table tag will bring up the cell properties instead
of the tabkle properties.
Actual Results:
wrong Dialogs pop up
Expected Results:
I would like to see the properties dialog of the current tag instead
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Double clicking a tag symbol in the HTML-Tags view does not always bring up the appropriate dialog → Double clicking table tag in HTMLTags view brings up the cell dialog
Updated•22 years ago
|
Keywords: helpwanted
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•17 years ago
|
Assignee: composer → nobody
QA Contact: chrispetersen → composer
Comment 1•16 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•15 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
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•