Nightly Builds
Posted by Dave Hyatt on Wednesday, October 12th, 2005 at 2:56 pmYou can download nightly builds of WebKit as well as WebKit+SVG from the following URL.
http://nightly.webkit.org/builds/
The icons that you see on the site are what will actually appear in your dock, so the gold-rimmed icon and the gold-rimmed icon with the SVG label can be used to distinguish these builds from your built-in Safari install.
Help us test the latest builds!
October 12th, 2005 at 4:14 pm
I’ve just downloaded the latest nightly build to play around with the new css3-properties. It seems to me that the border-radius property would be more useful if the border would follow the edge of a rounded border. I realize this can be pretty hard to do with border-style set to wave but it would be useful even if it was limited to solid borders. It can be done by nesting element with different background colors but isn’t the whole point of the new border- and background-properties to avoid having to nest elements to get certain visual effects
Anyway, I’m really looking forward to the next version of Safari!
October 12th, 2005 at 4:42 pm
Well - you know how to make friends!
Thanks people.
October 12th, 2005 at 5:06 pm
Excellent!
October 12th, 2005 at 5:23 pm
cool
October 12th, 2005 at 6:10 pm
Gabrielf, it will. The border-radius property is only partially implemented right now. Only transparent borders are supported.
October 12th, 2005 at 8:31 pm
[...] ounced at the media event, but rather from the WebKit team. They announced today that the nightly builds of WebKit/Safari would be available for download in binary form. Sweetness. I am, right [...]
October 12th, 2005 at 9:39 pm
It would be awesome if the nightly page had an RSS feed.
October 12th, 2005 at 10:24 pm
Seems that the freshly-downloaded SVG build doesn’t display any of the SVG examples over at http://www.adobe.com/svg/examples.html properly.
October 12th, 2005 at 11:58 pm
Latest doesn’t play nicely with Gmail (ie none of the links work). Sorry to mention it if known already.
October 13th, 2005 at 1:32 am
Myrd - the Adobe SVG examples have a whole host of problems. SVG enabled Geckos won’t display most of them either.
October 13th, 2005 at 3:56 am
Any comments on Panther compatibility? Should I bother to download? If not - is it something planned for the future?
October 13th, 2005 at 6:09 am
I tried the latest WebKit+SVG build but does crash on this site: http://www.mactechnews.de/index.php?function=17&thread=37148&cat=8&answers=652 while the official WebKit release works just fine on that page.
Furthermore is the navigation bar at the bottom on http://tineoidea.de/start.htm not working, but it isn´t working in the official neither.
I don´t know where to post stuff like this so I hope it´s no prob. here.
October 13th, 2005 at 6:24 am
Nightly builds — great idea. Thanks!
October 13th, 2005 at 7:46 am
Does not work in 10.3.x, shame really, I was hoping for a way to tests my stuff in the new WebKit. Will wait till I buy Tiger though, i guess.
October 13th, 2005 at 5:29 pm
Nightly WebKit builds
The WebKit team announced a new site today where you can download nightly builds of the latest WebKit — very cool. I went ahead and wrote the following simple shell script to automate the process of downloading and installing the latest build:
…
October 13th, 2005 at 5:29 pm
[...] Nightly WebKit builds 13 Oct 2005 The WebKit team announced a new site today where you can download nightly builds of the latest WebKit — very cool. [...]
October 13th, 2005 at 10:07 pm
I grabbed the DrawTest.app and downloaded the W3C SVG tests to toy with. Many of these (animation, text, marker element, and filter tests) failed but these are probably expected fails at this point in development. While this helps me know “what to expect” so far in the svg progress, could I construct my own tests based on pieces of my own SVG code, dissect them and organize them in a manner like the W3C test suite? or is this app designed around specific test suites.
The “viewer” window is handy for looking or examining parts in detail. Deletion, re-arrangement, and selection work, but object creation or modification (via inspector) appear only partially there. Not sure if this is because these are bits ripped out from another tool that haven’t quite been excised or if the intent is to allow the tester to graphically toy with parts of an SVG doc with the inspector / dumping of code. Either goal is fine, but just curious which path this developer tool intends.
While I have gotten a hard crash in the WebKit + SVG app when trying to view the three Adobe SVG examples in succession, I haven’t yet gotten a crash in DrawTest.app from attempting to render an SVG example. I do get DrawTest.app crashes when customizing the toolbar in the viewer window but these are probably not related to the SVG rendering at all.
October 13th, 2005 at 10:52 pm
Safari Nightly Builds
You can now download Safari/Webkit and WebKit+SVG from http://nightly.webkit.org/builds. In order to distinguish these with the built-in Safari, the nightly builds Webkit are using gold-rimmed icons and gold-rimmed icon with SVG….
October 13th, 2005 at 10:56 pm
Just wanted to let people know that I have updated NightShift to version 1.2. It now handles the migrated nightly builds. If you don’t know what NighShift is, read on.
NightShift automatically downloads and updates WebKit, the Safari HTML rendering engine, to the latest nightly version. No user intervention is required, everything is fully automated.
* Downloads WebKit nightly build from web server (either standard or SVG version)
* Mounts the disk image
* Creates a backup archive of the previous Webkit on disk
* Copies the new nightly build to its default location (user-specified)
* Optionally launches the new version of WebKit
* Option to undo latest install and revert to last version
* Option to show the change log for past week
Versiontracker hasn’t updated the listing yet and MacUpdate is currently offline. Those who have NightShift 1.1 can update from within NightShift. New users can get a copy at http://homepage.mac.com/reinholdpenner
Enjoy, -Reinhold
October 13th, 2005 at 11:21 pm
It’s great to see the Shockwave 3D offset bug fixed at looooong last! But now there’s a cursor offset with Flash 8! Check this for instance: http://www.foon.co.uk/farcade/efri/ and roll over the buttons
October 13th, 2005 at 11:44 pm
In response to macnoid’s comments:
> Many of these (animation, text, marker element, and filter tests) failed but these are probably expected fails at this point in development.
Yes, many things are still broken. See the list of bugs:
http://tinyurl.com/athb7
> While this helps me know “what to expect� so far in the svg progress, could I construct my own tests based on pieces of my own SVG code, dissect them and organize them in a manner like the W3C test suite?
Yes you can, and you are *very encouraged* to do so. Drop us a line on the mailing lists or irc for more info.
> Deletion, re-arrangement, and selection work, but object creation or modification (via inspector) appear only partially there. Not sure if this is because these are bits ripped out from another tool that haven’t quite been excised or if the intent is to allow the tester to graphically toy with parts of an SVG doc with the inspector / dumping of code. Either goal is fine, but just curious which path this developer tool intends.
Yes all editing is esentially broken right now. We’re waiting on:
http://bugzilla.opendarwin.org/show_bug.cgi?id=4624
to fix it all again.
>While I have gotten a hard crash in the WebKit + SVG app when trying to view the three Adobe SVG examples in succession, I haven’t yet gotten a crash in DrawTest.app from attempting to render an SVG example. I do get DrawTest.app crashes when customizing the toolbar in the viewer window but these are probably not related to the SVG rendering at all.
These are bugs. We would be very interested in fixing these. Instructions on how to file WebKit bugs are available here:
http://webkit.opendarwin.org/quality/reporting.html
Thanks for testing WebKit+SVG!
October 14th, 2005 at 2:10 am
[...] t to prove a point WebKit Nightly Builds now more official hyatt announced on Surfin’ Safari that WebKit Nightly Builds now have a more official location. WebKit, W [...]
October 14th, 2005 at 3:38 am
[...] « gaim-vv merging back! Surfin’ Safari » Nightly Builds Surfin’ Safari » Nightly Builds The WebKit guys have been busy adding some CSS3 support and fixing th [...]
October 14th, 2005 at 11:25 am
If this is not too stupid of a question, I assume that these builds are generic, in that they are not targeted towards any particular processor. Would it be possible to optimize Webkit for the G5, for example? Would there be any benefit to doing so?
October 15th, 2005 at 3:41 pm
Is the SVG support not 100% supported? When I try to “visualize my friends” at facebook.com, the SVG doc loads fine, except shows no text where there should be.
October 16th, 2005 at 1:21 am
timmerk: that’s right, SVG support is not 100% complete.
October 20th, 2005 at 4:03 am
Well, I still have a small bug, probably WebKit related:
If you visit a site with text/plain content, for example:
http://g-rave.nl/files/ports/www-lynx-patch-xhtml
It is probably shown using the HTML parser, but it is sent with text/plain:
$ telnet g-rave.nl 80
Trying 83.98.131.212…
Connected to g-rave.nl.
Escape character is ‘^]’.
GET /files/ports/www-lynx-patch-xhtml HTTP/1.1
Host: g-rave.nl
HTTP/1.1 200 OK
Date: Thu, 20 Oct 2005 11:02:57 GMT
Server: xs-httpd/3.3 beta/0.30
Connection: close
Content-type: text/plain
[...]
Cool to see that the current snapshots pass Acid2. Wicked
October 20th, 2005 at 12:02 pm
For some reason I crash on the Macmall site with nightly webkit. The site gets to last part of loading and the webkit crashes and gives the option to close, report , reopen. Normal safari works fine on that site. I went thru and disabled the plugins and found it was the javascript causing the problem. With javascript turned off, the nightly works fine on macmall. All safari and java updates are installed. Using os x 10.42
October 21st, 2005 at 6:29 am
Been dying to use the nightly webkit builds for a couple of months, but am not able to give up the function of Saft which saves tabs upon crash or exit. The way I work is not conducive to working otherwise as I receive calls throughout the day and often have to drop safari in the middle of tasks and thus I accumulate a lot of open (and important) windows. It is burdensome to have to go back through history and dig them back up if a crash occurs or an accidental quit application is issued so I cannot live without saft, HOWEVER due to having so many windows open I am sure that I can be of more benefit in terms of tracking down memory leaks and such if you would but PLEASE add this one function to safari immediately (ie, save window and tab states). This would be the single-most beneficial function in a very long, long time for me in my safari usage and would free me from saft which is having some serious issues with PithHelmet at the moment as well.
October 23rd, 2005 at 8:02 am
@Scott: Please create a bug report if you see a problem with the nightly builds.
http://webkit.opendarwin.org/quality/reporting.html
Posting it as a comment here doesn’t guarantee that it will be addressed.
October 30th, 2005 at 11:13 pm
Not sure if this is a bug in WebKit, or simply the application wrapper, but every time I need to open an external link (Mail.app, RSS Menu, etc), it spawns a new copy of the app. I now have three separate copies of WebKit on my Dock. I didn’t realize OS X would allow that in the first place.
Any hope this can be fixed, or should I file a bug report on it?
April 26th, 2007 at 6:33 pm
The only thing that might prevent me from running WebKit Nightly Builds full time besides the occasional crash, is the lack of right click spell checking. It’s one of the best features of OS X in my mind and no browser is complete without it. But alas “Command :” shall have to do.