Bug 114077 – Allowing a pause before searching History & omitting Google strings from results

• Status: RESOLVED
• Resolution: INVALID
• Component: History

[nonegiven]

Excuse me I am an idiot and am new to trac-ing, however, I am a fairly heavy and professional user.

There are two enhancements which I think would improve WebKit/Safari. Again, excuse me if these have already been dealt with. I am not using 10.8 yet.


a) Allowing a keystroke/pause before searching 'History' page

b) Automatically omitting the Google strings from history results both in the History page and drop down menu.


- a) Currently, in 'Show all History', when I type a single letter WebKit/Safari pauses and beachballs. It starts searching for results which are mostly irrelevant and also blocks me from continuing to type the rest of the word I am looking for.

- The only work around for this is to type out the search somewhere else and then 'copy and paste' it into the Search window so it searches only for that word .... and not everything sharing the first letter.

• Solution: Either it should i) pauses for a fraction of a second, ii) wait until (say) three letters have been typed adjustable in preferences, iii) be smart enough to wait until one has stopped typing, iv) sort results in the background *until* one has stopped typing.

- There is something wrong in it consuming resources when achieving nothing.


- b) Currently Google has a very bad form of prefixing any link one is choosing in Google search results with the Google URL and a long string of other characters it is no doubt using for its commercial benefit.

– In history, this blocks one from seeing what the actual URL was. Instead one only sees the start of the Google address which is pointless in locating the actual URL you wanted.

• Solution: Someway of removing or making non-visible the Google strings.

Hope that helps/

[Alexey Proskuryakov]

Thank you for the report, these are both interesting ideas!

I'm however marking this INVALID. The reason is that both are Safari enhancement requests, while we only track WebKit issues here in Bugzilla. Please see <https://www.webkit.org/blog/101/back-to-basics/> for more details about the difference.

Please file these enhancement requests at <http://bugreport.apple.com> for Apple engineers working on Safari to consider. It's very desirable to file them in separate bugs, not in a single one.