Closed Bug 243246 Opened 21 years ago Closed 21 years ago

Get Info box forgets Status tab selection after showing folder

Categories

(Camino Graveyard :: Bookmarks, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: brion, Assigned: stuart.morgan+bugzilla)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a) Gecko/20040510 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a) Gecko/20040510 Camino/0.7+ When a bookmark is selected in the bookmark manager, the Get Info box has 'Info' and 'Status' tabs. When a folder is selected, there are no tabs. Selecting a folder, then another item causes the second item to display with the 'Info' tab selected instead of remaining on (returning to) 'Status'. Selecting one bookmark directly after another does not change which tab is selected, and it is surprising that this is different. (It is particularly annoying using keyboard navigation, since moving from one folder to another then requires selecting it.) Reproducible: Always Steps to Reproduce: 1. Open Bookmark Manager 2. Select a bookmark 3. Open 'Get Info' box 4. Click 'Status' tab 5. Click on a bookmark folder 6. Click on another bookmark item Actual Results: When the second bookmark is selected, the Get Info box displays the 'Info' tab. Expected Results: It should come up with the 'Status' tab, where I left it. Mac OS X 10.3.3
Assignee: pinkerton → josha
Confirmed using 2004050308 (v0.8b).
Status: UNCONFIRMED → NEW
Ever confirmed: true
I imagine this is probably due to the fact that for some strange reason the folder info view exists as a tab in the bookmark view. I haven't looked at the code, but presumably there's weird view extracting/swapping going on. Bug 242650 is probably due to the same thing, so perhaps the views should be separated in the .nib file.
Assignee: josha → stuart.morgan
fixed on branch and trunk
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.