i do have safari 3.1.2 but this doesn't work like FF3. For example, lets say i visited this url, and it's in my browsing history:
http://www.myurl.com/mypath/
when i type "myurl mypath" in FF3 this url appears in the dropdown, but in safari in doesn't
I use Quicksilver and the Safari plugin to do that.
My Safari does exactly that.
I type 'mac' and get a list based on my history and bookmarks.
Your point is valid but you use kind of a bad example, since the URL for the Apple Support Discussions is discussions.apple.com so it will come up. Perhaps using "supp" makes a stronger case.E.g. if I visited a site a week ago called Apple Support Discussions, I could type into Firefox "dis" and it'd come up in the address bar almost telepathically. In Safari I'd be lucky if it came in when I typed "Apple" as Safari only looks at the beginning of the website URL or Title, not in the middle or elsewhere.
download safari 4? and it does this with no plugins needed. and you get the cool top sites page in you bookmarks bar, as well as a few other enhanced features. I downloaded it long before I upgraded to SL.. no problems, love it![]()
Webkit is the renderengine that Safari uses. Safari itself is a bit more than just webkit so submitting a bug to webkit for resolving a Safari interface issue will most likely be closed instantly. It's not something in webkit's control.You realize that WebKit (the code that powers at least 95% of Safari) is an open source project, right?
You can submit a bug report directly to http://webkit.org, maybe even submit a patch if you know how.
Safari 4 and Firefox 3 & 3.5 have both something similar regarding the addressbar. They both are able to search through the history and bookmarks to dig up a site. And that's where the similarities end. In Safari you can only dig up a site if you type in the first letters of its URL, which means you actually have to remember the first part of the URL. Firefox is much better at digging up sites because it can do what Safari does plus it can use keywords (anywhere in the URL or title of the page), tags and the keyword field. From a user perspective Firefox is an awful lot better at finding a site you forgot. This functionality is all about being able to find the sites you forgot and that is not accomplished with Safari's way of doing it since you need to remember the url. Firefox does not require that, the only thing you need to do is remember *something* about the site. That is a more natural way of doing things. If the list of results is to big you just specify some more keywords to narrow it down.My Safari does exactly that.
I type 'mac' and get a list based on my history and bookmarks.
Webkit is the renderengine that Safari uses. Safari itself is a bit more than just webkit so submitting a bug to webkit for resolving a Safari interface issue will most likely be closed instantly. It's not something in webkit's control.
Oh, the irony.Next time, rather than assuming you know how open source projects work, you should do a little research.
Then why on Earth are you still commenting?It's not very wise to make assumptions about how projects work when you, in reality, clearly have little knowledge about how the project actually works.
That would be due to the fact the webkit you downloaded uses the Safari GUI. That's why it looks and acts like Safari does. The only GUI thing they develop is the WebInspector.In addition to being a rendering engine, WebKit is the UI for Safari. If you took 3 seconds to visit http://webkit.org and download a nightly you would find that the app you've just downloaded is in every way equivalent (all the way down to the preference pane) to Safari except for the icon (it's a little more golden to differentiate WebKit builds from official Safari releases). The only real difference is the name and possibly a little extra (1%) fairy dust that goes into each release-- all of which eventually get backported. This includes all of the code for OSX and the Windows releases too. It is all open sourced.
Yes please, do some research next time like reading the website which you quite obviously didn't do. The frontpage says:Opening a UI related ticket at WebKit would be accepted, and in fact it's quite common, since, as I said, the WebKit guys implement the UI that you will eventually see in the Safari release.
Next time, rather than assuming you know how open source projects work, you should do a little research.
WebKit is an open source web browser engine. WebKit is also the name of the Mac OS X system framework version of the engine that's used by Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML and JavaScript code began as a branch of the KHTML and KJS libraries from KDE. This website is also the home of S60's S60 WebKit development.
WebKit is an engine, not a browser.
We do not plan to develop or host a full-featured web browser based on WebKit. Others are welcome to do so, of course.
In fact running Webkit on Windows requires Safari, without Safari you can't run Webkit. Which is quite obvious for something that is a render engine and not a webbrowser (as they say themselves).Running WebKit
1.
Type this command to run Safari with the WebKit you built:
WebKit/WebKitTools/Scripts/run-safari
Use the --debug option for a debug build:
WebKit/WebKitTools/Scripts/run-safari --debug