Re: [webkit-dev] Proposal: Remove TextureMapperImageBuffer

Hi all, After llvmpipe(Mesa) is blacklisted in EFL (after bumped up EFL), I couldn’t fix regressions related with TextureMapper and CoordinatedGraphics in EFL port. I agree to remove TextureMapperImageBuffer and disable accelerated compositing in EFL port for awhile. Gyuyoung, could you find o

Re: [webkit-dev] Proposal: Remove TextureMapperImageBuffer

Hello Martin, I and Ossy have maintained EFL bots and EWS so far. Recently WebGL feature has been broken on EFL port since we bumped EFL version to 1.11.2. That's why we skipped to run WebGL tests on EFL layout test. - https://trac.webkit.org/changeset/167345. But, unfortunately I'm not sure when

Re: [webkit-dev] Clarifying 3D feature defines

Thanks for bringing up the point about perspective versus 3D transforms. For the sake of clarity, one reason 3D_GRAPHICS may be different from WebGL is that GraphicsContext3D is used to render accelerated compositing contents when using the TextureMapper and not simply WebGL. --Martin On Thu, Apr

Re: [webkit-dev] Clarifying 3D feature defines

On Apr 23, 2015, at 4:39 PM, Martin Robinson wrote: > > In the process of cleaning up and dusting off the GTK+ cmake build > system, we have rediscovered the pair of somewhat confusing feature > defines WTF_USE_3D_GRAPHICS and ENABLE_3D_RENDERING. From a brief > audit, it appears that WTF_USE_3D_

[webkit-dev] Clarifying 3D feature defines

In the process of cleaning up and dusting off the GTK+ cmake build system, we have rediscovered the pair of somewhat confusing feature defines WTF_USE_3D_GRAPHICS and ENABLE_3D_RENDERING. From a brief audit, it appears that WTF_USE_3D_GRAPHICS is a generic flag for any kind of 3D rendering at all (

Re: [webkit-dev] [Proposal] Remove support for 'multipart/x-mixed-replace' main resources

> On Apr 23, 2015, at 1:07 PM, Brady Eidson wrote: > > >> On Apr 21, 2015, at 3:39 PM, Chris Dumez wrote: >> >> Hi, >> >> I would like to suggest we remove support for 'multipart/x-mixed-replace’ >> main resources while keeping support for multipart images. >> >> Based on Chrome usage data

Re: [webkit-dev] [Proposal] Remove support for 'multipart/x-mixed-replace' main resources

> On Apr 23, 2015, at 1:19 PM, Brady Eidson wrote: > >> >> On Apr 23, 2015, at 1:11 PM, Chris Dumez > > wrote: >> >> >> >>> On Apr 23, 2015, at 1:07 PM, Brady Eidson >> > wrote: >>> On Apr 21, 2015, at 3:39 PM, Chris Dumez >>>

[webkit-dev] Proposal: Remove TextureMapperImageBuffer

I'd love to coordinate with whoever is running the EFL bots to get a configuration that can run these tests with OpenGL. The WebKitGTK+ bots use llvmpipe to make this happen. --Martin On Thu, Apr 23, 2015 at 1:15 PM, Benjamin Poulain wrote: > It seems undesirable to use a completely different st

Re: [webkit-dev] Client Hints

+Ilya for spec related questions. Also, I forgot to mention it, but my intention is to implement the RW and DPR hints first, and see about the MD and RQ hints (which are newer to the spec) later on. On Thu, Apr 23, 2015 at 7:02 PM, Maciej Stachowiak wrote: > > Additional spec concerns: > > (1)

Re: [webkit-dev] [Proposal] Remove support for 'multipart/x-mixed-replace' main resources

> On Apr 23, 2015, at 1:11 PM, Chris Dumez wrote: > > > >> On Apr 23, 2015, at 1:07 PM, Brady Eidson > > wrote: >> >>> >>> On Apr 21, 2015, at 3:39 PM, Chris Dumez >> > wrote: >>> >>> Hi, >>> >>> I would like to suggest we remove support f

Re: [webkit-dev] Proposal: Remove TextureMapperImageBuffer

It seems undesirable to use a completely different stack for testing and for shipping. Wouldn't it be possible to use Mesa on the EFL bots? On 4/23/15 12:10 PM, Martin Robinson wrote: A slight update on this issue. It's already been attempted here: https://bugs.webkit.org/show_bug.cgi?id=14356

Re: [webkit-dev] [Proposal] Remove support for 'multipart/x-mixed-replace' main resources

> On Apr 23, 2015, at 1:07 PM, Brady Eidson wrote: > >> >> On Apr 21, 2015, at 3:39 PM, Chris Dumez wrote: >> >> Hi, >> >> I would like to suggest we remove support for 'multipart/x-mixed-replace’ >> main resources while keeping support for multipart images. >> >> Based on Chrome usage da

Re: [webkit-dev] [Proposal] Remove support for 'multipart/x-mixed-replace' main resources

> On Apr 21, 2015, at 3:39 PM, Chris Dumez wrote: > > Hi, > > I would like to suggest we remove support for 'multipart/x-mixed-replace’ > main resources while keeping support for multipart images. > > Based on Chrome usage data, this feature is extremely rarely used by Web > sites (less than

Re: [webkit-dev] Proposal: Remove TextureMapperImageBuffer

A slight update on this issue. It's already been attempted here: https://bugs.webkit.org/show_bug.cgi?id=143561 The issue is that WebKitEFL is using the TextureMapperImageBuffer to run tests on their bots, because the EFL bots don't support OpenGL tests. My suggestion is that we disable accelerate

[webkit-dev] Proposal: Remove TextureMapperImageBuffer

Background: There currently exists a fallback TextureMapper implementation that does not use OpenGL to composite and project layers, but instead relies on 2D rasterization. This does not work correctly for Cairo, since Cairo only supports affine transformations. I believe this path is only used by

Re: [webkit-dev] Client Hints

Additional spec concerns: (1) The RW header is unimplementable because image requests are sent before the display width of the image is known. (2) The MD header is defined in a way that’s probably not useful to rely on; if I’m on 802.11g on a home WiFi network where the next hop is a cable mod

Re: [webkit-dev] Client Hints

> On Apr 23, 2015, at 12:48 AM, Yoav Weiss wrote: > > Hi, > > As I've discussed during my session at the contributor's meetup, I'm > interested in implementing Client-Hints > in WebKit. > > For those unfamiliar with it, Client-Hints is a standa

[webkit-dev] Client Hints

Hi, As I've discussed during my session at the contributor's meetup, I'm interested in implementing Client-Hints in WebKit. For those unfamiliar with it, Client-Hints is a standard destined to improve content negotiation, and enable the browser to a