hmmm, so does this mean we should be seeing Safari v68 soon? Not that i've seen anything later than v60 of course. Heres for hoping for tabbed browsing! ;)

Yeah, just what I wanted to ask. After Apple canceled the seed program, I guess the situation with all those hypothetical versions has gone worse. :)

So does one have to compile this and plug it into the contents of a Safari package to try it out?

Compiling as we speak - however, how does one figure out that everything is properly loaded, etc? Is there an about: protocol page that lets me know which webcore I'm using, etc?

Built them both - 4 warnings about prebinding on webcore, dropped them into a new safari.app, and it crashes immediatley. I'm no Obj-C guy, so I'm stuck.

Damn - maybe David can help out ? :-)

Compiled WebCore is 50MB?

See the bottom of this page.

http://www.mozillazine.org/weblogs/hyatt/WebCore/chapter1.html

OK, that's kinda weird. I had the same crashing problem, and webcore is now over 50MB. Strangely, it now works, although I don't think I changed anything. Is it really supposed to be 50MB?

A while ago I built the v65 webcore and javascriptcore frameworks and dropped them into v60 and got a crash, even though I followed that page. I eventually decided I did something wrong, since webcore was huge (something around the 50MB already mentioned here, IIRC), yet the v60 framework in Safari.app was 3-4MB, IIRC.

I didn't compile the webcore source, but a large build usually means that the target is development instead of deployment. Try changing that in the targets tab in ProjectBuilder.

Import JavaScriptCore and WebCore into their own projects in Project Builder, then select the "Targets" tab in the vertical tab menu on the left of the main window for each project. Expand "Build Styles" and select "Deployment". Then build away.

That will build both sans debug code, thus reducing size to something more familiar.

Forgive me for posting this here. Safari crashes 100% of the time when trying to load this URI: http://images.digitalexpressions.nu/showpic.php?PID=12352

So when I build my new Safari with the new webcore/javascript core, this page (the comments page) fails to load. Turning off popup blocking has no effect.

Oh well.

David.

Really, it's sort of evil to post that there's a new WebCore that we can barely use with the "current" v60 Safari. But we love you anyways.

Any chance on a public beta soon, so we can forget all of this "hypothetical build", "build your own WebCore" stuff? (I know, you have no control, and can't say anyway.)

BTW, I tried Phoenix recently. My, my, but I'm starting to recognize that Dave Hyatt feel. Between Phoenix, Chimera, and Safari, there are some very pronounced similarities in their spirit and design.

Keep up the great work, and as always, thanks for the blog!

Its 50MB due to debug symbols. Build it on the command line using the "pbxbuild install DSTROOT=/tmp" command. It will get stripped of debug symbols and end up in the /tmp folder. (no way to do an install build via the gui unless you set the DEPLOYMENT_POSTPROCESSING variable, but pbxbuild is simpler)

Some versions of Safari have variables that depend upon certain versions of JavaScriptCore and WebCore, so when you drop a new one in, it will crash.

If you don't have versions later than 60, you shouldn't bother unless you really know what you're doing.

I notice the Camino nightlies have adopted the Apple bookmark model - you click the sidebar button and the bookmarks appear in page like the Safari style.

ACK! This is BAD BAD BAD BAD BAD! I have a horror story for you all:

I've been running v67 and it's been working fine, but I've kept v64 stuffed as backup. I decided to install v68 WebCore and JavaScriptCore frameworks in v67. I stuffed v67 for backup, downloaded the frameworks, and compiled them as directed (set the build style to deployment, set build directory, set intermediate products to go in build directory, and compiled JavaScriptCore.framework first). I then dragged JavaScriptCore.framework and WebCore.framework into Safari's Frameworks directory.

I then ran Safari.

It bounced in the dock for about 10 seconds, then stopped bouncing. No crash message, no nothing. I tried again, it bounced 5 times and stopped. I looked in the console, it had a message something like the following:

dylb: /Applications/Safari.app can't open the file JavaScriptCore in /Library/Frameworks/JavaScriptCore.frameworks/Versions/A/ (file or directory missing, errno = 2)

Please note that it's not exact, because my console log was cleared when I restarted.

Anyway, the weird thing is it was looking in /Library/Frameworks for the file. I couldn't figure out why. First I looked in the JavaScriptCore.framework folder to make sure the aliases were set correctly. It all looked fine, but I recreated the aliases, just in case. I also unstuffed my backup v67 copy to compare it with the JavaScriptCore.framework in there. It looked exactly the same.

At this point, my friend emailed me a URL, which I clicked on my accident while trying to copy it. The 2nd copy of Safari started up, but it looked wrong. The site I tried to access had a favicon cached, so that was displayed, but the URL bar text was overlayed on top of the favicon (instead of being indented). Then, after a second, it crashed (null pointer at CFCreatePropertyListFromStream). I thought this was weird, as this was the clean backup.

I tried opening Safari without a URL and it worked fine. Except for 1 thing - in the bookmark menu, the items without a favicon weren't indented, so it looked weird. I tried loading a page and it crashed. I re-opened Safari and opened the snippets window and tried to render "test". It crashed. So basically, it crashed when it tried to render anything (always null pointer at CFCreatePropertyListFromStream)

I tried different things to fix this. I first moved the compiled frameworks back into the folder I built them into and deleted both copies of Safari, and re-unstuffed v67. Still crashed.

I think renamed the frameworks to have .bak at the end, so they wouldn't look like frameworks anymore. I threw away Safari and re-unstuffed v67. I ran it. It was worse. The URL bar text started halfway across the URL bar. It looked weird, and still crashed.

I deleted the frameworks (and cycled Safari again), the URL bar was back to previous behaviour, but still crashed.

I deleted Safari and tried v64. Still crash.

I removed preferences and cache, cycled Safari (v67 again), still crash.

I created a new user, logged in as that, still crash.

I restarted, logged in as the new user, still crash.

I've flushed out every bit of v68 code from my system. I've restored Safari from 2 different backups repeatedly. I've restarted, used a new user. Everything I do results in Safari crashing at the same spot when it tries to render.

Now, finally, I went and re-downloaded the 2-12-03 public beta (i.e. v60) from apple's website. THAT works. But v67 and v64 still don't work. What could possibly be going on here?

Update:

I went and re-downloaded v67. It works fine. But it didn't when I unstuffed it from my stuffed backup copy (and neither did v64, which has been backed up since I got v67, so it couldn't possibly have been modified). Very weird.

Still, I'm not going to try to install WebCore.framework again, and I would really love an explanation as to what happened.

so kevin, i guess you know now why apple releases only SOME public betas. stick to them or stop complaining!

v67 + v68 plays very nice indeed. (Lots of this though 2003-03-26 23:27:19.566 Safari[3227] *** -[WebBridge formIsLoginForm:]: selector not recognized ) - backspacing in forms does not work however..

Actually I take that back Autocomplete is broken...
But all I was interested in anyway was the CSS Parser - Keep up the good work !

New Safari in Softwareupdate panel this morning.

OPPS, It was verion 60. I don't know why it showed a necessary update. I just rebuilt my system in the last couple of days. But I had v60 installed in the App. folder.

Sorry, I will be much more careful in the future.

I compiled v68 and dropped into /Library/Frameworks as per Twirlip of the Mists /. journal log. The most obvious problem seems to be that backspace no longer works in any text entry form. For example, google search form.

I am running v67 Safari.

It seems the file uploads don't work in 67 ( But did in 60 ) ie I'm really looking forward to the next public beta.

I do not know whether this is a WebCore issue -- but in Safari v60 scrolling within frames is extraordinarily slow (at least compared to the scrolling speed with sites that do not use frames).

Actually, scrolling is sluggish enough so that I find using phpMyAdmin or browsing the Java API (which both make use of frames) a real pain on my iBook 600.
BTW: Slow scrolling is also true for embedded HTML views (created with the iframe tag).
I would be very nice to have this issue fixed in the next public beta/the final version.

Bugs on WebCore 68: the backspace, arrow keys don't work for input type="text" when autocompletion is enabled and the input type="file" doesn't work at all.

Not just backspace, the tab key is ignored as well. File upload stops working since v67.

Does the imminence of the new release, as well as me being the only person not to have a pirated build and so be using v60, mean there is no point in submitting bug notices for v60 any more?

i'll definitely check it out