Closed Bug 45060 Opened 25 years ago Closed 25 years ago

Addressing Area: display the background lines

Categories

(SeaMonkey :: Themes, defect, P2)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.8

People

(Reporter: jglick, Assigned: hewitt)

References

Details

(Keywords: polish, Whiteboard: [nsbeta1+])

Attachments

(2 files)

In the Addressing Area of Mail Compose, it would be helpful if we could display the background lines/grid like 4.x.
P2 per Mail UE Review. Nominate as nsbeta3
Keywords: nsbeta3
Priority: P3 → P2
QA Contact: lchiang → laurel
Would be nice to have but we have so much else to do...
Status: NEW → ASSIGNED
Keywords: polish
Whiteboard: nsbeta3-
Target Milestone: --- → M20
Whiteboard: nsbeta3-
mail6 type of nsbeta3 bug per mail triage
Whiteboard: mail6
Target Milestone: M20 → M18
Keywords: mail6
Whiteboard: mail6
mail triage marking [nsbeta3-]
Whiteboard: [nsbeta3-]
Sorry for the extra email. Removing mail6 keyword.
Keywords: mail6
marking nsbeta1+ and moving to mozilla0.8. This is only in the modern skin.
Keywords: nsbeta3nsbeta1
Whiteboard: [nsbeta3-] → [nsbeta1+]
Target Milestone: M18 → mozilla0.8
Classic theme already has the background line.
Modern skin should have the background lines.
reassign to varada
Assignee: ducarroz → varada
Status: ASSIGNED → NEW
Assignee: varada → hewitt
reassigning to hewitt. cc'ing hangas. We'd talked about giving differences in skins to Paul's team. Feel free to reevalue the beta1 acceptance and milestone. The current settings mean that mailnews would like this. If you guys aren't going to be able to help out with this, please reassign this back to varada.
I'm happy to take this since I always wanted to see those old grid lines from 4.x come back... the question is, what is the right way to do it? In classic, there is only one grid line drawn because there is only one treerow to style. If we wanted to fully emulate the 4.x look in which the grid covers the entire tree, that would take some js work to create and dispose of "dummy rows" to fill the empty part of the grid, but go away if new addressees are added.
Status: NEW → ASSIGNED
Component: Composition → Themes
Product: MailNews → Browser
Target Milestone: mozilla0.8 → mozilla0.9
Themes Triage Team nsbeta1+
I've got a working fix for this which I will post soon as patch once I refine it a bit. I'm cc'ing ducarroz because I had to modify his code a bit to make this work. As I stated in my last comment, we needed to add some "dummy rows" to the addressing widget tree so the empty space in the tree can be filled with grid lines for address rows that have yet to be entered. As new addresses are entered, the dummy rows are replaced. This solution required just a bit of new code in addressingWidgetOverlay.js.
As I play with my solution as detailed below, I see some problems that I don't think are avoidable: 1. the dummy rows created when msgcompose first fires are static, meaning that if the tree grows (due to the splitter being adjusted) no more new rows will be created, and thus there will be a big empty space in area that grows. I don't know of a way to capture an event for when a splitter is moved, but if there is such an event then there is a way to solve this problem. 2. treerows currently are all forced to be the same size as the largest in the tree. Because of this, there will be some empty space at the bottom of the tree that contains no gridlines because there's no way for me to specify that the last tree row should fill the exact amount of space remaining.
Target Milestone: mozilla0.9 → mozilla0.8
Blocks: 45062
Attached patch patch to fixSplinter Review
Hold on that patch. I'm going to revise it so that dummy rows are created when the splitter is moved and when rows are deleted.
good. R=ducarroz.
sr=sspitzer
fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
VERIFIED FIXED on build 2001020504 (windows 2000), build 2001020513 (mac os 9.0.4) and build 2001020506 (linux redhat 7.0).
Status: RESOLVED → VERIFIED
You might want to double-check the changes that were checked into -r1.45 of addressingWidgetOverlay.js. There's now a problem with the "To/From/CC" field not showing up when the user enters an address then hits enter.
The following line in awAppendNewRow() is not properly being executed: if (nextDummy) body.removeChild(nextDummy); Since there has not been an update to get the new item displayed before the delete is performed, the two actions negate each other. The result is a missing "To/From/CC" button and the little card icon. If the above line is replaced with the following, it will prevent this from occurring (although it's probably not a good fix): if (nextDummy) setTimeout("awFitDummyRows();",0);
I think the problem with the To/CC/Bcc fields not appearing are logged in bug# 69524.
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: