> On Jun 10, 2019, at 6:10 PM, Yusuke Suzuki wrote:
> Congrats! :D
>> On Jun 10, 2019, at 3:49 PM, Saam Barati wrote:
>> Hi folks,
>> Tadeu and Robin are both now WebKit reviewers. Join me in congratulating
>> them. Please ask them to review your code! They both
> On Jun 10, 2019, at 3:49 PM, Saam Barati wrote:
> Hi folks,
> Tadeu and Robin are both now WebKit reviewers. Join me in congratulating
> them. Please ask them to review your code! They both have a focus in JSC.
> - Saam
Tadeu and Robin are both now WebKit reviewers. Join me in congratulating them.
Please ask them to review your code! They both have a focus in JSC.
webkit-dev mailing list
On 10/06/2019 17:31, Maciej Stachowiak wrote:
> Since SVG WG resolved to remove it, has it in fact been removed from
> the SVG spec?
Right, compare SVG 2 (W3C Recommendation 04 October 2018):
and SVG 1.1 (W3C Recommendation 16 August
On Sat, Jun 8, 2019 at 5:37 PM Konstantin Tokarev wrote:
> 04.06.2019, 02:41, "Ryosuke Niwa" :
> > I assume you want to use this feature. What are your use cases?
> Actually, I was just rambling through web-platform-tests and discovered
> thing I wasn't aware of,
> which seemed to be on
The one remaining thing we could potentially worry about is platform-specific
content, like books or content embedded in apps. But given what
SVGTests.hasExtension() is supposed to do, that seems very unlikely.
Since SVG WG resolved to remove it, has it in fact been removed from the SVG
On Mon, Jun 10, 2019 at 10:33 AM Adrien Destugues
> On Mon, Jun 10, 2019 at 09:37:06AM +0300, Noam Rosenthal wrote:
> > ~ (reposting from webkit email)
> Another limitation we hit on some websites is that it is not possible
> for us to create too many drawable offscreen bitmaps.
FWIW, here's the original intent to remove it from Chromium:
We had use counters, and I wrote "Usage is zero for all of them."
When concerned about usage in the wild, the tool we usually use for
On Mon, Jun 10, 2019 at 09:37:06AM +0300, Noam Rosenthal wrote:
> ~ (reposting from webkit email)
I should pprobably give a little more context here, as the maintainer of
the WebKitLegacy port for Haiku.
Our main concern, as Rajagopalan mentionned, is that Haiku does not have
>btw I might be able to help out (no promises), I haven't touched WebKit
code in a few years but I was responsible for TextureMapper and the
coordinated graphics system and I like bizarre >projects (a Haiku port
sounds like one). Let's see how it goes :)
Sure thank you for very great insite will
~ (reposting from webkit email)
I suggest starting by learning one of the other ports - like GTK - how the
whole flow works from the windowing system to WebCore to the graphics
system. Read the code, run it in debug mode and put breakpoints, get those
aha moments of how it all works
A quick look back on what we have done so far. We are trying to port
webkit2 to haiku and we have a working IPC with us. So the next step i
presume is to be rendering.
I did few amount of research and have few basic ideas. Correct me if I am
1) The rendering takes place
Mail list logo