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

07.08.2017, 23:15, "Michael Catanzaro" : > On Tue, Aug 1, 2017 at 8:57 AM, Dean Jackson wrote: >>  In general I think we should be more enthusiastic about removing >>  feature flags that are guarding core parts of the Web platform. Web >>  Timing is a

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

> On Aug 2, 2017, at 2:18 AM, Ryosuke Niwa wrote: > > 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 >>>

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

O Mér, 02-08-2017 ás 12:43 +0300, Konstantin Tokarev escribiu: > Also, AFAICS WebAudio is not widely used across the Web. Can anyone > point me to real > website which is not WebAudio demo but makes use of this API somehow? Check www.webaudioweekly.com for several examples. BR

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

Niwa <rn...@webkit.org>; Adrien Destugues <pulkoma...@gmail.com> Cc: WebKit-Dev <webkit-dev@lists.webkit.org> Subject: Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag? 02.08.2017, 09:19, "Ryosuke Niwa" <rn...@webkit.org>: > On

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

On Tue, Aug 1, 2017 at 7:54 PM, Maciej Stachowiak wrote: > Chromium Embedded Framework is an obvious comparison project for use cases > like that. CEF is arguably more popular as a bundled engine than WebKit, so > we probably don't need more flexibility than they provide. Does CEF

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

02.08.2017, 09:19, "Ryosuke Niwa" : > 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 >> >>  

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

> On Aug 1, 2017, at 11:18 PM, Ryosuke Niwa wrote: > > 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 >>>

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

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

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

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: >>> >>>

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: >

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"

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

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,

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

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

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

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

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

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

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

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

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

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 build systems by default, and we have not experienced any