Closed
Bug 114311
Opened 23 years ago
Closed 14 years ago
Writing in a table-cell behaves very weird
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: hwaara, Unassigned)
Details
Build 2001-12-08-08, Windows 98. 1. Create a new editor document 2. Click the table button in the toolbar, and create a table with 2 rows and 2 cols 3. Start writing in the focused cell immediately... Every time you key down in the cell, it will make the cell X% larger and the cell in the other column X% smaller. It just looks strange. I would expect the cell I am writing in to accomodate its size so it fits the string I've written in it perfectly, by default.
Comment 2•23 years ago
|
||
Blame stupid W3C rules for table layout. I hate this and in 4.x we used a proprietary NS tag (COLS) to suppress this behavior, but in the modern days of complete standards compliance, we aren't allowed to do that. You can suppress it by defining width attribute on the table cells (first cells in top row are enough). I will keep this open as a reminder to think about more creative ways to fight this behavior.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Updated•22 years ago
|
Target Milestone: mozilla1.1alpha → Future
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: Future → ---
Comment 3•15 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 4•14 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: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•