Reorder Help tabs per usability test

VERIFIED FIXED in mozilla1.0.1

Status

SeaMonkey
Help Documentation
P3
normal
VERIFIED FIXED
16 years ago
13 years ago

People

(Reporter: Sean Cotter, Assigned: Ian Oeschger (gone))

Tracking

Trunk
mozilla1.0.1
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [adt2 rtm],custrtm-,adt1.0.1)

Attachments

(2 attachments)

(Reporter)

Description

16 years ago
Our recent usability test showed that users frequently find the tabs located at
the bottom of the TOC frame difficult to see. Therefore, we would like to
reorder the tabs as follows and continue to open to the Contents tab by default,
so that all the tabs are located at the top of the frame by default:

New order, from top to bottom: Glossary/Index/Search/Contents
(Reporter)

Comment 1

16 years ago
nominating for nsbeta1
Keywords: nsbeta1
Priority: -- → P3
Whiteboard: [adt1]
Target Milestone: --- → mozilla1.0

Comment 2

16 years ago
I agree with this, marking new
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 3

16 years ago
Marking as nsbeta1+, for RTM. 
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt1] → [adt1 rtm]
(Assignee)

Comment 4

16 years ago
Created attachment 78709 [details] [diff] [review]
reordering panels in help
(Assignee)

Comment 5

16 years ago
Created attachment 78710 [details]
screenshot of patch above
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED

Comment 6

16 years ago
Changing impact and milestone.
Whiteboard: [adt1 rtm] → [adt2 rtm]
Target Milestone: mozilla1.0 → mozilla1.0.1

Comment 7

16 years ago
Comment on attachment 78709 [details] [diff] [review]
reordering panels in help

r=andreww
Attachment #78709 - Flags: review+

Comment 8

16 years ago
Adding custrtm-; no impact for customization. 

Comment 9

16 years ago
Comment on attachment 78709 [details] [diff] [review]
reordering panels in help

sr=alecf
Attachment #78709 - Flags: superreview+

Updated

16 years ago
Keywords: mozilla1.0.1

Updated

16 years ago
Whiteboard: [adt2 rtm] → [adt2 rtm],custrtm-
(Assignee)

Comment 10

16 years ago
Checked in fix on trunk. So, what do I do again?, mark this FIXED and add
something further when I go in on the branch?

Comment 11

16 years ago
> Checked in fix on trunk. So, what do I do again?

I think the convention is to add [fixed on trunk] to the Status Whiteboard.

Comment 12

16 years ago
Ian, if you think this is ready for the branch, mark it with an adt1.0.1
keyword. We'll need an "a=" for the Moz branch; I'll ask ADT for approval as well.
(Assignee)

Comment 13

16 years ago
Adding adt1.0.1 keyword for check in to branch
Whiteboard: [adt2 rtm],custrtm- → [adt2 rtm],custrtm-,adt1.0.1

Comment 14

16 years ago
l10n approved to check into branch. please check it in today.

Comment 15

16 years ago
Verified fixed win xp trunk build 2002060408, Mac OS X trunk build 2002060403
and linux trunk build 20020604, marking fixed (hope that's okay) and will come
right back and mark verified
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 16

16 years ago
Verified :-)
Status: RESOLVED → VERIFIED

Updated

16 years ago
Attachment #78709 - Flags: approval+

Comment 17

16 years ago
please checkin to the 1.0.1 branch, once there remove the "mozilla1.0.1+"
keyword and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1 → mozilla1.0.1+
(Assignee)

Comment 18

16 years ago
checked in on the branch (and the trunk before). updating keywords.

Keywords: mozilla1.0.1+ → fixed1.0.1

Comment 19

16 years ago
Verified Fixed Win XP branch 2002082209, Mac OS X (Jaguar) branch build
2002082205 and linux branch build 2002082207
Keywords: fixed1.0.1 → verified1.0.1
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.