Re: [webkit-dev] Removing support for CSS regions

> On 2 Aug 2017, at 01:03, Ryosuke Niwa wrote: > > On Mon, Jul 31, 2017 at 1:49 AM, Andreas Kling wrote: >> Some time has passed, and it seems that adoption of CSS regions on the web >> is not gonna happen. >> >> Blink has long since removed their support. >> Firefox never supported it AFAIK.

Re: [webkit-dev] Removing support for CSS regions

> On 1 Aug 2017, at 15:38, Dean Jackson wrote: > > I've been told that Amazon's Kindle Cloud Reader uses CSS Regions if > available, and gets a significant performance boost. It has a fallback though. Hi Dean! I’ve WebInspected around in a few books using Kindle Cloud Reader and can’t find a

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

On Tue, Aug 1, 2017 at 10:41 PM, Adrien Destugues wrote: >> Some others I see: >> >> ENABLE_GEOLOCATION >> ENABLE_INDEXED_DATABASE >> ENABLE_CSS_SCROLL_SNAP >> ENABLE_WEBGL >> ENABLE_WEB_AUDIO > > At least these are still not implemented in the Haiku port. I know we > are not an upstream port anym

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> Some others I see: > > ENABLE_GEOLOCATION > ENABLE_INDEXED_DATABASE > ENABLE_CSS_SCROLL_SNAP > ENABLE_WEBGL > ENABLE_WEB_AUDIO At least these are still not implemented in the Haiku port. I know we are not an upstream port anymore and have little chance of being again as I'm slowly trying to catc

Re: [webkit-dev] Bring back ARMv6 support to JSC

Hi all. FYI, I keep the last weeks investigating the issue with ARMv6 IC and I was able to find the source of the bug and apply a quick fix to run benchmarks again to get results. I just ran V8Spider, Octane and Kraken by now and I'm attaching the results in this email. We found some test cases r

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

On Tue, Aug 1, 2017 at 11:55 PM, Adrian Perez de Castro wrote: Moreover, for the WebKitGTK+ disabling both ENABLE_VIDEO and ENABLE_WEB_AUDIO does not need GStreamer at all, which further reduces disk and memory usage. For example Buildroot includes a WebKitGTK+ recipe which can disable both [1

Re: [webkit-dev] Intent to implement WebKit for Windows ports

On Tue, 01 Aug 2017 22:50:35 +0100, Michael Catanzaro wrote: > I will just add that there are some WebKitGTK+ users who would love for > WebKitGTK+ to be supported on Windows once again. Evolution and GnuCash > come to mind. Having a working WinCairo port of modern WebKit would be > a huge step

Re: [webkit-dev] Removing support for CSS regions

On Mon, Jul 31, 2017 at 1:49 AM, Andreas Kling wrote: > Some time has passed, and it seems that adoption of CSS regions on the web is > not gonna happen. > > Blink has long since removed their support. > Firefox never supported it AFAIK. > (The new) IE has some amount of support behind a prefix,

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On Aug 1, 2017, at 6:55 PM, Adrian Perez de Castro wrote: > > Hello, > > On Tue, 01 Aug 2017 18:11:53 -0400, Maciej Stachowiak > wrote: > >>> On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev wrote: >>> >>> 02.08.2017, 00:49, "Sam Weinig" : > On Aug 1, 2017, at 6:

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

I’ve done some experiments with automagically building the unified source files. I have some data that I’ll share with the rest of WebKit when I have more information. But as a quick note, since my current approach to unified sources has the build system decide which cpp files to bundle together

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

Hello, On Tue, 01 Aug 2017 18:11:53 -0400, Maciej Stachowiak wrote: > > On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev wrote: > > > > 02.08.2017, 00:49, "Sam Weinig" : > >>> On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: > >>> > On 24 Jul 2017, at 22:44, Brian Burg wrote: > > >

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On Aug 1, 2017, at 6:32 PM, Konstantin Tokarev wrote: > > > > 02.08.2017, 01:12, "Maciej Stachowiak" >: >>> On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev wrote: >>> >>> 02.08.2017, 00:49, "Sam Weinig" : > On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: >>

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

On Tue, Aug 1, 2017 at 11:32 PM, Konstantin Tokarev wrote: That's not true for Windows, where each application is shipping its own libraries, and is also not true for macOS in case port other than Mac is used. And such "small" applications surely benefit from reduced size and reduced dependenc

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

On Tue, Aug 1, 2017 at 11:33 PM, Keith Miller wrote: P.S. There is also a reasonable chance that we will do some form of unified sources (compiling multiple cpp files at the same time). In that case we don’t need to change our config.h rules. Do you have experience with unified source builds

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

That’s right if we end up going with C++ modules. We will either need to produce a replacement for config.h or have all root headers (i.e. headers that don’t include any other WebKit headers) include config.h. This is because with C++ modules the rule is that you have to include what you use. C+

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

02.08.2017, 01:12, "Maciej Stachowiak" : >>  On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev wrote: >> >>  02.08.2017, 00:49, "Sam Weinig" :   On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: >   On 24 Jul 2017, at 22:44, Brian Burg wrote: > >   Hi WebKittens, > >  

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev wrote: > > > > 02.08.2017, 00:49, "Sam Weinig" : >>> On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: >>> On 24 Jul 2017, at 22:44, Brian Burg wrote: Hi WebKittens, In WebKit, the various web-exposed timing APIs

[webkit-dev] Introducing the BB++ Programming Language

Hi WebKit, You probably remember me as the author of Root.Ptr. It turns out I wrote a new programming language called "BB++" to wrap the proper usage of Root.Ptr, making applications as clean as Javascript but are as performant as C++ applications and benefit from a deterministic memory manag

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

01.08.2017, 16:58, "Dean Jackson" : >>  On 24 Jul 2017, at 22:44, Brian Burg wrote: >> >>  Hi WebKittens, >> >>  In WebKit, the various web-exposed timing APIs–Resource Timing, User >> Timing, and Navigation Timing are guarded by the ENABLE_WEB_TIMING feature >> flag. >> >>  It seems that ENAB

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On Aug 1, 2017, at 9:57 AM, Dean Jackson wrote: > > > >> On 24 Jul 2017, at 22:44, Brian Burg wrote: >> >> Hi WebKittens, >> >> In WebKit, the various web-exposed timing APIs–Resource Timing, User Timing, >> and Navigation Timing are guarded by the ENABLE_WEB_TIMING feature flag. >> >>

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

02.08.2017, 00:49, "Sam Weinig" : >>  On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: >> >>>  On 24 Jul 2017, at 22:44, Brian Burg wrote: >>> >>>  Hi WebKittens, >>> >>>  In WebKit, the various web-exposed timing APIs–Resource Timing, User >>> Timing, and Navigation Timing are guarded by the E

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

On Tue, Aug 1, 2017 at 10:39 PM, Michael Catanzaro wrote: We might want to keep ENABLE_GEOLOCATION since on our platform it pulls in a dependency that's not needed on embedded systems. I don't really care since I suspect it is small, but I bet somebody else will. I think this applies to ENABL

Re: [webkit-dev] Intent to implement WebKit for Windows ports

Hi Don! I will just add that there are some WebKitGTK+ users who would love for WebKitGTK+ to be supported on Windows once again. Evolution and GnuCash come to mind. Having a working WinCairo port of modern WebKit would be a huge step towards that. Although Igalia does not intend to maintain

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On Aug 1, 2017, at 6:57 AM, Dean Jackson wrote: > > > >> On 24 Jul 2017, at 22:44, Brian Burg wrote: >> >> Hi WebKittens, >> >> In WebKit, the various web-exposed timing APIs–Resource Timing, User Timing, >> and Navigation Timing are guarded by the ENABLE_WEB_TIMING feature flag. >> >>

Re: [webkit-dev] WebKit opengl

On Tue, Aug 1, 2017 at 9:13 PM, Nagendra K wrote: Hi Dean, Thanks for the reply. I actually have a embedded device with opengl es 1.1 and WebKit which is 7 years old, now requirement is to update the WebKit using the same opengles1.1 i.e. no option to update opengles1.1. So as you said we nee

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

We might want to keep ENABLE_GEOLOCATION since on our platform it pulls in a dependency that's not needed on embedded systems. I don't really care since I suspect it is small, but I bet somebody else will. And I'm not sure about ENABLE_WEBGL. We have it forced on always, but we do allow disabl

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

On Mon, Jul 31, 2017 at 1:27 PM, Darin Adler wrote: > We originally adopted this “config.h” style to make WebKit buildable with > autotools. Since that has not been a consideration for years I would be > willing to abandon this and change how we do things. > > I don’t think we should add lots of

Re: [webkit-dev] WebKit opengl

01.08.2017, 23:14, "Nagendra K" : > Hi Dean, > > Thanks for the reply. > I actually have a embedded device with opengl es 1.1 and WebKit which is 7 > years old, now requirement is to update the WebKit using the same opengles1.1 > i.e. no option to update opengles1.1. I bet your old WebKit was

Re: [webkit-dev] WebKit opengl

Hi Dean, Thanks for the reply. I actually have a embedded device with opengl es 1.1 and WebKit which is 7 years old, now requirement is to update the WebKit using the same opengles1.1 i.e. no option to update opengles1.1. So as you said we need opengles2 or opengl4 to upgrade WebKit as WebKit has

[webkit-dev] Intent to implement WebKit for Windows ports

Hi WebKittens, We over at Sony have been committing more resources to WebKit, from revitalizing the WinCairo port, rebooting the cURL network backend, and continued work on the PAL layer. We've had some developers looking at the possibility to move WinCairo from WebKitLegacy over to WebKit and

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

On 08/01/2017 08:25 AM, Darin Adler wrote: >> On Jul 31, 2017, at 2:04 PM, Michael Catanzaro wrote: >> >> On Mon, Jul 31, 2017 at 9:27 PM, Darin Adler wrote: >>> I don’t think we should add lots of includes of “config.h”, though. I think >>> we can come up with something better. >> >> Like what?

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

> On 24 Jul 2017, at 22:44, Brian Burg wrote: > > Hi WebKittens, > > In WebKit, the various web-exposed timing APIs–Resource Timing, User Timing, > and Navigation Timing are guarded by the ENABLE_WEB_TIMING feature flag. > > It seems that ENABLE_WEB_TIMING is turned on for Xcode and CMake bu

Re: [webkit-dev] WebKit opengl

> On 19 Jul 2017, at 12:21, Nagendra K wrote: > > Current build of WebKit using opengl and with custom port, all apps will > directly use the opengl calls to draw, making the opengl independent of > WebKit. > So if I upgrade the WebKit, will the latest WebKit require opengl for any of > the

Re: [webkit-dev] Opengl support in webkit

> On 21 Jul 2017, at 13:47, Nagendra K wrote: > > Hi , > > Does WebKit engine mandate to use any version of opengl? > Can we link any opengl which my platform has. As long as your OpenGL is compatible with OpenGL 4.0 and above, or OpenGL ES 2.0 and above, I think you'll be fine. Dean > >

Re: [webkit-dev] Removing support for CSS regions

I've been told that Amazon's Kindle Cloud Reader uses CSS Regions if available, and gets a significant performance boost. It has a fallback though. Also, it would be worth checking at least Apple's iBooks store for any content that might have used regions. It would be a shame if purchased books

Re: [webkit-dev] What's the rationale for not including config.h in any header files?

On 07/31/2017 11:16 PM, Maciej Stachowiak wrote: > > >> On Jul 31, 2017, at 5:04 PM, Michael Catanzaro wrote: >> >> On Mon, Jul 31, 2017 at 9:27 PM, Darin Adler wrote: >>> I don’t think we should add lots of includes of “config.h”, though. I think >>> we can come up with something better. >> >