The stress test EWS has some issue when dealing with testharness.js tests.
Every now and then it thinks it's a different type of test and it dumps
the layout tree, and it fails as the actual result has nothing to do
with a layout tree dump.
Actually it dumps an empty layout tree:
On 14/10/2020 03:12, Ken Russell wrote:
> On Tue, Oct 13, 2020 at 2:37 PM Konstantin Tokarev > wrote:
> 1. Workflow 1 - "Squash merge" policy
> * Whole PR is considered to be a single atomic change of WebKit
> source tree. If work is supposed to be
On 25/09/18 01:00, Ryosuke Niwa wrote:
> On Mon, Sep 24, 2018 at 1:26 AM Frédéric Wang > wrote:
> On 12/09/2018 23:48, Dean Jackson wrote:
> > What about testing?
> > You can turn both experimental and internal features on via
On 20/02/18 20:09, Michael Catanzaro wrote:
> ENABLE_CSS3_TEXT looks to be support for text-align-last and
> text-justify . Seems to be only partically implemented in WebKit. I
> guess this is the sort of thing that should probably be implemented
> eventually, so probably makes sense to keep
On 10/05/17 04:23, Ryosuke Niwa wrote:
> Continuing the tradition of a massive rename in
> I suggest we rename the top-level LayoutTests directory to something
> more descriptive of the current state.
> Some ideas:
Dunno if it was related to this or something else but planet.webkit.org
is not being updated since March 10, 2017.
webkit-dev mailing list
On 08/08/15 00:22, Dean Jackson wrote:
>> On 7 Aug 2015, at 2:44 AM, Christian Biesinger
>> Hi all!
>> We (blink) would like to unprefix the intrinsic sizing keywords:
>> We support them
On 03/05/16 17:12, Gyuyoung Kim wrote:
> In second issue case, although it looks there is no critical issue with
> new layout methods yet
> I think I need to check it further. But the issues won't appear on port
> which uses gaps painting.
Maybe I didn't explain myself properly, but the issue
On 03/05/16 15:24, Gyuyoung Kim wrote:
> I upload a patch to add a preference API in order to enable/disable the
> selection gap painting feature.
BTW, this has been removed from Chrome too past year:
On 30/04/16 00:17, Dean Jackson wrote:
> Please leave the build flag around. We probably need a bigger discussion
> on this, but for now we should have both a runtime flag and a build flag
> just in case a browser ships and doesn't want the feature compiled at all
> (reducing binary size).
as announced yesterday it seems that the WebKit prefixing policy has
been updated .
Right now CSS Grid Layout implementation is prefixed in WebKit and
behind a compilation flag.
We'd like to ask about the possibility to unprefix it and put it behind
a runtime flag (probably removing the
this is a new status review (last one was in August 2014 ) of the CSS
Grid Layout  implementation done by Igalia. We'll summarize the work
done during the past months and the plans for the future.
Of course, we'll be really happy to get any kind of feedback from the
On 11/07/14 22:38, Joseph Pecoraro wrote:
- GTK EWS bot has Unable to build without patch” with:
ninja: error: build.ninja:3225: lexing error
We found the problem and the EWS should be running properly again.
Who would be best to look into these issues? I thought there used
On 25/04/14 23:39, Benjamin Poulain wrote:
On 4/25/14, 5:21 AM, Javier Fernandez wrote:
If everybody agrees, we have a patch ready to do this change:
JFYI, we've just landed this change today (r167993).
Personally, I think you should remove the runtime flag, and be
On Mon, 2014-02-10 at 13:38 -0800, Benjamin Poulain wrote:
Can't we add a compile time flag instead?
The chromium patch you linked is inelegant and it touches some hot paths.
BTW, only with the compile flag the issue is not completely fixed.
For example you can enable the compile flag but
On 20/12/13 02:37, Yoshifumi Inoue wrote: I would like to provide
render tree iterator base rendered position from
Render Tree for TextIterator, Selection, and others. TextIterator is the
first client of its.
Ok, I guess that it could be something similar to the RenderIterator
On 19/12/13 02:17, Yoshifumi Inoue wrote:
Selection for Shadow DOM tree is similar to CSS Region. Shadow DOM tree
also randomizes rendering order against (shadow/non-shadow) DOM tree order.
Using render tree information for selection also allows us to handle
we've been working for a while in selection and CSS Regions.
Current implementation is working fine from the DOM tree point of view,
the retrieved content when you do a selection is right (fulfilling the
editing spec ).
However, in several use cases with CSS Regions, highlighted content
On 05/20/2013 04:48 PM, Brian Holt wrote:
Memory leak detection is a recurrent topic on this mailing list [1-5]
but at present there exists only support for the Mac leaks tool. The
de facto standard for memory checking and leak detection for Unix is
Valgrind and the goal of this
Mail list logo