Re: [webkit-dev] Building Webkit
Hi,
Are you running the build-webkit and other commands from your Cygwin shell?
The directions don't seem to explicitly state that this is necessary, but
it is!
Set the environment variables in the Control Panel | System Properties
utility. Click on the 'Advanced' tab, select the Environment Variables
button, and add the variables to the User variables for a21612 window:
WebKitLibrariesDir | {Path to WebKit}\WebKitLibraries\win
WebKitOutputDir| {Path to WebKit}\WebKitBuild
-Brent
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] No more javascript parsing errors in console
Adam Roben [EMAIL PROTECTED] wrote: David Kilzer wrote: This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used http://www.dmregister.com/ to test.) I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors. It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug. Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors. JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2. Dave ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] No more javascript parsing errors in console
On Mar 28, 2008, at 9:36 AM, David Kilzer wrote: Adam Roben [EMAIL PROTECTED] wrote: David Kilzer wrote: This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used http://www.dmregister.com/ to test.) I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors. It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug. Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors. JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2. It's worth emphasizing that the comment still applies, though, to the JavaScript parsing error problem. If there's a bug, please file a bug report. Bug reports sent only to the mailing list aren't as good and usually don't result in a fix. -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] No more javascript parsing errors in console
In fact, it's the other 'round: Javascript console does not show parsing error if opened before page load. Filed a bug at http://bugs.webkit.org/show_bug.cgi?id=18182 Max Barel _ Développement web2, XHTML, CSS, PHP/MySQL, JavaScript, Ajax http://ac-mb.info Le 28 mars 08 à 17:36, David Kilzer a écrit : Adam Roben [EMAIL PROTECTED] wrote: David Kilzer wrote: This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used http://www.dmregister.com/ to test.) I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors. It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug. Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors. JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2. Dave ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
