Closed Bug 720657 Opened 12 years ago Closed 10 years ago

Investigate possible side-effects of bug 566489 (Enable inline autocomplete again) on SeaMonkey

Categories

(SeaMonkey :: Autocomplete, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: neil, Unassigned)

References

Details

Some of the changes made to places autocomplete may impact SeaMonkey.
> Some of the changes made to places autocomplete may impact SeaMonkey
How does one investigate this?

Gosh a lot of regressions from bug 566489 !
https://bugzilla.mozilla.org/showdependencytree.cgi?id=566489&hide_resolved=0

Also see:
Bug 659437 - Tracking bug for URL autocomplete edge cases

Bug 720258 Quote: "There's already anger over inline-autocomplete, and I don't think that's going to go away as the change gets rolled out to more users"
Bug 720240 "Enable inline autocomplete again, but make it smarter" actually made it dumber
Depends on: 720792
Summary: Investigate possible side-effects of bug 566489 on SeaMonkey → Investigate possible side-effects of bug 566489 (Enable inline autocomplete again) on SeaMonkey
I'm going through the regressions, most are in the controller and due to pre-existing bugs, others are just bugs that were already there with the old implementation but being reported again. I'll now look into bug 720792 that is likely the change most impacting Seamonkey. The other changes should not have an interesting impact, but feel free to ask and I'll try to answer.
I think there should be no side effects as of now, apart possible new bugs introduced, but that's another story.
(In reply to Marco Bonardo [::mak] (needinfo? me) from comment #3)
> I think there should be no side effects as of now, apart possible new bugs
> introduced, but that's another story.
Removing this bug from my bug radar.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.