haha, good luck with the battle, I just have to give some props, never have I used such a nice browser. You and the kids keep up the good work.

thumbs up fellas,

just a word to say Safari now does essentially all of my browsing. The last release effectively allowed me to work 100% with the agenda system of the lab. No more need to fire-up IE.
Bye bye M$.

Your battle is much appreciated. I'm not a mac-user, but are looking forward to the time I see your work with auto:overflow backported to Konquorer. The lack of support of this has been the greatest drawback in Konqueror for a long time in my opinion.

I seldom use any other browser these days, thanks to you and Apple!
My only remaining big problem with Safari, is that it does not work with my internet bank. My bank uses Netscapes certificate handling. The procedure goes like this - first I enter my Personal ID Number and Password, then I create a bank certificate, which fails in Safari. It simply downloads the certificate which is called "certnew.cer" by the way, which I now know is in the DER-format.
In Netscape this instead brings up a dialogue box where you set your Security Device password(or something) etc. After this, you also create a Personal Certificate. This doesn't work at all in Safari, it complains about a non-working bank certificate. I've tried importing the "certnew.cer" into Keychain, which works fine, but doesn't do anything when I try to connect to my bank.

Is this really hard to implement in Safari? Explorer doesn't work either, only Netscape 6/7 and Mozilla 1.3 and up. Don't know why Camino won't work, but it seems it's just not up to date with the latest Mozilla code.
I know you know alot about the inner workings of Mozilla, so I hope that this might get fixed.

This is the address to my bank (Swedish), though I don't know how much you can gather from that site since you don't have a bank account there:

http://www.skandiabanken.se

I'd also like to give props to you and the entire team working on Safari. I have been used to using nightly builds of Mozilla until Safari was released. I have been using both until the latest beta release of Safari. The only reason I need Mozilla now is due to Safari not working properly behind my works firewall/proxy server. It does not allow me to access any SSL based pages from that location, although Mozilla does with no problems. I can access the same sites from home with no problems. Hopefully this will get sorted out soon, and I will not need Mozilla at all. Again, keep up the great work.

Thank You!!

It would be very useful to under what type of features overflow:auto gives you... The IHT discussion on their layout widget sheds some light. More would be welcome!

I'd also like to throw in a vote for better SSL handling, (read: Personal Certs). Right now, the only browsers you can really use at MIT are Mozilla, and IE 5.5 and up (Win only).

john

While you're working on scrolling, take a look at page scrolling when the tab bar is open. Safari scrolls beautifully without the tab bar, but it seems as if scrolling when background tabs are loading doesn't work properly. Pictures won't draw properly. So if there was a picture under the tab bar and I scrolled up to see more of it, the block of the picture that was under the tab bar would be drawn incorrectly.

Hi!
Good job - Safari is definitely coming along - and it's great that scrolling support is getting put into place.
I have a question about bug reporting:
I'm doing QA for a DHTML / Javascript framework, and have been encountering a number of bugs and issues in Safari...
I've been reporting bugs to Apple through the little [BUG] icon on the Safari app.
Is this the best way to report bugs?
I notice that once the report is submitted, there's no way to track what happens to it, including whether it's likely to get resolved for the official release.
The reports I want to submit have been isolated pretty well, with minimal test-cases to reproduce, rather than just being a report of mis-rendering on some public site, with no attempt to isolate the responsible code...
I have been pointed to http://bugreporter.apple.com, which allows you to actually watch the progress of bugs, but seems to be really set up for Mac OS-level issues.

Which of these should I (and other web developers) use to report issues once we've isolated them? Which is more useful to you? Also, if it is better to report bugs through the tool built into the application, is there any way to get feedback on whether issues are going to be resolved?

Thanks

Hyat, you'll beat overflowzilla!

After that you can do some easier (?) stuff, like BUTTON-tag and the css clear property.

Are there any forums where people are discussing more technical Safari topics? I like this discussion but it seems inappropriate to stray from Dave's topic and I have some questions taht I can't find an answer to.

relational to pb's post, is there anywhere to post "this site is broken in safari" urls, or should that be a bug report?

Any problems with Safari at all should be reported using the bug button -- that's what it's for. kap: "site broken" problems should be definitely reported via the bug button in Safari. As for Paul Notley's comment, I believe the bug button is the most useful one to David Hyatt and is team, as that's why they put it there.

I think Hyatt wants to restrict his weblog comments to problems on the specific topics that he's posted -- so if you have a problem in relation to overflow, then it would be appropriate to post it here. Otherwise, you should probably use the bug button.

Of course, Hyatt could want you to post here instead, but I think he's made it clear in the past.

Then perhaps we can move on to drag and drop text support.... One of the things I find frustrating about many of my new Apple apps... I can't drag out clippings...

I have whole Libraries of various bits of brower booty in clipping format. Special bonus: the whole of the content shows up in column view previews.

You can drag out clippings - you just need to hold the mouse button down a few moments before you begin your drag

Just curious, but will the event onScroll be supported?

Similarly... Someone showed me a site that didn't work in Safari... So I took the time to isolate the problem (only a few lines)... But I have it hosted on my laptop, which even though I have broadband, I don't like to keep it on all the time. I really don't know whether I should post it through the bug button because then they may check it when my laptop is off and I doubt they'll continue to recheck it... Hrm...

You can send page source along with a bug-button report so they can try it out locally...

Regards,
Harald

Are you guys going to implement plug-in transparency, as utilized by flash?

You can test your buggy things with http://www.craigdavid.co.uk. An example of site that doesn't work very well with Safari.

While we are on the subject of scrolling...

The bug where safari jumps a long way in the wrong direction while scrolling the mouse wheel and moving the mouse at the same time still persists.

It goes like this: Load a long page, scroll the wheelie downwards and while doing this drag the mouse towards you. Guess where you end up? Top of the page! Ack!

I have not read all the posts but two scrolling bugs still persist for me, the most annoying is having scrolling controls neuter themselves, specifically the bottom scroll arrow when set up to have both at bottom of a window scroll bar. Seems to happen most of the time with forms pages. The other bugs: jumping and speed with long lists. Any way to refine scroll control in the code some more?

The craig david site looks fine with my overflow:auto patch, and the scrolling works in that news ticker on the left.

if you're looking for more bugs check out this page

http://www.blizzard.com/support/?id=mwr0642p

the rows render indented each way.

I guess I could go through the file and figure out what's wrong, but camino and ie both render it correctly.

Have no friends not equal to yourself.