Closed
Bug 236219
Opened 21 years ago
Closed 19 years ago
Unreliable highlighting in compose window when tabbing thru
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mcow, Assigned: sspitzer)
References
Details
(Keywords: fixed1.8.1, polish)
Attachments
(2 files, 2 obsolete files)
|
2.50 KB,
patch
|
Bienvenu
:
review+
mscott
:
superreview+
|
Details | Diff | Splinter Review |
|
4.37 KB,
patch
|
mscott
:
approval-branch-1.8.1+
|
Details | Diff | Splinter Review |
Bug 215846 fixed the compose window so that if the attachments panel contains
anything, it becomes part of the tab order. (At this writing, requiring
F6/Shift-F6 or Ctrl-Tab/Shift-Ctrl-Tab; just plain Tab does not pass thru the
panel.)
Tabbing from Subject to Attachments to Body (using F6 or Ctrl-Tab), when the
focus arrives at the attachments box, the attachment highlight goes from grey to
black, but on leaving the attachments box), it remains black.
Reversing the process with Shift-F6/Shift-Ctrl-Tab handles the highlighting
correctly.
To reproduce: Open a compose window. Attach a file; then single-click the
attachment entry to select it. Move focus to the Subject box.
Type F6, F6.
Actual result:
Attachment selection becomes black on first F6, remains black on second F6.
Expected result:
Attachment selection becomes black on first F6, becomes grey on second F6.
xref bug 205666.
Updated•21 years ago
|
Product: MailNews → Core
| Reporter | ||
Comment 1•20 years ago
|
||
On further examination with Mozilla 1.7.11, the problem of the highlight not
being cleared is not restricted to the move from Attachment box to Body; it also
occurs when using Shift+F6 to move from the From field to the Body.
Interestingly, shifting the focus from Subject to Body with F6 (when there is no
attachment in the list) does clear the highlight from the Subject.
Summary: Unreliable highlighting in Attachments pane when tabbing thru → Unreliable highlighting in compose window when tabbing thru
| Reporter | ||
Comment 2•20 years ago
|
||
This is analogous to the issue where F6/Ctrl+Tab navigation of the main window
does not clear the focus ring when the focus is shifting into the message pane
with F6/Shift+F6 (in 1.7.x and earlier -- this was fixed in the suite as part of
bug 203386).
| Reporter | ||
Comment 3•20 years ago
|
||
I did the same thing here that I did in the patch for bug 203386 to force the
focus-ring updating amongst the panes. Simple, works great.
This also fixes the Reply and Edit-as-New cases described in bug 289339 -- a
compose window that opens to put the focus in the body initially will now have
the 'From' focus indicator cleared.
I'm not sure if it's worth caching the result of
document.getElementById("appcontent")
as is done for so many other elements such as with GetMsgIdentityElement().
Maybe it's more efficient, maybe it's not; it sure doesn't make the code any
easier to read, in my eyes.
Neil, I don't know if this patch drops in for the suite, but it's short and
easy. I got the "appcontent" element name from the .xul file.
Attachment #191891 -
Flags: superreview?(mscott)
Attachment #191891 -
Flags: review?(neil.parkwaycc.co.uk)
| Reporter | ||
Updated•20 years ago
|
Attachment #191891 -
Attachment description: patch for TB (sorry, not a CVS diff) → patch for TB (sorry, not a CVS diff -- this is against the 0805 build)
| Reporter | ||
Comment 4•19 years ago
|
||
Comment on attachment 191891 [details] [diff] [review]
patch for TB (sorry, not a CVS diff -- this is against the 0805 build)
David, can I get a review from you on this?
Attachment #191891 -
Flags: review?(neil.parkwaycc.co.uk) → review?(bienvenu)
Comment 5•19 years ago
|
||
Comment on attachment 191891 [details] [diff] [review]
patch for TB (sorry, not a CVS diff -- this is against the 0805 build)
seems OK - I'll try it out in a bit.
Attachment #191891 -
Flags: review?(bienvenu) → review+
| Reporter | ||
Comment 6•19 years ago
|
||
(In reply to comment #5)
> (From update of attachment 191891 [details] [diff] [review] [edit])
> seems OK - I'll try it out in a bit.
David, any further feedback on this?
Scott, can you sr?
| Reporter | ||
Comment 7•19 years ago
|
||
Added an additional fix for an erroneous reference to a nonexistent
"bucketTree" that shows up while testing my changes.
The other bug that shows up while testing this (when trying to F6/Shift+Tab
into the addressing widget) is bug 311217. At the moment, that's beyond my
capacity to fix.
Attachment #191891 -
Attachment is obsolete: true
Attachment #191891 -
Flags: superreview?(mscott)
| Reporter | ||
Updated•19 years ago
|
Attachment #212402 -
Flags: superreview?(mscott)
| Reporter | ||
Comment 8•19 years ago
|
||
Thanks to Aleks Totic's work at bug 276075, I've now got a working Venkman for TB installed, and I was able to fix the problem at bug 311217 as well. Asking for re-review and sr.
Attachment #212402 -
Attachment is obsolete: true
Attachment #212507 -
Flags: superreview?(mscott)
Attachment #212507 -
Flags: review?(bienvenu)
Attachment #212402 -
Flags: superreview?(mscott)
Comment 9•19 years ago
|
||
Mike, I'll give this a try once I've cleaned up my mess on the other f6 patch
Comment 10•19 years ago
|
||
Comment on attachment 212507 [details] [diff] [review]
diff -u vs. trunk (1.6a1) 0216 nightly distro
the one thing I noticed while testing this is that the selection always goes to the first attachment when cycling through with f6, even if a different attachment was selected (e.g., attachment #2 [details] [diff] [review]). I doubt this is a regression, but I'm just pointing it out. I'll attach the diff I have in my tree...
Attachment #212507 -
Flags: review?(bienvenu) → review+
Comment 11•19 years ago
|
||
| Reporter | ||
Comment 12•19 years ago
|
||
(In reply to comment #10)
> the one thing I noticed while testing this is that the selection always goes
> to the first attachment when cycling through with f6, even if a different
> attachment was selected (e.g., attachment #2 [details] [diff] [review] [edit]). I doubt this is a
> regression, but I'm just pointing it out. I'll attach the diff I have in
> my tree...
Yeah it does -- the function that gets called is (and has been all along)
|FocusOnFirstAttachment()|. I have some ideas on fixing that, which I'll put into bug 303712 after this stuff gets checked in.
Comment 13•19 years ago
|
||
Comment on attachment 212507 [details] [diff] [review]
diff -u vs. trunk (1.6a1) 0216 nightly distro
can we just remove
+// var element = document.getElementById("msgRecipient#" + awGetNumberOfRecipients());
instead of commenting it out?
Attachment #212507 -
Flags: superreview?(mscott) → superreview+
| Reporter | ||
Comment 14•19 years ago
|
||
(In reply to comment #13)
> can we just remove [code] instead of commenting it out?
Definitely; David's CVS diff already has done, in fact. Thank you, Scott.
David, would you do the honors of checking that in?
Comment 15•19 years ago
|
||
Comment on attachment 212610 [details] [diff] [review]
cvs diff
Mike, I'm assuming we want this for 2.0 - are there any other patches that this patch is dependent on?
Attachment #212610 -
Flags: approval-branch-1.8.1?(mscott)
| Reporter | ||
Comment 16•19 years ago
|
||
(In reply to comment #15)
> are there any other patches that this
> patch is dependent on?
No, this is standalone, as far as I know. It's the only patch I've made that affects the compose window.
Comment 17•19 years ago
|
||
k, thx. Marking fixed on trunk. We'll let it bake a little and then put it on the branch.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Attachment #212610 -
Flags: approval-branch-1.8.1?(mscott) → approval-branch-1.8.1+
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•