Apprunner Build ID: 1999100118 In the Navigator category, the bottom preference is thus arrayed: |- Location Bar History -------------------------------| | | | Clear the list of sites on the location bar: [Clear] | | | |______________________________________________________| <Smiles in true apprecation> This application parses HTML, does it not? Hyperlinks? May we not re-arrange this interface as: [Clear] the list of sites on the location bar ?
german is working on the pref final wording etc. reassign.
Good concept, I'll consider later, past dogfood. My gut feeling is the full list is too complex a UI for general usage.
It is somewhat unusual to have the coammnd button that performs the action in front the label that explains the consequences. Yes I agree the wording could be finetuned (and it will) but I would not reverse the order. Usually users are afraid to click a command button without having read what it does. cc'ing vera for ideas on better wording...moving to m16
Rea-ssign to verah(writer) to see whether we want to change the wording...
I'll put some thought into it soon. Thanks!
Bulk move of all Pref UI component bugs to new Preferences component. Pref UI component will be deleted.
Component: Pref UI → Preferences
This is not a stability blocker for M15 checkpoint. Pushing to M16 to facilitate an M15 branch.
Target Milestone: M15 → M16
What's happening with this?
I've changed the explanatory text to "Clear the list of sites stored in the location bar menu." We're not using hyperlinks in the Prefs dialogs, so we still have a button labeled "Clear Location Bar." This section of the Navigator Prefs dialog has the heading "Location Bar." I'm hoping the wording change makes it more obvious what clicking this button does. However, I'm planning on looking at it again for a general UI text cleanup before M20. You will see the wording changes I've already made when M16 comes out (or maybe you can see it now -- it's checked in, but I haven't been able to install the latest build!). If you think it's okay then go ahead and close this bug after you see the change; if not, add a comment and I'll up the milestone to M20 and work on it some more.
M16 has been out for a while now, these bugs target milestones need to be updated.
I'm going to mark this fixed. My new wording is in as of M16; it's not exactly what the author of this bug suggested but it is more clear.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.