Re: [webkit-dev] WebKit Documentation

> Why not double-down on the GitHub wiki? It's very easy to learn to use, > and there are edit buttons everywhere so there is no "distance" between > the docs and the ability to edit them. The easier it is to edit docs, > the better we'll do at keeping them up to date. > > I like Markdown, and

Re: [webkit-dev] Shrinking Git clone size (WebKit Transition to Git)

19.10.2020, 07:38, "Ryosuke Niwa" : > Hi all, > > While we're making the transition to Git, I think we should try to > shrink the Git clone size. Right now, it's 10GB and I suspect we can > cut it down quite a bit without sacrificing much. For example, we can > exclude any history for

Re: [webkit-dev] WebKit Transition to Git

14.10.2020, 16:52, "Tetsuharu OHZEKI" : > I feel from this discussion that everybody has their own best way and > we’re tackling to resolve them at once in this migration process. > I also feel it’s a bit difficult to conclude something. > > FWIW, I would like to write some my problems about the

Re: [webkit-dev] WebKit Transition to Git

14.10.2020, 02:01, "Ryosuke Niwa" : > On Tue, Oct 13, 2020 at 3:53 PM Konstantin Tokarev wrote: >>  14.10.2020, 01:45, "Ryosuke Niwa" : >>  > On Tue, Oct 13, 2020 at 3:40 PM Konstantin Tokarev >> wrote: >>  >> 14.10.2020, 01:30, &

Re: [webkit-dev] WebKit Transition to Git

14.10.2020, 01:45, "Ryosuke Niwa" : > On Tue, Oct 13, 2020 at 3:40 PM Konstantin Tokarev wrote: >>  14.10.2020, 01:30, "Ryosuke Niwa" : >>  > On Tue, Oct 13, 2020 at 2:37 PM Konstantin Tokarev >> wrote: >>  >> 13.10.2020, 22:33, &qu

Re: [webkit-dev] WebKit Transition to Git

14.10.2020, 01:30, "Ryosuke Niwa" : > On Tue, Oct 13, 2020 at 2:37 PM Konstantin Tokarev wrote: >>  13.10.2020, 22:33, "Maciej Stachowiak" : >>  >> On Oct 2, 2020, at 10:59 AM, Michael Catanzaro >> wrote: >>  >> >>  >> On

Re: [webkit-dev] WebKit Transition to Git

13.10.2020, 22:33, "Maciej Stachowiak" : >>  On Oct 2, 2020, at 10:59 AM, Michael Catanzaro wrote: >> >>  On Fri, Oct 2, 2020 at 6:36 pm, Philippe Normand wrote: >>>  Would you also consider preventing merge commits in order to keep a >>>  clean mainline branch? >> >>  Big +1 to blocking merge

Re: [webkit-dev] WebKit Transition to Git

06.10.2020, 18:03, "Michael Catanzaro" : > On Tue, Oct 6, 2020 at 3:13 am, Konstantin Tokarev > wrote: >>  1. Sub-par support for linking issues to each other >>   >> >>  Traditional bug track

Re: [webkit-dev] WebKit Transition to Git

06.10.2020, 20:32, "Yusuke Suzuki" : >>  On Oct 5, 2020, at 5:13 PM, Konstantin Tokarev wrote: >> >>  05.10.2020, 23:41, "Yusuke Suzuki" : >>>  I think security component is special in terms of how to handle it already >>> (e.g. not post

Re: [webkit-dev] WebKit Transition to Git

06.10.2020, 12:40, "Konstantin Tokarev" : > 06.10.2020, 11:42, "Ryosuke Niwa" : >>  On Mon, Oct 5, 2020 at 5:13 PM Konstantin Tokarev wrote: >>> >>>   1. Sub-par support for linking issues to each other >>>   --

Re: [webkit-dev] WebKit Transition to Git

06.10.2020, 11:42, "Ryosuke Niwa" : > On Mon, Oct 5, 2020 at 5:13 PM Konstantin Tokarev wrote: >>  05.10.2020, 23:41, "Yusuke Suzuki" : >>  > I think security component is special in terms of how to handle it >> already (e.g. not posting a test wi

Re: [webkit-dev] WebKit Transition to Git

05.10.2020, 13:26, "Frédéric Wang" : > One thing to take into account is that WebKit's repository is big and > public GitHub/GitLab prevent creating large repository by default. This > means it might not be possible for contributors to actually fork > WebKit's repository on their account and

Re: [webkit-dev] WebKit Transition to Git

05.10.2020, 17:19, "Robert Ma" : > On Mon, Oct 5, 2020 at 6:22 AM Frédéric Wang wrote: >> One thing to take into account is that WebKit's repository is big and >> public GitHub/GitLab prevent creating large repository by default. This >> means it might not be possible for contributors to

Re: [webkit-dev] WebKit Transition to Git

05.10.2020, 23:41, "Yusuke Suzuki" : > I think security component is special in terms of how to handle it already > (e.g. not posting a test with the patch etc.) > To me, handling non-security issues in GitHub and security issues in Bugzilla > is OK. > By nature, security issues are not open.

Re: [webkit-dev] WebKit Transition to Git

02.10.2020, 19:46, "Jonathan Bedard" : > Monotonic Commit Identifiers > Of great interest to Apple’s engineers has been retaining some kind of > ordered tag we can use to refer to commits to make defending CI and bisection > easier. We’ve developed a scheme for this that assigns commits an

Re: [webkit-dev] WebKit Transition to Git

03.10.2020, 21:49, "Adrien Destugues" : > Yes that's why I didn't elaborate much. Whichever tool you pick, there > will always be people unhappy about it. Right. For example, I have negative bias against GitLab, because this company have bought its open source competitor (Gitorious, which was

Re: [webkit-dev] WebKit Transition to Git

02.10.2020, 23:17, "Jonathan Bedard" : >>  On Oct 2, 2020, at 11:47 AM, Tetsuharu OHZEKI >> wrote: >> >>  Hi Jonathan, >> >>  As a contributor, I hear this change positively and I'm looking >>  forward to transition to a new process. >> >>  I have some questions and feelings: >> >>  1. Will we

Re: [webkit-dev] WebKit Transition to Git

03.10.2020, 05:18, "Ryosuke Niwa" : > On Fri, Oct 2, 2020 at 5:06 PM Michael Catanzaro wrote: >>  On Fri, Oct 2, 2020 at 13:48, Ken Russell wrote: >>  > Github's code review UI has a couple of feature gaps in my opinion. >>  > It's difficult to look at earlier versions of the pull request, in

Re: [webkit-dev] WebKit Transition to Git

03.10.2020, 20:40, "Michael Catanzaro" : > On Sat, Oct 3, 2020 at 3:16 am, Ryosuke Niwa wrote: >>  I've gotta say I'm very much concerned about getting rid of change >>  logs when we move to Git. We put a lot of useful information about >>  what was causing the bug, how we fixed it, and why we

Re: [webkit-dev] WebKit Transition to Git

03.10.2020, 19:34, "Alexey Proskuryakov" : >>  3 окт. 2020 г., в 2:24 AM, Adrien Destugues >> написал(а): >> >>  On Fri, Oct 02, 2020 at 07:05:21PM -0500, Michael Catanzaro wrote:  I realize that Gerrit might not integrate at all with hosting the repo  on Github, but has any thought

Re: [webkit-dev] WebKit Transition to Git

03.10.2020, 19:46, "Tetsuharu OHZEKI" : >>>  I think having to create an account on a website isn't the main thing >>>  preventing people to contribute anyway? It's more about having to use >>>  project-specific tools to prepare the patch for submission (in the case >>>  of WebKit, having to

Re: [webkit-dev] Smart Pointer Analysis Tool for WebKit

17.09.2020, 09:35, "Ryosuke Niwa" : > Hi all, > > I’ve been working with Geoff (ggaren) and Jan Korous from Apple's compiler > team to create a static analyzer which detects dangerous use of ref counted > objects, and we’re looking for folks who are interested in trying out this > tool and

Re: [webkit-dev] Generating compile_commands.json when building WebKit on MacOS

20.07.2020, 13:13, "shriva...@firemail.cc" : > Hi webkit-dev, > > I'm trying to study the structure of web browsers in general and WebKit > specifically for academic purposes. I found that using language servers > that index compile_commands.json (clangd, ccls etc.) is a very good > solution to

Re: [webkit-dev] Terminology: Could we change 'roll out' to 'roll back'?

07.03.2020, 05:41, "Kirsling, Ross" : > I'd be thrilled for us to use 'revert'. > Somehow I'd convinced myself that it'd be easier to ask for this if we kept > the 'roll' part, but I'm not really sure why I thought so. On the negative side, it won't be possible anymore to say that someone is

Re: [webkit-dev] Naming convention for static member variables

19.02.2020, 22:31, "Simon Fraser" : > class Foo { >   static bool thing. > }; > > What's the naming convention for static member variables like this? I've seen > m_foo, which seems positively harmful. I've seen s_foo, which I like. > > There are 165 instances of s_ that I can find in the

Re: [webkit-dev] Adrian Perez de Castro is now a WebKit reviewer

14.10.2019, 16:20, "Carlos Alberto Lopez Perez" : > Hi everyone, > > I would like to announce that Adrian Perez de Castro (aperezdc on #webkit) > is now a WebKit reviewer. > > Adrian has several years of experience working with the WebKitGTK and WPE > WebKit ports. He is the release manager of

Re: [webkit-dev] Can the WebKit logo be used for WebKit ports? (like WebKitGTK)

10.10.2019, 23:10, "Ryosuke Niwa" : > People often associate the term "WebKit" with Apple's WebKit port in > practice. The risk here is really about people not understanding the nuance > of port specific bugs & set of features. However, Safari has its own column in the table, and its logo is

Re: [webkit-dev] Questions about JSC EWS queues

18.09.2019, 20:24, "Aakash Jain" : > Hi All, > > I am working on moving JSC EWS queues from old EWS to new EWS. I am trying to > clearly understand various JSC EWS queues. I have few questions: > > 1) What does 'jsc-only' port represent? It is a port which aims to provide just JSC with minimum

Re: [webkit-dev] Moving to Python 3

16.07.2019, 14:33, "Guillaume Emont" : > Quoting Fujii Hironori (2019-07-16 08:04:09) >>  On Sun, Jul 14, 2019 at 7:44 AM Ryosuke Niwa wrote: >> >>  I don’t think anyone is arguing that we’d eventually need to move to >>  Python3. I’m arguing that it’s not okay to require random WebKit

Re: [webkit-dev] [CMake] Bump cmake_minimum_required version to 3.10

27.06.2019, 20:19, "Michael Catanzaro" : > On Thu, Jun 27, 2019 at 11:20 AM, Brent Fulgham > wrote: >>  Apple is in the process of bringing up VS2019 now. I would be in >>  favor of moving the minimum to 3.14 so we can safely support VS2019 >>  compiles. > > The 3.14 target is too aggressive

Re: [webkit-dev] What is the status of Network Error Logging and Reporting API?

ever, I think this feature could be useful as a lightweight inspector replacement for embedded systems which are deployed to clients, when it may not be easy to make a direct connection. > > On Sun, Jun 2, 2019 at 6:16 PM Konstantin Tokarev wrote: >> They are missing from features.json &g

[webkit-dev] What is the status of Network Error Logging and Reporting API?

They are missing from features.json https://w3c.github.io/network-error-logging/ https://www.w3.org/TR/reporting/ -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] C++17 is here. Should we use it?

11.05.2019, 02:47, "Yusuke Suzuki" : > Cool! So, > > 1. We can use GCC 7 > 2. We can use libstdc++7 > > Is my understanding correct? Basically, this means that we can use cool C++17 > features super aggressively :) Not so aggressively with library features, a few of them require libstdc++ 8

Re: [webkit-dev] C++17 is here. Should we use it?

07.05.2019, 16:53, "Michael Catanzaro" : > Since there were no objections, I've updated the policy on the wiki: > > https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy > https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement Note that since we have to support libstdc++ 6.x, most of C++17

Re: [webkit-dev] C++17 is here. Should we use it?

20.04.2019, 01:16, "Alex Christensen" : > It’s always fun to reply to two year old emails. > > I would like to have a plan to start using and requiring C++17 in WebKit. > Based on my minimal research, I believe that DebianBuster is frozen but not > yet released. Is there something we are still

Re: [webkit-dev] Spam and indexing

22.04.2019, 18:58, "Michael Catanzaro" : > Not indexing bugs.webkit.org will be sad for people who won't be able > to find bugs they may be interested in via search engines... but those > people are probably not WebKit developers working with WebKit on a > daily basis. For us, it's just

Re: [webkit-dev] Concurrent JS and 32bit platforms

11.04.2019, 17:03, "Xan" : > Hi all, > > as part of our work on improving 32bit support in JSC we at Igalia are > planning to have a look at enabling concurrent js for these platforms. Before > we dive in, though, we thought it would be better to ask some preliminary > questions: > > - Was

Re: [webkit-dev] Spam and indexing

29.03.2019, 19:30, "Michael Catanzaro" : > On Thu, Mar 28, 2019 at 3:57 PM, Alexey Proskuryakov > wrote: >>  2. Block indexing completely. >> >>  Seems like no one was bothered by lack of indexing on new bugs so far. > > Spam problem seems worse than not being indexed. > > If you want to search

Re: [webkit-dev] Spam and indexing

29.03.2019, 19:16, "Alexey Proskuryakov" : >> 28 марта 2019 г., в 14:10, Konstantin Tokarev написал(а): >> >> 28.03.2019, 23:58, "Alexey Proskuryakov" : >>> Hello, >>> >>> The robots.txt file that we have on bugs.webkit.org cu

Re: [webkit-dev] Spam and indexing

28.03.2019, 23:58, "Alexey Proskuryakov" : > Hello, > > The robots.txt file that we have on bugs.webkit.org currently allows search > engines access to individual bug pages, but not to any bug lists. As a > result, search engines and the Internet Archive only index bugs that were > filed

Re: [webkit-dev] Regarding problem in building webkit2

25.02.2019, 14:06, "Rajagopalan Gangadharan" : > Hello, > > I am trying to build webkit for haiku and I stumbled upon an error > > The error is in “Source\WebKit\UIProcess\WebsiteData\WebsiteDataStore.cpp” > line 2080 says about missing platformSetNetworkParameters function and I saw > it was

Re: [webkit-dev] Moving to Git

20.02.2019, 22:27, "Bug Tracker" : > Sorry, for the anonymous email. I opted for it because the list archives are > public and concluded that it's not that useful to reveal my identity for the > purposes of this question. > > In short, however, I am a graduate student interested in using

Re: [webkit-dev] 'final' class specifier and 'final' method specifier

20.12.2018, 09:17, "Fujii Hironori" : > Thank you very much for the feedbacks. > > On Thu, Dec 20, 2018 at 4:52 AM Konstantin Tokarev wrote: >> 19.12.2018, 12:53, "Fujii Hironori" : >>> I'd like to change this because 'final' doesn't necessa

Re: [webkit-dev] 'final' class specifier and 'final' method specifier

19.12.2018, 23:27, "Michael Catanzaro" : > On Wed, Dec 19, 2018 at 1:58 PM, Konstantin Tokarev > wrote: >>  Adding override to method which already has final specifier doesn't >>  affect anything, >>  because both final and override may ony be used on virtual

Re: [webkit-dev] 'final' class specifier and 'final' method specifier

19.12.2018, 21:02, "Darin Adler" : >>  On Dec 19, 2018, at 1:52 AM, Fujii Hironori >> wrote: >> >>  I'd like to change this because 'final' doesn't necessarily imply >>  'override'. See the following stackoverflow: >>  https://stackoverflow.com/questions/29412412/does-final-imply-override > >

Re: [webkit-dev] 'final' class specifier and 'final' method specifier

19.12.2018, 12:53, "Fujii Hironori" : > I'd like to change this because 'final' doesn't necessarily imply > 'override'. See the following stackoverflow: > https://stackoverflow.com/questions/29412412/does-final-imply-override It does imply override, unless it is used in a declaration of new

Re: [webkit-dev] Watch out for std::optional's move constructor

18.12.2018, 22:35, "Michael Catanzaro" : > I know I'm getting a bit far afield here, but: > > On Mon, Dec 17, 2018 at 9:26 PM, Ryosuke Niwa wrote: >>  But then our behavior of HashMap which doesn't accept the POD >>  integral value of 0 as a key > > This behavior is really unexpected and

Re: [webkit-dev] Lots of spam on Bugzilla

05.12.2018, 20:31, "Michael Catanzaro" : > On Wed, Dec 5, 2018 at 10:44 AM, ross.kirsl...@sony.com wrote: >>  You can click Tag and enter "spam". (There's also the "obsolete" tag >>  for hiding, say, outdated feedback from the EWS bots. Unfortunately >>  tagging is purely by manual entry right

Re: [webkit-dev] Rename wtf/unicode/UTF8.h

31.10.2018, 05:18, "Fujii Hironori" : > wtf/unicode/UTF8.h is conflicting with ICU header in MSVC builds. I'd like to > rename wtf/unicode/UTF8.h to wtf/unicode/WTFUTF8.h. > Any suggestion? What about Unicode.h or UnicodeHelpers.h? UTF8.h deals with UTF16 as well > > Here is ICU's #include

Re: [webkit-dev] Is gperf really needed when building the JSCOnly with CMake?

Or, better, if (ENABLE_WEBCORE) 30.09.2018, 18:58, "Michael Catanzaro" :Yeah, I'd just put it in an if (NOT ${PORT} STREQUAL "JSCOnly")(writing that off the top of my head, probably somehow wrong)___webkit-dev mailing

Re: [webkit-dev] Freenode spam counter-measure

nd wrote: >> >>> On 6 Aug 2018, at 16:12, Darin Adler wrote: >>> >>>> On Aug 6, 2018, at 5:22 AM, Konstantin Tokarev wrote: >>>> >>>>>> On Aug 5, 2018, at 2:38 AM, Philippe Normand wrote: >>>>>> >>>>

Re: [webkit-dev] Freenode spam counter-measure

06.08.2018, 01:21, "Darin Adler" : >>  On Aug 5, 2018, at 2:38 AM, Philippe Normand wrote: >> >>  Can one of the #webkit admin please set the +r mode on? This would help >> reducing spam. Only messages from registered nicks would come through. > > I tried this by typing this: > > /msg

Re: [webkit-dev] why the "WebKitStorageProcess”　process missing when midori running?

26.05.2018, 12:28, "tugouxp" <13824125...@163.com>: > Hi folks: > >    i porting the webkit to my boards, and also the browser midori and > minibrowser can be running normally, but from the pstree , > > i know that the process "WebKitStorageProcess“　are not running, so can you > tell me why?

Re: [webkit-dev] Switch to std::variant?

23.05.2018, 18:40, "Michael Catanzaro" : > On Wed, May 23, 2018 at 6:14 AM, z...@falconsigh.net wrote: >>  Some GCC-and-libstdc++ configurations would still require a fallback >>  implementation > > After the std::optional fiasco, I'm pretty nervous about the state of >

Re: [webkit-dev] [jsc-dev] Proposal: Removing ENABLE(INTL)

21.05.2018, 17:45, "Michael Catanzaro" <mcatanz...@igalia.com>: > On Mon, May 21, 2018 at 8:55 AM, Konstantin Tokarev <annu...@yandex.ru> > wrote: >>  For the record, having !ENABLE(INTL) option allowed to build WebKit >>  against old ICU versions,

Re: [webkit-dev] [jsc-dev] Proposal: Removing ENABLE(INTL)

19.05.2018, 14:12, "Yusuke SUZUKI" : > Hi WebKittens, > > I would like to remove ENABLE(INTL) compile time flag and always enable INTL. > This is ECMAScript Intl (i18n) feature. This feature depends on ICU. > But right now, even JSC (and WTF) always require ICU. Even if we

Re: [webkit-dev] New iOS versions sending bogus User-Agent build data

26.04.2018, 20:09, "Colin Bendell | +1.613.914.3387" <co...@bendell.ca>: > On 26 April 2018 at 12:23, Konstantin Tokarev <annu...@yandex.ru> wrote: >>  Not to mention those evil people who reject page loading for user agents >>  they don't (want to) supp

Re: [webkit-dev] New iOS versions sending bogus User-Agent build data

26.04.2018, 19:16, "Michael Catanzaro" : > On Thu, Apr 26, 2018 at 11:13 AM, Michael Catanzaro > wrote: >>  By fixing the WebKit bug, of course. And in the meantime you can work >>  around it on the server side by not using img src=mp4, right? > >

Re: [webkit-dev] New iOS versions sending bogus User-Agent build data

26.04.2018, 13:08, "Ricky Young" : > Until iOS 11.3, User-Agent build data contained the build that corresponds to > the device (e.g. Mobile/15D100 if the requesting device was running iOS > 11.2.6). > > Since iOS 11.3 was released I noticed that the User-Agent that is reported

Re: [webkit-dev] Compiling Webkit --wincairo

19.04.2018, 17:24, "Barone Ashura" : > Hello, > > I would like to understand how can I control the build process for building > Webkit-cairo on windows. > > As of now I managed to successfully compile/integrate/link/execute a source > tree downloaded from git using the

Re: [webkit-dev] python2

10.04.2018, 23:38, "Michael Catanzaro" : > Hi, > > python2 end of life is January 1, 2020. But even before then, we'll need to > make WebKit work in environments without python2 available, because it's not > going to be present in the next Red Hat Enterprise Linux or

Re: [webkit-dev] Using compile_command.json in sources that go into Unified Sources

26.03.2018, 16:31, "Adrian Perez de Castro" : > On Mon, 26 Mar 2018 07:54:38 -0500, Michael Catanzaro > wrote: >>  On Sat, Mar 24, 2018 at 6:03 PM, Cadu Bentzen >>  wrote: >>  > I included calling this script at the end of the

Re: [webkit-dev] Meltdown and Spectre attacks

05.01.2018, 20:28, "Michael Catanzaro" <mcatanz...@igalia.com>: > On Fri, Jan 5, 2018 at 10:31 AM, Konstantin Tokarev <annu...@yandex.ru> > wrote: >>  Seems like both mitigations are already present in trunk > > Are there recent commits you can link to?

Re: [webkit-dev] Meltdown and Spectre attacks

> Hi, > > Here's a collection of blog posts from other major browser vendors > regarding the Meltdown and Spectre attacks: > > https://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/ > >

Re: [webkit-dev] Exporting WPT tests

21.12.2017, 04:29, "youenn fablet" : > Hi all, > > Just to let you know that a new script landed in WebKit: > Tools/Scripts/export-w3c-test-changes. > Please have a look if you are interested in and ping me if you have any > question or suggestion. > This script can: > -

Re: [webkit-dev] Buildbot upgrade on build.webkit.org

11.12.2017, 02:49, "Carlos Alberto Lopez Perez" : > On 07/12/17 21:47, Aakash Jain wrote: >>  For people using build.webkit.org , I would >>  like to know what pages you use most of the time (e.g.: builder page, >>  console view etc.) and what are

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

  08.12.2017, 20:18, "JF Bastien" :Also, as we discussed on the github bug the JSC binary is available as part of the WebAssembly waterfall that Google maintains at wasm-stat.us The build is pretty

Re: [webkit-dev] Upstreaming from LayoutTests to web-platform-tests, coordinating Blink+WebKit

17.11.2017, 18:19, "Maciej Stachowiak" <m...@apple.com>: >>  On Nov 17, 2017, at 7:15 AM, Konstantin Tokarev <annu...@yandex.ru> wrote: >> >>  16.11.2017, 20:10, "Alexey Proskuryakov" <a...@webkit.org>: >>>  Migrating WebKit t

Re: [webkit-dev] Upstreaming from LayoutTests to web-platform-tests, coordinating Blink+WebKit

16.11.2017, 20:10, "Alexey Proskuryakov" : > Migrating WebKit tests seems undesirable to me, as that would make us lose > all their modification history. As mentioned before, WPT tests are inherently > getting less attention in CI support, largely because of unclear benefit

Re: [webkit-dev] unified sources build + forwarding headers that are copies

14.11.2017, 14:54, "Salisbury, Mark" : > Hello, > > I’m building on Windows (WPE platform, perhaps I’m the first to try this!) > and I’m seeing some compile errors that I believe are arising from previously > untested combinations of source files. > > If I understand

Re: [webkit-dev] unified sources build + forwarding headers that are copies

14.11.2017, 19:10, "Michael Catanzaro" : > On Tue, Nov 14, 2017 at 5:54 AM, Salisbury, Mark > wrote: >>  Hello, >> >>  I’m building on Windows (WPE platform, perhaps I’m the first to >>  try this!) > > Wow! > >>  and I’m seeing some compile errors

Re: [webkit-dev] where should tests reside? tests/preload v. tests/loading

08.11.2017, 17:54, "Colin Bendell | +1.613.914.3387" : > I'm chasing down racy logging with one of my tests and I've noticed > some duplication for preloader tests. Specifically: > 1) when should you organize preload tests in > LayoutTests/http/tests/preload v. >

Re: [webkit-dev] Proposal: Remove ENABLE(MATHML)

23.10.2017, 19:11, "Frédéric WANG" <fred.w...@free.fr>: > On 23/10/2017 18:04, Konstantin Tokarev wrote: >>  There is a big difference between SVG and MathML: the first one is entirely >> self- >>  contained, while (AFAIU) MathML requires presence of ma

Re: [webkit-dev] Proposal: Remove ENABLE(MATHML)

23.10.2017, 18:43, "Frédéric WANG" : > Hi, > > There have been some discussions recently on > https://bugs.webkit.org/show_bug.cgi?id=177744 regarding the relevance > of the compile-time flag for MathML. Discussing with Olivier during the > Web Engines Hackfest, it seems he

Re: [webkit-dev] RFC: Removing feature flag defaults in build-webkit

21.09.2017, 22:01, "Tim Horton" <timothy_hor...@apple.com>: >>  On Sep 21, 2017, at 11:57, Konstantin Tokarev <annu...@yandex.ru> wrote: >> >>  21.09.2017, 21:54, "Tim Horton" <timothy_hor...@apple.com>: >>>  Hi, all! >>>

Re: [webkit-dev] RFC: Removing feature flag defaults in build-webkit

21.09.2017, 21:54, "Tim Horton" : > Hi, all! > > Would anybody mind if build-webkit stopped being a source of default values > of feature flags? > > We have defaults for feature flags in FeatureDefines.xcconfig for Xcode, > WebKitFeatures.cmake (and Options*.cmake for

Re: [webkit-dev] Generation of documentation describing HTML5 support

07.09.2017, 13:03, "Romain Bellessort" : > Hi all, > > Safari has some documentation describing support for HTML/CSS/JS (see e.g. > [1]). Creating and maintaining such documentation likely requires a > significant amount of work. > > I don't know to what extent Apple

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

30.08.2017, 21:05, "Alex Christensen" : >>  On Aug 29, 2017, at 5:54 PM, Sam Weinig wrote: >>  In a completely other direction, what does this mean for use of Xcode? Can >> we still build from Xcode? Debug? > > CMake can generate Xcode files, so you

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

30.08.2017, 03:01, "Michael Catanzaro" : > On Tue, Aug 29, 2017 at 6:20 PM, Alicia Boya García > wrote: >>  As long as the sets are generated consistently that approach should be >>  equally fine and indeed it would reduce the burden for contributors. >>

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

29.08.2017, 14:44, "Alicia Boya García" : > On 08/29/2017 06:20 AM, Daniel Bates wrote: > >>  Do we know what is the cause(es) for the slow clean builds? I am assuming >> that much of the speed up from the "unified source" comes from clang being >> able to use an in-memory

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

29.08.2017, 23:54, "Alicia Boya García" : > I'm all for stable bundle .cpp files. Automatic generation can be nice > for the first time... and once in while we can try to modify the bundles > to try to make the build even faster, but really most of the time bundle > contents

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

29.08.2017, 22:48, "Geoffrey Garen" : >>> We have some preliminary data that says incremental builds will be OK, but >>> not a full benchmark. >>> >>> Here’s a full benchmark I propose to test incremental builds: >>> >>> Start 7 days ago in SVN history. Do a clean build. >>>

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

  29.08.2017, 21:32, "Maciej Stachowiak" :  On Aug 29, 2017, at 9:10 AM, Chris Dumez wrote: I worry about adopting unity build because while it makes clean builds faster, it also slows down incremental builds. As a developer, I rarely do clean builds, I mostly do

Re: [webkit-dev] Growing tired of long build times? Check out this awesome new way to speed up your build... soon (HINT: It's not buying a new computer)

29.08.2017, 21:19, "Olmstead, Don" : > Did you happen to look at any sort of distributed build system? We use > distributed builds here for WebKit and a full rebuild is pretty reasonable. > That would negate the need to change how everything is done to get a unity >

Re: [webkit-dev] "webkit-patch upload --no-review" submits to EWS by default

15.08.2017, 00:16, "Daniel Bates" : > Hi all, > > Just a heads up. Following r220715, "webkit-patch upload --no-review" and  > "webkit-patch post-commits --no-review" now submits a patch(es) for EWS > analysis by default. You no longer need to open the Bugzilla bug and click

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] Python

07.08.2017, 16:47, "Michael Catanzaro" : > Hi, > > As you're probably already aware, in Arch Linux /usr/bin/python has > been a symlink to /usr/bin/python3 for a long time now. In practice > this means that Arch users are not going to be able to use basically > any of our

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

04.08.2017, 21:20, "Carlos Alberto Lopez Perez" <clo...@igalia.com>: > On 02/08/17 12:14, Konstantin Tokarev wrote: >>  FWIW, I use ENABLE_ALLINONE_BUILD=ON as a default build option in Qt >>  port and don't have any "terrible" development experien

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

03.08.2017, 01:07, "Michael Catanzaro" <mcatanz...@igalia.com>: > On Wed, Aug 2, 2017 at 11:14 AM, Konstantin Tokarev <annu...@yandex.ru> wrote: >> FWIW, I use ENABLE_ALLINONE_BUILD=ON as a default build option in Qt port >> and don't have any "terrible

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

02.08.2017, 01:49, "Michael Catanzaro" : > 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

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] OpenGl version to be used

02.08.2017, 10:36, "gaurav.arad...@wipro.com" : > Hi, > > We are trying to port Webkit on an embedded platform from version 74xxx to  > 184849 (from Webkit turnk version in 2010 to  version in 2015). Currently we > have custom implementation of OpenGl 1.x running on

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

02.08.2017, 01:12, "Maciej Stachowiak" <m...@apple.com>: >>  On Aug 1, 2017, at 5:55 PM, Konstantin Tokarev <annu...@yandex.ru> wrote: >> >>  02.08.2017, 00:49, "Sam Weinig" <wei...@apple.com>: >>>>   On Aug 1, 2017, at 6:57

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?

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

Re: [webkit-dev] JIT probe mechanism soon required for DFG and FTL OSR Exit

19.07.2017, 02:49, "Mark Lam" : > FYI, I’m looking into making OSR exits work in a more memory efficient way > using the JIT probe mechanism.  Once we make this transition, the DFG and FTL > will not work for any CPU targets that don’t support the JIT probe mechanism. >  

Re: [webkit-dev] WebKit build

14.07.2017, 17:00, "Nagendra K" : > Hi All > > Is it possible to build WebKit without any port? No. > I want to add custom port above that step by step and check. > I saw the build-webkit Script which gives "--only -webkit build" option, but > this is not working. > >

Re: [webkit-dev] Pthread

07.07.2017, 15:01, "Nagendra K" : > Hi All, > > When building JavaScriptCore I am not able to link pthread calls. > Is there a way we can specify the CMakeLists.txt with option to include > pthread. > > I am using Ubuntu machine to build. You need to link

Re: [webkit-dev] Layout test

un 2017 8:50 p.m., "Konstantin Tokarev" <annu...@yandex.ru> wrote: 29.06.2017, 18:18, "Nagendra K" <pingnagen...@gmail.com>:> Hi,>> I have a requirement to check if a particular WebKit or latest WebKit works on the embedded platform. They have custom port which

  1   2   3   >