Re: [webkit-dev] maximalOutlineSize inflate all RenderLayers

2015-07-06 Thread Simon Fraser
This is a well-known issue. Ideally outline size would be factored into visual overflow, but that’s a bit tricky because outline is weird and crosses between RenderObjects. https://bugs.webkit.org/show_bug.cgi?id=106397 > On Jul 6, 2015, at 9:2

[webkit-dev] maximalOutlineSize inflate all RenderLayers

2015-07-06 Thread Kim, NamHoon
Hi experts, While hacking composited layer in WebKit, I realized CSS outline style inflate size of all RenderLayers. Since WebKit has default css of 5px outline for focused element, focusing input in the below sample inflate the cyan box. This can reproduced in WK2 OSX port in r186227. .box {

Re: [webkit-dev] Support "registerProtocolHandler" in WebKit2

2015-07-06 Thread Gyuyoung Kim
>The custom protocol handler feature of the WebKit2 API is for the embedding native application to provide raw data to resource loads directly. >While tangentially related to how registerProtocolHandler would work for some uses, there’s numerous differences. If so, custom protocol handler feature

Re: [webkit-dev] JSC framework API proposal: setting a handler for enqueuing tasks

2015-07-06 Thread Geoffrey Garen
I’m suggesting a default runloop for non-web content. I haven’t read through the details of integrating with the web content definition of micro task. Geoff > On Jul 6, 2015, at 4:44 PM, Maciej Stachowiak wrote: > > > Should JS be defining an event loop abstraction that WebCore then uses? Th

Re: [webkit-dev] JSC framework API proposal: setting a handler for enqueuing tasks

2015-07-06 Thread Maciej Stachowiak
Should JS be defining an event loop abstraction that WebCore then uses? That would be weird, because the required behavior of the even loop in web content is chock full of issues that are not at all related to JavaScript. JSC doesn't even know enough to run microtasks at all the right times (fr

Re: [webkit-dev] JSC framework API proposal: setting a handler for enqueuing tasks

2015-07-06 Thread Geoffrey Garen
I think it would be better for JavaScriptCore to handle micro tasks natively. It’s not so great for each client to need to reinvent the microtask runloop abstraction. Geoff > On Jul 6, 2015, at 10:05 AM, Yusuke SUZUKI wrote: > > Hi WebKittens, > > I've landed the update of the ES6 Promise im

[webkit-dev] JSC framework API proposal: setting a handler for enqueuing tasks

2015-07-06 Thread Yusuke SUZUKI
Hi WebKittens, I've landed the update of the ES6 Promise implementation. Through this work, I've experimentally added the internal private function, @enqueueJob(JS function, JS array for arguments). This is corresponding to the ES6 spec EnqueueJob[1]. This EnqueueJob handler is now tightly integr

Re: [webkit-dev] Support "registerProtocolHandler" in WebKit2

2015-07-06 Thread Brady Eidson
> On Jul 1, 2015, at 7:42 PM, Gyuyoung Kim wrote: > > WebKit2 already has a similar feature, which is so-called *custom protocol* > enabled by Mac, Gtk and EFL ports. However the custom protocol feature > supports to register custom scheme > through API layer instead of JavaScript. The registe