• June 11th, 2007 • 23 comments
New Safari for Windows full of bugs
Apple has released Safari for XP and Vista today
Some randoms screenshots from the web:
i.never.nu lots of random white spaces
Montreal Tech Watch : titles and dates are not displayed.
Le monde : random typography. Titles are disappearing too.
I have tried to see if the texts were changed to the background color or indented, but no, they are just hidden.
Bravo Apple.
Update: it seems that other users cannot reproduce the errors. I think it’s a problem with how it handles utf-8. (meaning users from the US don’t have the problems, but if XP is set to french, it f**cks up)
I am saying this because other french-speaking users have noticed the bugs too
June 11th, 2007 at 3:31 pm
OH MY GOD!!!!!!
Beta software doesn’t work right.
What’s the world coming too?????
June 11th, 2007 at 3:41 pm
Yes, it’s fast but even for a beta it shows too many strange things…
June 11th, 2007 at 3:46 pm
All three sites worked fine for me in Safari 3 beta and render identically for Firefox 2.0.
June 11th, 2007 at 4:33 pm
Are you on Vista or XP? Sites render fine on my XP.
June 11th, 2007 at 4:52 pm
Well, I could reproduce it for Lemonde.fr
And then I tried a search in Google.
HAHAHA !
Such a simple page to display, but now links are full of underscored spaces…
It is not *even* a beta !
June 11th, 2007 at 6:43 pm
@everyone
yes i can reproduce the errors.
and yes for a beta I expect problems like layout problems or color problems but definetely not hidden texts and random display!!!
June 11th, 2007 at 7:05 pm
Hey there,
I’ve not noticed any major oddities with the safari 3.0 beta on my mac. I suspect that the windows version is suffering from being released too early with little testing – which is sadly all too common nowadays.
June 11th, 2007 at 7:54 pm
random; Correction, *Apple* says it’s beta, but it’s not. The quality is really alpha-level. Public betas are supposed to be better than just beta to boot. I’ve used public beta software before and haven’t seen even a tiny fraction of the difficulties shown with Safari 3.
June 12th, 2007 at 2:38 am
Safari on Windows italian has the same identical problems!
I guess it’s a US-only beta. No other country can use it.
I’ve just tried TinyMCE (the JS engine seems to work perfectly): the pages come out totally garbled if you use bold or italic! Words simply disappear, unless you disable it!
That’s quite a seriuos issue!
June 12th, 2007 at 3:05 am
I can reproduce those errors too – on a Dutch OS. In my case it displays lots of sites just fine, while at others it just omits list elements, headings, and anything between <i> or <em> tags.
I was told that renaming a folder en.lproj to nl.lproj might help, but it didn’t.
How the language of the OS could make these particular differences, beats me!
Weird!
June 12th, 2007 at 3:05 am
I can reproduce those errors too – on a Dutch OS. In my case it displays lots of sites just fine, while at others it just omits list elements, headings, and anything between <i> or <em> tags.
I was told that renaming a folder en.lproj to nl.lproj might help, but it didn’t.
How the language of the OS could make these particular differences, beats me!
Weird!
June 12th, 2007 at 4:23 am
it is clearly alpha on windows, and what you are experiencing sounds like rendering engine bugs for UTF text.
however, the same build on mac os x very very stable, on non-english sites too (korean).
i guess steve pushed the engineers to release it for his wwdc keynote, what’s new
June 12th, 2007 at 9:13 am
Slight update,
I’ve noticed that on my mac the Safari 3.0 beta appears to be leaking memory like a sieve. At one point i observed it was using 1.2gb of virtual memory.
It also appears that other applications which use the Webkit are also affected.
Thus i have decided to remove this beta and wait until a proper stable release. If i want better rendering i’ll just try out the webkit nightly builds, but that is as far as i am going at the moment.
June 12th, 2007 at 10:00 pm
I had the same memory leak problem with it on my XP machine.
June 12th, 2007 at 10:12 pm
“Beta”? What fucking bullshit!
Look in “About Safari”.
It VERY clearly says “3.0 (522.11.3).
Let’s not get stupid – OK? If something is lower than version 1.0 you can rightly say it is “beta” software – but when the makers proudly proclaim it is version 3.0 – then they better fucking well have that software singing – and it DOES NOT SING.
It is a buggy, feature-poor memory hog with a crappy UI and bullshit window handling (like every Mac app – which is retarded).
If Apple want to make a difference in the browser space, then they are going the wrong way about it.
What is needed at this time is something which can level-foot it with Firefox -and this box of crap compares favourably to Phoenix 0.4 in my view.
Let’s see if they can actually produce a useful browser in 2 years from now – that’s about how much work they need to do.
June 13th, 2007 at 3:50 am
I really can’t see what all the fuss is about. I’m running Safari on XP and all is fine. Its been up 24 hours nearly and no more than 134Mb used. No problems rendering the websites listed above. In fact its IE that can’t render montrealtechwatch.com – the sidebar is completely missing. Of course Safari won’t render large chunks of the web as well as IE or Firefox, but isn’t that more to do with the fact that large chunks of the web use non-standard technology like ActiveX to do the wizardy which is of course microsoft only?
June 13th, 2007 at 4:16 am
Right on Garry,
Safari is one of the most standards compliant browsers around and the first to pass the “Acid 2 Test”:http://en.wikipedia.org/wiki/Acid2 Test
June 13th, 2007 at 4:41 am
On my Windows XP SP2 (US English version) Safari 3 is actually behaving REALLY BAD.
The texts are disappearing (even from pages like yahoo.com) and it’s totally unusable. I can’t see half of the links and half of the texts…
This is not beta, this is early ALPHA if anything.
June 13th, 2007 at 3:38 pm
Like Micheal, my install has loads of menu header text missing, the dropdown lists are blank, the webpage is missing chunks of imagery and text, and in this state it is just unusable.
Running Win XP Home SP2 on an AMD 64 FX-57 with 2 GB RAM.
Was expecting it to be better than this. Will wait for later BETA’s (if there are to be any) before trying again.
June 16th, 2007 at 7:42 am
It’s really amusing to see how people are whining about the quality of free software. If you don’t want to use a beta of Safari, continue to use IE or Firefox or whatever and be happy. Instead you jam all communication frequencies available complaining about it.
Don’t you see, that’s exactly what Apple wanted – massive feedback. Very smart of them indeed.
June 17th, 2007 at 3:55 am
the primary function of a web browser is to display web pages, right? isn’t a public beta supposed to do at least that? people are not complaining because they have found obscure bugs that no one else is seeing or because of some (rather theoretical at this point) buffer overflow bug. they are complaining because Safari on Windows is not able to display web pages most of the time. the quality of this beta is like it came directly off the developer’s machine who said “I tested it on my machine, it works”. it doesn’t look like they did an internal beta test at all, for some bugs are so painfully obvious. again, it’s okay if one or the other function is not fully functioning yet (and listed under “known bugs”), but Safari doesn’t display text and headings on a lot of people’s machines! I uninstalled the “beta” after only a few minutes, when it became clear it cannot be used to (gasp) browse the web! people have become to expect a lot more from public betas.
and I think it’s a shame that Safari on Vista looks like an OS X app and not like a Vista app. Apple, please be a good citizen (I know they won’t). ha, if MS Office looked like XP on the Mac, complete with the blue title bar, the scroll bars and everything – Mac users would go rampant.
June 19th, 2007 at 5:50 am
running safari 3.0.1 on win xp (belgian/dutch) here.
for me the biggest problem by far is the fact that when submitting (a form with) a textarea which contains double square brackets (as used in wiki’s) or double backslash or …, the text following those ‘special characters’ gets lost.
posted a bug on http://bugs.webkit.org/show_bug.cgi?id=14165 about it, really hope this gets solved.
September 6th, 2010 at 7:32 am
Migraine is een bonzende hoofdpijn die meestal voorkomt aan één kant van de schedel. De pijn is heftig en houdt 4 tot 72 uur aan.