Zalan Bujtas | 18 Aug 20:14 2014


Hi Everyone,
I’d like to propose removing ENABLE(SUBPIXEL_LAYOUT), as every port has it enabled. As part of this
activity, I am planning to enable SATURATED_LAYOUT_ARITHMETIC by default.
Yong Li | 18 Aug 13:35 2014

Re: ftlopt merge - basically done

Has anyone managed to make an FTL build on Linux?

Yong Li
From: Sergio Villar Senin
Sent: ‎8/‎7/‎2014 11:58 AM
To: webkit-dev <at>
Subject: Re: [webkit-dev] ftlopt merge - basically done

On 06/08/14 23:35, Filip Pizlo wrote:
> Hi everyone,
> The JSC “ftlopt” branch is basically merged.  I think I have one more revision to merge over, and it is a minor one.  Please don’t land more things on the branch.  Landing on trunk is fine; it’s unlikely to get in my way as I merge the last revision over.
> Thanks to everyone who helped with diagnostic problems and fixing things!

For those not following the development in that branch, mind sharing
details about what that work was about?

webkit-dev mailing list
webkit-dev <at>
webkit-dev mailing list
webkit-dev <at>
Andy Estes | 18 Aug 08:54 2014

webkitbot unable to roll out patches

I tried using webkitbot tonight to roll out a patch, but it’s encountering an error running `update-webkit`.

[23:42:16]  <estes> webkitbot: rollout r172697 made two webarchive layout tests start flaking
[23:42:18]  <webkitbot> estes: Preparing rollout for ...
[23:42:39]  <webkitbot> Exception executing command: Failed to run "['Tools/Scripts/update-webkit']" exit_code: 1

Ossy rebooted the bot but the error persists. Perhaps something's gone wrong with the bot’s working copy?

webkit-dev mailing list
webkit-dev <at>
Osztrogonác Csaba | 15 Aug 11:10 2014

Mac WK1 EWS bots having issues


it seems the Apple Mac WK1 EWS bots have problems:

Last Pass: 11 hours, 57 minutes ago by webkit-ews-01
Unable to pass tests without patch (tree is red?)

Regressions: Unexpected text-only failures (30)
   compositing/plugins/composited-plugin.html [ Failure ]
   compositing/plugins/no-backing-store.html [ Failure ]
   compositing/plugins/small-to-large-composited-plugin.html [ Failure ]
   fast/frames/sandboxed-iframe-about-blank.html [ Failure ]
   fast/frames/sandboxed-iframe-navigation-allowed.html [ Failure ]
   fast/frames/sandboxed-iframe-plugins.html [ Failure ]
   fast/replaced/invalid-object-with-fallback.html [ Failure ]
   fullscreen/full-screen-plugin.html [ Failure ]
   http/tests/plugins/create-v8-script-objects.html [ Failure ]
   http/tests/plugins/cross-frame-object-access.html [ Failure ]
   http/tests/plugins/get-url-beforeunload-destroys-plugin.html [ Failure
   platform/mac/plugins/convert-point.html [ Failure ]
   platform/mac/plugins/supports-carbon-event-model.html [ Failure ]
   platform/mac/plugins/testplugin-onnew-onpaint.html [ Failure ]
   plugins/destroy-during-npp-new.html [ Failure ]
   plugins/destroy-plugin-from-callback.html [ Failure ]
   plugins/npruntime/browser-object-identity.html [ Failure ]
   plugins/npruntime/construct.html [ Failure ]
   plugins/npruntime/delete-plugin-within-invoke.html [ Failure ]
   plugins/npruntime/embed-property-equality.html [ Failure ]
   plugins/npruntime/embed-property-iframe-equality.html [ Failure ]
   plugins/npruntime/embed-property.html [ Failure ]
   plugins/npruntime/enumerate.html [ Failure ]
   plugins/npruntime/evaluate.html [ Failure ]
   plugins/npruntime/get-int-identifier-special-values.html [ Failure ]
   plugins/npruntime/get-property-return-value.html [ Failure ]
   plugins/npruntime/identifier-conversion.html [ Failure ]
   plugins/npruntime/invoke-browserfuncs.html [ Failure ]
   plugins/npruntime/invoke-default.html [ Failure ]
   plugins/npruntime/invoke.html [ Failure ]

It's so strange, because all (8) of the Mac WK1 EWS suffer
from this issue, but there isn't any failure on the buildbots.
How is it possible? I thought the buildbots and EWS bots
have exactly the same configuration.

Maybe is the culprit,
because there weren't any other relevant patch that time.

Rodrigo B Almeida | 14 Aug 19:08 2014

On the use of C++ exception handling

Dear all, I've been investigating the use of C++ exception handling constructs in open-source C++ projects (including webkit). Currently, I am conducting a survey on this subject and I would really appreciate if you could contribute to this research by answering a few questions.

The survey is available on-line:

All the best,

webkit-dev mailing list
webkit-dev <at>
Info | 14 Aug 13:09 2014

WebAudio time domain sample data range?

What is the range of the input sample data that the webaudio
implementation is dealing with (e.g. in  

Is it float values between -1 and 1, or is the data scaled

(I am trying to immitate the built-in logic of the AnalyzerNode, by  
running a JavaScript side FFT on the time domain data that I am  
getting in the "onaudioprocess" event of a ScriptProcessorNode. I am  
using all the scaling/transformation logic from RealtimeAnalyser.cpp  
but still my resuls are quite different from the built-in ones..)
Info | 14 Aug 13:08 2014

FFT normalization in RealtimeAnalyser

In order to understand the idiotic differences between the data ranges  
of the AnalyzerNode's getFloatFrequencyData() and  
getByteFrequencyData() APIs I finally found myself analyzing the  
WebKit sources:

What surprises me there is the:
     const double magnitudeScale = 1.0 / DefaultFFTSize;
which is used to normalize the FFT results (see  

Should the correct scaling factor not rather be: 2/actualFftSize?
Daryle Walker | 12 Aug 00:55 2014

How do I find a WebView's desired size?

This is for implementing the windowWillUseStandardFrame:defaultFrame: method on OS X, which enables the green button to do an optimized zoom.  How can I find out what height and width a WebView wants to be if it had infinite screen space?  If it negotiates the size instead, assume that the maximum width is X and height is Y (which I would compute within windowWillUseStandardFrame:defaultFrame:).  These views have scrollbars within their window, so they must have an internal notion of what size they want to be.

This has to work whether or not the WebView is showing either HTML or anything else.

Asking a similar question on the Cocoa list, a respondent lamented that web browsers these days just punt on the question and go full screen.  I don’t want to do that.

Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com 

webkit-dev mailing list
webkit-dev <at>
Koen Bok | 11 Aug 12:23 2014

WKWebView Inspector in my own app

I am looking how to show the inspector in my own mac desktop app with WKWebViews.

I think I need to initialize an XPC or http connection to a WKWebView and pass it to a new inspector instance, and then show it.

Can anyone maybe point me in the right direction?

webkit-dev mailing list
webkit-dev <at>
Osztrogonác Csaba | 7 Aug 08:13 2014

Re: Heads up: Incremental build issue on cmake (GTK/EFL) ports

Of course, I used the "Force Clean build" checkbox on as you mentioned. ;) So the buildbots
are happy now.

I sent this mail to let the developers know what should
they do if they run into this problem on local builds.

But unfortunately we aren't able to clean the EFL EWS,
only its maintainer can do it. Gyuyoung, could you kick
this bot please? (It seems GTK guys already fixed their EWS)


Ryosuke Niwa írta:
> You should be able to trgger clean builds on 
> <> once you login.  Or are you talking about 
> downstream bots GTK/EFL bots?
> On Wednesday, August 6, 2014, Osztrogonác Csaba <oszi <at> 
> <mailto:oszi <at>>> wrote:
>     Hi,
>     r171961 changed the path of the generated inspector files (because
>     of r171942) from WebKitBuild/Release/__DerivedSources/JavaScriptCore
>     to WebKitBuild/Release/__DerivedSources/JavaScriptCore/__inspector
>     But unfortunately the old generated files remained in the old
>     path which caused the following strange incremental build error
>     after r172129:
>     In file included from
>     /home/oszi/webkit/Source/__JavaScriptCore/inspector/__agents/InspectorAgent.h:35:0,
>                      from
>     /home/oszi/webkit/Source/__JavaScriptCore/inspector/__JSGlobalObjectInspectorControl__ler.cpp:35:
>     /home/oszi/webkit/WebKitBuild/__Release/DerivedSources/__JavaScriptCore/__InspectorJSBackendDispatchers.__h:89:18:
>     note:        virtual void
>     Inspector::__InspectorRuntimeBackendDispatc__herHandler::__getRuntimeTypeForVariableInTex__tRange(Inspector::ErrorString*__,
>     const WTF::String&, const WTF::String&, int, int, int, int,
>     WTF::String*)
>     To solve this problem, you should simple remove the following files
>     from WebKitBuild/Release/__DerivedSources/JavaScriptCore:
>     InspectorJSBackendDispatchers.__cpp
>     InspectorJSBackendDispatchers.__h
>     InspectorJSFrontendDispatchers__.cpp
>     InspectorJSFrontendDispatchers__.h
>     InspectorJSTypeBuilders.cpp
>     InspectorJSTypeBuilders.h
>     I triggered clean build on the buildbots to fix this issue, but
>     these files should be removed on the GTK and EFL EWS bots too.
>     br,
>     Ossy
>     _________________________________________________
>     webkit-dev mailing list
>     webkit-dev <at>
>     <>
> -- 
> Ryosuke Niwa
Daryle Walker | 7 Aug 04:00 2014

Is there a (JavaScript) to test out WebUIDelegate?

I’m trying out Cocoa with a mini web-browser project.  My document class holding a WebView object implements the WebUIDelegate informal protocol.  I could test out webView:createWebViewWithRequest: by visiting a page that sends all links to a new window/tab.  Twitter is a good example of this.  It was a pain finding a page with Javascript-generated messages to the status bar, needed to test webView:setStatusText:.  Is there a JavaScript test suite so I can try triggering any of the other WebUIDelegate calls.  So far I need:

- (WebView *)webView:(WebView *)sender createWebViewWithRequest:(NSURLRequest *)request;  // click links on Twitter
- (void)webViewShow:(WebView *)sender;  // need a case that doesn’t call webView:createWebViewWithRequest: first
- (void)webView:(WebView *)sender setStatusText:(NSString *)text;  // went to a JavaScript demo on status-bar messages
- (NSString *)webViewStatusText:(WebView *)sender;
- (BOOL)webViewIsStatusBarVisible:(WebView *)sender;
- (void)webView:(WebView *)sender setStatusBarVisible:(BOOL)visible;

I need a way to test the second function since it and the first function are usually called together, but my implementation of the first function automatically calls its own version of the second.  So I need a way to call the second function by itself.

Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com 

webkit-dev mailing list
webkit-dev <at>