Re: [webkit-dev] EFL port?

2017-02-13 Thread Gyuyoung Kim
Hi, I agree that we should have enough people to keep EFL port on upstream. Unfortunately I guess there will be no enough people to maintain EFL port even If I've done my internal work. So, If other maintainers or volunteers put their hand up for EFL port, it seems to me that EFL port has a time

Re: [webkit-dev] EFL port?

2017-02-13 Thread Gustavo Sverzut Barbieri
Hi guys, I have a small team working with WebKit-EFL as well, we're working on a different platform supported by EFL but not WebKit-EFL, so it's a series of minor patches to allow WebKit-EFL to run on Fbdev and without GL stack. Patches will reach bugs.webkit.org soon. On Sat, Feb 11, 2017 at

Re: [webkit-dev] CSS Parse error in element.

2017-02-13 Thread Atul Sowani
@Konstantin Thanks for the update and it is definitely relieving to know that those were known issues and have been fixed in later version of QtWebKit. I will work with PhantomJS maintainers to get the QtWebKit version upgraded in the latest PhantomJS version. Thanks! On Mon, Feb 13, 2017 at

Re: [webkit-dev] CSS Parse error in element.

2017-02-13 Thread Konstantin Tokarev
13.02.2017, 11:52, "Atul Sowani" : > I am using Qt 5.5.1. It ships with obsolete WebKit version based on trunk from 2013. Indeed it is known to have assertion failures related to calc like those you've posted, which were fixed since that times. Please upgrade to QtWebKit

Re: [webkit-dev] CSS Parse error in element.

2017-02-13 Thread Atul Sowani
I have been debugging on the CSS Parser issue and what I observed is similar to issue described at http://stackoverflow.com/questions/27256849/it-is-possible-to-use-vh-minus-pixels-in-a-css-calc For example, the CSS parser is crashing while processing following: height:calc(100vh - 200px) I

Re: [webkit-dev] CSS Parse error in element.

2017-02-13 Thread Atul Sowani
I am using Qt 5.5.1. On Thu, Feb 9, 2017 at 10:15 PM, Simon Fraser wrote: > What WebKit revision are your sources based on? It's quite likely the this > bug has been fixed. > > Simon > > On Feb 9, 2017, at 4:09 AM, Atul Sowani wrote: > > Finally I