Closed Bug 57564 Opened 24 years ago Closed 21 years ago

Can still add duplicate Smart Browsing entries

Categories

(SeaMonkey :: Preferences, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.2alpha

People

(Reporter: bugzilla, Assigned: samir_bugzilla)

Details

Build ID: new {trunk, branch}

Steps to Reproduce:
(1) Open the prefs window
(2) Navigator > Smart Browsing
(3) Type "Test" in the textfield next to "Domain:"
(4) Click the Add button
(5) Type "Test" again
(6) Hurry and press Add before it disables!

Result: You can add duplicate entries.  This really will become less and less 
noticeable as perf improves (since the button should hopefully disable 
immediately), but there should still be additional logic to prevent this from 
happening in any case.  I think this is bad UI, since just disabling the button 
if you've typed in a duplicate isn't very indicative why you can't add the 
site, especially if you have a long list of sites entered.  Although it is 
proactive instead of reactive error handling.  Hmm. Matt?
That's right. The `Add' button shouldn't disable, that tells you nothing. 
Instead, when you press the button, the list should just select (and scroll to) 
the entry that's already there.
taking
Assignee: matt → blakeross
OS: Windows 98 → All
Priority: P3 → P4
Hardware: PC → All
Target Milestone: --- → mozilla1.2
Status: NEW → ASSIGNED
reassigning for now
Assignee: blakeross → matt
Status: ASSIGNED → NEW
I think this is kind of fixed.
you cant add "test" twice. But you can add "test" and then "test "

btw: what does it mean to add "test". It says domains. Does that then mean
"gemal.test.dk" and "test.gemal.dk" or what? And what about "test "????
to samir.
Assignee: matt → sgehani
QA Contact: sairuh → claudius
This part of UI was removed by bug 149812. Choosing FIXED as resolution because
fix is known, although it's a way of fixing that cannotbe chosen for all bugs...
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.