The "binary search" approach could possibly be automated by: http://search.cpan.org/~coke/App-SVNBinarySearch-v0.1.0/svn_binary_searc h
... of course assuming you have a test script that isolates the bug. (note svn_binray search has a dependency on http://search.cpan.org/~roode/Iterator-0.03/Iterator.pm) HTH Bradley -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext David D. Kilzer Sent: Thursday, February 09, 2006 3:03 PM To: Clayton Ferris Cc: [email protected] Subject: Re: [webkit-dev] help identifying a workaround for a known bug There are two approaches: 1. "Reduce" the problem to the smallest amount of HTML that still exhibits the problem, then post that information here. There are many open bugs on http://bugzilla.opendarwin.org/ that need reductions and that haven't been fixed yet, so I doubt anyone has time to re-reduce this issue. 2. Try a "binary search" of the nightly builds on http://nightly.webkit.org/ to find out which nightly this bug was fixed in. (Basically, try the newest build and the oldest build. The newest build should have the issue fixed, while the oldest build should not. Then choose a build half-way between these two by date, and try it. If it exibits the problem, choose a build half-way between that build and the oldest build, else choose a build half-way between that build and the newest build. Continue until you've found where the fix occurred.) If you find which nightly fixed the issue, you can isolate the WebKit fix to the changes between that build and the previous nightly. Then you can use Subversion to look at logs between those dates or revision numbers if they are SVN builds (these are just examples): svn log -v -r{2005-10-10}:{2005-10-11} svn log -v -r11935:11955 If the first nightly on that site had the problem fixed, then the fix was sometime between the open source release of WebKit and that first nightly. Dave On Thu, Feb 09, 2006 at 12:23:21PM -0700, Clayton Ferris wrote: > On this site: http://www.iirodesign.com/ there is a bug in the current > version of Safari, which has apparently been fixed in the nightly > builds. > > The bug is the large spaces which occur under the individual posts, > especially the first two. > > This space doesn't appear in any browser that I tried except Safari, > and like I said it also appears fixed in the nightly Webkit. > > Any ideas of what exactly this bug is, or how I can make it look right > in the released Safari version? > > thanks, > Clayton Ferris _______________________________________________ webkit-dev mailing list [email protected] http://www.opendarwin.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://www.opendarwin.org/mailman/listinfo/webkit-dev
