[webkit-dev] Patch WebKit to support custom Audio I/O handlers
Dear Everyone! Currently, we are working on a project that aims to extend Selenium's functionality in regard to the Audio Input and Output, which Selenium currently does not support. The goal is to be able to provide custom audio input/output to an internal website, which we want to test automatically. For this, we are currently evaluating a rather complex approach involving using special Linux VMs and PulseAudio, thus rerouting the audio through the PulseAudio server. This approach is, of course, rather unsatisfying and error prone. Which is why we are thinking about forking WebKit and implementing a custom audio backend relaying the audio input and the audio output of the website to a custom handler. Which is why I want to ask: * I am a novice in the WebKit project, how would you suggest starting this task? * If we really were to go this route, would you be interested in an upstream patch or would you prefer a fork instead? * (off-topic) Are there any different approaches other than the two suggested above? Yours faithfully, Alexander ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Patch WebKit to support custom Audio I/O handlers
Dear Everyone! Currently, we are working on a project that aims to extend Selenium's functionality in regard to the Audio Input and Output, which Selenium currently does not support. The goal is to be able to provide custom audio input/output to an internal website, which we want to test automatically. For this, we are currently evaluating a rather complex approach involving using special Linux VMs and PulseAudio, thus rerouting the audio through the PulseAudio server. This approach is, of course, rather unsatisfying and error prone. Which is why we are thinking about forking WebKit and implementing a custom audio backend relaying the audio input and the audio output of the website to a custom handler. Which is why I want to ask: * I am a novice in the WebKit project, how would you suggest starting this task? * If we really were to go this route, would you be interested in an upstream patch or would you prefer a fork instead? * (off-topic) Are there any different approaches other than the two suggested above? Yours faithfully, Alexander ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2023 WebKit Contributors Meeting — Save the Date
Hello WebKit Contributors, save the date! You are invited to participate in the 2023 WebKit Contributors Meeting at the Apple Park campus or available online via WebEx on Tuesday, October 24th, from 1 PM to around 6 PM Pacific and Wednesday, October 25th, from 8 AM to around 2 PM Pacific. To attend, you must be an active contributor to the WebKit open-source project. The meeting will be free of charge, and registration will open soon. Registration is required whether you are attending in person or virtually. You can find more details about the event and register when registration is open at the 2023 WebKit Contributors Meeting page: https://webkit.org/meeting/ **Health & Safety** For the safety of everyone at Apple Park, in-person attendees will be required to wear a mask indoors except while eating and drinking. If you are feeling ill, we encourage you to join remotely using WebEx. We also strongly encourage testing for COVID prior to attending in-person and attending online if you receive any positive result. This year’s event is being organized by Jon Davis, Brian Kardell, Eric Meyer, and Jen Simmons. The event will feature presentation-led discussions of 10-40 minutes long, followed by queue-moderated discussion. There will also be a lightning talk segment if you have a topic you can present in less than 10 minutes. If you have a topic to present for discussion, please email any of the organizers or message them on WebKit Slack. Feel free to reach out to any of the organizers with ideas or questions about this year’s online event. We’re looking forward to seeing you there! --- Jon Davis, on behalf of the WebKit Contributors Meeting Organizers ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] git-webkit pr now supports --no-ews / --ews flags
As of 259501@main, we now have both, GitHub label "skip-ews" and git-webkit pr support for --skip-ews flag. Thanks Aakash > On Jan 26, 2023, at 3:58 PM, Geoffrey Garen wrote: > > This is great! > > As it is said in "Ghost Dog: The Way of the Samurai", it is bad when one > thing becomes two. Can we pick one name for this feature? Either —no-ews > (git-webkit) and no-ews (GitHub) or —skip-ews (git-webkit) and skip-ews > (GitHub)? > > Thanks, > Geoff > >> On Jan 26, 2023, at 11:36 AM, Aakash Jain via webkit-dev >> wrote: >> >> Hi Everyone, >> >> git-webkit pr now supports --no-ews / --ews flags (as of 259115@main). This >> is similar to --no-ews flag we had in webkit-patch. You can also manually >> add skip-ews label on any PR when you don't need EWS to run anymore on it. >> --no-ews flag will also automatically add the skip-ews label on the >> corresponding GitHub PR. >> >> Please feel free to use skip-ews GitHub label or --no-ews flag in git-webkit >> pr, when you don't need to run EWS for any reason (e.g.: PR failed a >> critical EWS indicating need for new iteration, and you don't need to run >> rest of the EWSes on that commit). >> >> If you notice any issues, please let me know or file bugs (and assign to me). >> >> >> Thanks >> Aakash >> ___________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> https://lists.webkit.org/mailman/listinfo/webkit-dev > ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] git-webkit pr now supports --no-ews / --ews flags
This is great! As it is said in "Ghost Dog: The Way of the Samurai", it is bad when one thing becomes two. Can we pick one name for this feature? Either —no-ews (git-webkit) and no-ews (GitHub) or —skip-ews (git-webkit) and skip-ews (GitHub)? Thanks, Geoff > On Jan 26, 2023, at 11:36 AM, Aakash Jain via webkit-dev > wrote: > > Hi Everyone, > > git-webkit pr now supports --no-ews / --ews flags (as of 259115@main). This > is similar to --no-ews flag we had in webkit-patch. You can also manually > add skip-ews label on any PR when you don't need EWS to run anymore on it. > --no-ews flag will also automatically add the skip-ews label on the > corresponding GitHub PR. > > Please feel free to use skip-ews GitHub label or --no-ews flag in git-webkit > pr, when you don't need to run EWS for any reason (e.g.: PR failed a critical > EWS indicating need for new iteration, and you don't need to run rest of the > EWSes on that commit). > > If you notice any issues, please let me know or file bugs (and assign to me). > > > Thanks > Aakash > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] git-webkit pr now supports --no-ews / --ews flags
Hi Everyone, git-webkit pr now supports --no-ews / --ews flags (as of 259115@main). This is similar to --no-ews flag we had in webkit-patch. You can also manually add skip-ews label on any PR when you don't need EWS to run anymore on it. --no-ews flag will also automatically add the skip-ews label on the corresponding GitHub PR. Please feel free to use skip-ews GitHub label or --no-ews flag in git-webkit pr, when you don't need to run EWS for any reason (e.g.: PR failed a critical EWS indicating need for new iteration, and you don't need to run rest of the EWSes on that commit). If you notice any issues, please let me know or file bugs (and assign to me). Thanks Aakash ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2022 WebKit Contributors Meeting — Registration Open!
Hello WebKit Contributors, You are invited to participate in a virtual WebKit Contributors Meeting hosted online via WebEx on Wedmesday, November 9th from 1 PM to around 6 PM Pacific and Thursday, November 10th from 8 AM to around 2 PM Pacific. To attend you must be an active contributor to the WebKit open-source project. The meeting will be free of charge, and registration is open. You can register for the event on the 2022 WebKit Contributors Meeting page: https://webkit.org/meeting/ This year’s event is being organized by Jon Davis, Brian Kardell, Eric Meyer, and Jen Simmons. The event will feature presentation-led discussions of 10-40 minutes long, followed by queue-moderated discussion. There will also be a lightning talk segment if you have a topic you can present in less than 10 minutes. If you have a topic to present for discussion, please email any of the organizers, or message them on WebKit Slack. This year will include an optional social experience in the form of a game that you can choose to participate in. It’s an extra fun way to get to know folks in the community. More details on this experience are available from the meeting page. Feel free to reach out to me with ideas or questions on this year’s online event. We’re looking forward to seeing you there. smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2021 WebKit Contributors Meeting - Save the Date
Hello WebKit Contributors, You are invited to participate in a virtual WebKit Contributors Meeting hosted online via WebEx on Monday, September 27th from 1 PM to around 6 PM Pacific and Tuesday, September 28th from 8 AM to around noon Pacific. To attend you must be an active contributor to the WebKit open-source project. The meeting will be free of charge, and registration will open soon. The event will feature presentation-led discussions of 10-40 minutes long, followed by queue-moderated discussion. If you have a topic to present for discussion, please email me, or message me on WebKit Slack. There will also be a lightning talk segment if you have a topic you can present in less than 10 minutes. Feel free to reach out to me with ideas or questions on this year’s online event. Thank you, Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Safari/Webkit Team and Developer Communication
To *Safari/Webkit-Developers*, I'd like to draw your attention to the following threads on this years WWDC21: https://developer.apple.com/forums/thread/681748 (Safari/Webkit Team and Developer Communication") https://developer.apple.com/forums/thread/681575 (Notifications for Web-Apps on iOS?) As web-developers we feel we have limited influence over Safari (specifically iOS Safari) and there's the growing perception that Safari is being strategically underfunded with specific features never being developed in order to push users towards the AppStore and it's 70+ billion $ in yearly revenue. We also understand that as people who actually develop browsers you are as passionate if not more so than the development community about the open web but we also understand that you don't have control over exactly what gets built/funded. Our feeling is that: - The Safari/Webkit Team does not have the budget/staffing it needs to keep up with the full feature set of a modern browser. - Upper management *strategically underfunds* or does not develop specific features to push developers to use the AppStore instead where Apple can then take a 30% cut off revenue / lock apps into the Apple ecosystem. - Upper Management does not see much value in funding the open-web in general but specifically does not want to fund anything that would allow native-app like functionality in a web-app on a mobile device. - Developer feature requests are largely ignored because of point no 2. - Other browsers are not allowed in iOS primarily because of point no 2. (with privacy/security being a very secondary reason) In terms of developing web-apps Safari on iOS is the *number one limiting factor*. Every year goes past, we request the same basic set of features but the *core *capabilities of web-apps remains largely stagnant. The Safari team needs a much higher budget, a ton more staff and should be able to operate relatively independently of external business goals. Priorities should be set between a combination of what's good for users and what's good for developers, how much money the AppStore makes should not be a consideration when deciding what does and what doesn't get developed. Safari and Web-Apps are often touted by Apple Legal in antitrust/monopoly investigations as the alternative to the AppStore. How can they be the alternative with the current feature set. This threat alone should push Apple to fund the Safari team and make web-apps a viable competitor with native. Please take a read of the linked posts above and please respond if you have any opinions or you don't agree with any of the assumptions/perceptions above. We implore you, talk to your colleagues, directors, senior directors, svps, vps, *advocate* for the open-web / web-apps and try to push Safari in a direction where it at least has the core basic features that native apps have. This change has to come from within the organization, all we can do as outsiders is appeal for your help. Thank-you for your hard work and time, please help us make this change. ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reminder: WebKit SVN tree clousures (March 2021)
Hello everyone, The maintenance has been completed. WebKit SVN tree is open again. Commit-queue bots are also back online. Thanks for your patience. Please let us know if you notice any issue. Thanks Aakash > On Mar 17, 2021, at 12:50 PM, Ling Ho via webkit-dev > wrote: > > Hello, > > The 2nd maintenance mentioned in my previous email will take place this > coming weekend as planned. > > The WebKit SVN tree will be closed during: > Begin: Friday, March 19th, 2021. 5pm (PDT) > End: Monday, March 22nd, 2021. No later than 6pm (PDT) > > ... > Ling Ho > > On 2/24/21 5:26 PM, Ling Ho wrote: >> Hello WebKit, >> >> Due to planned infrastructure maintenance, our critical continuous >> integration services (EWS and post-commit bots) will be unavailable during >> the following weekends: >> >> Dates: >> Begin: Friday, March 5th, 2021. 5pm (PST) >> End: Monday, March 8th, 2021. No later than 6pm (PST) >> >> Begin: Friday, March 19th, 2021. 5pm (PDT) >> End: Monday, March 22nd, 2021. No later than 6pm (PDT) >> >> To avoid accumulating difficult to diagnose regressions during this lengthy >> outage, WebKit SVN tree will be closed. >> >> Please email ad...@webkit.org <mailto:ad...@webkit.org> if you have any >> questions or concerns. >> >> Thanks, >> >> ... >> Ling Ho > > ___________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Reminder: WebKit SVN tree clousures (March 2021)
Hello, The 2nd maintenance mentioned in my previous email will take place this coming weekend as planned. The WebKit SVN tree will be closed during: *Begin*: Friday, March 19th, 2021. 5pm (PDT) *End*: Monday, March 22nd, 2021. No later than 6pm (PDT) ... Ling Ho On 2/24/21 5:26 PM, Ling Ho wrote: Hello WebKit, Due to planned infrastructure maintenance, our critical continuous integration services (EWS and post-commit bots) will be unavailable during the following weekends: *Dates*: *Begin*: Friday, March 5th, 2021. 5pm (PST) *End*: Monday, March 8th, 2021. No later than 6pm (PST) *Begin*: Friday, March 19th, 2021. 5pm (PDT) *End*: Monday, March 22nd, 2021. No later than 6pm (PDT) To avoid accumulating difficult to diagnose regressions during this lengthy outage, *WebKit SVN tree will be closed*. Please email ad...@webkit.org if you have any questions or concerns. Thanks, ... Ling Ho ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reminder: WebKit SVN Tree clousure (Dec 23, 2020 - Jan 5, 2021)
Due to an unforeseen change of circumstances, we are no longer planning to close the tree over the holiday break. Sorry for the last minute notice! Please keep an eye out for build and test breakage if you land changes. Happy holidays!" ... Ling Ho On 12/21/20 1:20 PM, Ling Ho wrote: This is a reminder that the WebKit source tree will be closed starting on Wednesday at 5pm PST. ... Ling Ho On 12/10/20 4:28 PM, Ling Ho wrote: Hello WebKit, Some of our critical continuous integration services will be unavailable due to planned underlying infrastructure maintenance. Most EWS and post-commit bots will be down, so we will be closing the WebKit SVN tree to avoid accumulating difficult to diagnose regressions during this lengthy outage. The planned closure of the tree will begin at *5 pm (PST) on Wednesday, Dec 23rd, 2020* until no later than *6 pm (PST) on Tuesday, Jan 5th**, 2021. *Please email ad...@webkit.org if you have any questions or concerns. Thanks, ... Ling Ho ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Reminder: WebKit SVN Tree clousure (Dec 23, 2020 - Jan 5, 2021)
This is a reminder that the WebKit source tree will be closed starting on Wednesday at 5pm PST. ... Ling Ho On 12/10/20 4:28 PM, Ling Ho wrote: Hello WebKit, Some of our critical continuous integration services will be unavailable due to planned underlying infrastructure maintenance. Most EWS and post-commit bots will be down, so we will be closing the WebKit SVN tree to avoid accumulating difficult to diagnose regressions during this lengthy outage. The planned closure of the tree will begin at *5 pm (PST) on Wednesday, Dec 23rd, 2020* until no later than *6 pm (PST) on Tuesday, Jan 5th**, 2021. *Please email ad...@webkit.org if you have any questions or concerns. Thanks, ... Ling Ho ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reminder: WebKit SVN Tree clousure (Nov 22nd - Nov 26th, 2020)
The WebKit SVN tree is now open. ... Ling Ho On 11/19/20 11:18 AM, Ling Ho wrote: This is a reminder that the WebKit SVN source tree will be close for commit this coming weekend. I will send out an email once the tree is open again after the maintenance. Thanks, ... Ling Ho On 11/11/20 6:16 PM, Ling Ho wrote: Hello WebKit, Some of our critical continuous integration services will be unavailable due to planned underlying infrastructure maintenance. Most EWS and post-commit bots will be down, so we will be closing the WebKit SVN tree to avoid accumulating difficult to diagnose regressions during this lengthy outage. The planned closure of the tree will begin at *8 pm (PST) on Sunday, Nov 22nd, 2020* until no later than *11 pm (PST) on Thursday, Nov 26th**, 2020. *Please email ad...@webkit.org if you have any questions or concerns. Thanks, ... Ling Ho ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Reminder: WebKit SVN Tree clousure (Nov 22nd - Nov 26th, 2020)
This is a reminder that the WebKit SVN source tree will be close for commit this coming weekend. I will send out an email once the tree is open again after the maintenance. Thanks, ... Ling Ho On 11/11/20 6:16 PM, Ling Ho wrote: Hello WebKit, Some of our critical continuous integration services will be unavailable due to planned underlying infrastructure maintenance. Most EWS and post-commit bots will be down, so we will be closing the WebKit SVN tree to avoid accumulating difficult to diagnose regressions during this lengthy outage. The planned closure of the tree will begin at *8 pm (PST) on Sunday, Nov 22nd, 2020* until no later than *11 pm (PST) on Thursday, Nov 26th**, 2020. *Please email ad...@webkit.org if you have any questions or concerns. Thanks, ... Ling Ho ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2020 WebKit Contributors Meeting - Registration Reminder
Hello WebKit Contributors, Reminder to register for the WebKit Contributors Meeting! You can register at: https://webkit.org/meeting/ <https://webkit.org/meeting/>. Registration is open to active contributors to the WebKit open-source project and the meeting is free of charge. The virtual WebKit Contributors Meeting hosted online via WebEx on Monday, November 16th from 8 AM to around noon Pacific and Tuesday, November 17th from 1 PM to around 6 PM Pacific. Best regards, Jon Davis smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] in WebKit?
Nice, that's very quick, thanks Antti! On Tue, Oct 20, 2020 at 7:25 PM Antti Koivisto wrote: > I landed the updated behavior. > > > antti > > On Mon, Oct 19, 2020 at 11:29 AM Anders Hartvoll Ruud < > andr...@chromium.org> wrote: > >> Yes, there's css/selectors/is-where-error-recovery.tentative.html >> >> (.tentative tag to be dropped momentarily). >> >> On Sat, Oct 17, 2020 at 10:17 AM Antti Koivisto wrote: >> >>> Seems like a sensible change. Are there WPT tests for this behavior >>> already? >>> >>> >>> antti >>> >>> On Fri, Oct 16, 2020 at 8:06 PM Anders Hartvoll Ruud < >>> andr...@chromium.org> wrote: >>> >>>> Hi, >>>> >>>> We are about to ship support for :is() and :where() in Chromium, >>>> including support for . >>>> <https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list> As >>>> far as I understand, :is() in Safari 14 takes a regular , >>>> and Chromium API owners are concerned that this is a potential source of >>>> interop problems. >>>> >>>> Are there any plans to implement the behavior >>>> in WebKit as well? >>>> >>>> Thanks, >>>> Anders >>>> >>>> FYI: https://bugs.webkit.org/show_bug.cgi?id=217814 >>>> ___ >>>> webkit-dev mailing list >>>> webkit-dev@lists.webkit.org >>>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>>> >>> ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] in WebKit?
I landed the updated behavior. antti On Mon, Oct 19, 2020 at 11:29 AM Anders Hartvoll Ruud wrote: > Yes, there's css/selectors/is-where-error-recovery.tentative.html > > (.tentative tag to be dropped momentarily). > > On Sat, Oct 17, 2020 at 10:17 AM Antti Koivisto wrote: > >> Seems like a sensible change. Are there WPT tests for this behavior >> already? >> >> >> antti >> >> On Fri, Oct 16, 2020 at 8:06 PM Anders Hartvoll Ruud < >> andr...@chromium.org> wrote: >> >>> Hi, >>> >>> We are about to ship support for :is() and :where() in Chromium, >>> including support for . >>> <https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list> As >>> far as I understand, :is() in Safari 14 takes a regular , >>> and Chromium API owners are concerned that this is a potential source of >>> interop problems. >>> >>> Are there any plans to implement the behavior >>> in WebKit as well? >>> >>> Thanks, >>> Anders >>> >>> FYI: https://bugs.webkit.org/show_bug.cgi?id=217814 >>> ___________ >>> webkit-dev mailing list >>> webkit-dev@lists.webkit.org >>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>> >> ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] in WebKit?
Yes, there's css/selectors/is-where-error-recovery.tentative.html (.tentative tag to be dropped momentarily). On Sat, Oct 17, 2020 at 10:17 AM Antti Koivisto wrote: > Seems like a sensible change. Are there WPT tests for this behavior > already? > > > antti > > On Fri, Oct 16, 2020 at 8:06 PM Anders Hartvoll Ruud > wrote: > >> Hi, >> >> We are about to ship support for :is() and :where() in Chromium, >> including support for . >> <https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list> As >> far as I understand, :is() in Safari 14 takes a regular , >> and Chromium API owners are concerned that this is a potential source of >> interop problems. >> >> Are there any plans to implement the behavior >> in WebKit as well? >> >> Thanks, >> Anders >> >> FYI: https://bugs.webkit.org/show_bug.cgi?id=217814 >> _______ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> https://lists.webkit.org/mailman/listinfo/webkit-dev >> > ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] in WebKit?
Seems like a sensible change. Are there WPT tests for this behavior already? antti On Fri, Oct 16, 2020 at 8:06 PM Anders Hartvoll Ruud wrote: > Hi, > > We are about to ship support for :is() and :where() in Chromium, including > support for . > <https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list> As > far as I understand, :is() in Safari 14 takes a regular , > and Chromium API owners are concerned that this is a potential source of > interop problems. > > Are there any plans to implement the behavior in > WebKit as well? > > Thanks, > Anders > > FYI: https://bugs.webkit.org/show_bug.cgi?id=217814 > ___________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > ___________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] in WebKit?
Hi, We are about to ship support for :is() and :where() in Chromium, including support for . <https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list> As far as I understand, :is() in Safari 14 takes a regular , and Chromium API owners are concerned that this is a potential source of interop problems. Are there any plans to implement the behavior in WebKit as well? Thanks, Anders FYI: https://bugs.webkit.org/show_bug.cgi?id=217814 ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2020 WebKit Contributors Meeting - Save the Date
Hello WebKit Contributors, You are invited to participate in a virtual WebKit Contributors Meeting hosted online via WebEx on Monday, November 16th from 8 AM to around noon Pacific and Tuesday, November 17th from 1 PM to around 6 PM Pacific. To attend you must be an active contributor to the WebKit open-source project. The meeting will be free of charge, and registration will open soon. The event will feature presentation-led discussions of 10-40 minutes long, followed by queue-moderated discussion. If you have a topic to present for discussion, please email me, or message me on WebKit Slack. Feel free to reach out to me with ideas or questions on this year’s online event. Thank you, Jon Davis smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2019 WebKit Contributors Meeting
Hi WebKit folks, The 2019 WebKit Contributors Meeting is tomorrow! Please keep in mind the following important notes: **New Location** We are at the Hilton Santa Clara this year. https://maps.apple.com/place?address=4949+Great+America+Parkway,+Santa+Clara,+CA+95054 **Wear Layers** Our after hours dinner party will be outdoors. While there will be heaters, I recommend wearing several layers for the evening festivities. I look forward to seeing everyone again this year! – Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Unprefix -webkit-clip-path
I support unprefixing! Simon > On Oct 28, 2019, at 11:55 AM, Dirk Schulze wrote: > > Hi, > > I didn’t hear any objections to unprefix -webkit-clip-path. Unless no new > concerns get raised, I’ll land the patch later this week. > > Greetings, > Dirk > >> On 21. Oct 2019, at 13:01, Dirk Schulze > <mailto:dschu...@adobe.com>> wrote: >> >> Hi, >> >> I’d like to unprefix the -webkit-clip-path implementation. >> >> The spec for clip-path is CSS Masking >> ED: https://drafts.fxtf.org/css-masking-1/ >> <https://drafts.fxtf.org/css-masking-1/> >> CR: https://www.w3.org/TR/css-masking-1/ >> <https://www.w3.org/TR/css-masking-1/> >> >> Currently, WebKit has 2 independent(!) implementations: >> 1. The SVG clip-path CSS property that only applies to SVG elements and only >> allows referencing of clipPath SVG elements. >> 2. The -webkit-clip-path CSS property that started with basic shapes (CSS >> shape functions) and added support for referencing of clipPath SVG elements. >> While initially it just worked on HTML elements it covers SVG elements as >> well now. >> >> Therefore, the -webkit-clip-path implementation is a superset of the >> clip-path implementation and I intend to replace the latter with the former >> entirely. -webkit-clip-path will get an alias for clip-path. >> >> “Unprefixing" clip-path (ship with newly supported features) has been in >> discussion at Mozilla as well: >> https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path%7Csort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ >> >> <https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path|sort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ> >> https://groups.google.com/forum/#!msg/mozilla.dev.platform/RM5O36MZ4x4/mU0cOsT7EgAJ >> >> <https://groups.google.com/forum/#!msg/mozilla.dev.platform/RM5O36MZ4x4/mU0cOsT7EgAJ> >> >> Main concern was the confusion around the path() CSS shape function which >> was the only CSS shape function not defined in CSS Shapes Level 1 (but >> defined in the Motion spec). As a result, the CSS WG moved the function to >> CSS Shapes Level 1 which should address the concerns of the Mozilla >> community. >> >> The work happens here: https://bugs.webkit.org/show_bug.cgi?id=187888 >> <https://bugs.webkit.org/show_bug.cgi?id=187888> >> >> There are a few low-priority issues left (see master bug >> https://bugs.webkit.org/show_bug.cgi?id=126207 >> <https://bugs.webkit.org/show_bug.cgi?id=126207>). They should not have a >> real-world affect though as they are corner cases. >> >> Please raise your concerns here on the mailing list or send your support. >> >> Thanks a lot, >> Dirk Schulze > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Unprefix -webkit-clip-path
Hi, I didn’t hear any objections to unprefix -webkit-clip-path. Unless no new concerns get raised, I’ll land the patch later this week. Greetings, Dirk On 21. Oct 2019, at 13:01, Dirk Schulze mailto:dschu...@adobe.com>> wrote: Hi, I’d like to unprefix the -webkit-clip-path implementation. The spec for clip-path is CSS Masking ED: https://drafts.fxtf.org/css-masking-1/ CR: https://www.w3.org/TR/css-masking-1/ Currently, WebKit has 2 independent(!) implementations: 1. The SVG clip-path CSS property that only applies to SVG elements and only allows referencing of clipPath SVG elements. 2. The -webkit-clip-path CSS property that started with basic shapes (CSS shape functions) and added support for referencing of clipPath SVG elements. While initially it just worked on HTML elements it covers SVG elements as well now. Therefore, the -webkit-clip-path implementation is a superset of the clip-path implementation and I intend to replace the latter with the former entirely. -webkit-clip-path will get an alias for clip-path. “Unprefixing" clip-path (ship with newly supported features) has been in discussion at Mozilla as well: https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path%7Csort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ<https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path|sort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ> https://groups.google.com/forum/#!msg/mozilla.dev.platform/RM5O36MZ4x4/mU0cOsT7EgAJ Main concern was the confusion around the path() CSS shape function which was the only CSS shape function not defined in CSS Shapes Level 1 (but defined in the Motion spec). As a result, the CSS WG moved the function to CSS Shapes Level 1 which should address the concerns of the Mozilla community. The work happens here: https://bugs.webkit.org/show_bug.cgi?id=187888 There are a few low-priority issues left (see master bug https://bugs.webkit.org/show_bug.cgi?id=126207). They should not have a real-world affect though as they are corner cases. Please raise your concerns here on the mailing list or send your support. Thanks a lot, Dirk Schulze ___________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
I see. Could you login by clicking on the Login button? The "register" link is outdated. It is meant for user without a Trac account to register a new one. The Email and Password it is asking on that page is your Trac/SVN credential. Jon, could you help update the register link on the Login page to point to https://trac.webkit.org/register ? Thanks, ... ling On 10/25/19 8:07 AM, Geoffrey Garen wrote: The Login page looks like this: If you click the link, it takes you to https://webkit.org/auth/wregister. I’m not sure what “not used for registration this year means”; but what I mean is that this link is present on the page, and clicking it loads an error page. Thanks, Geoff On Oct 24, 2019, at 11:11 PM, Ling Ho <mailto:lin...@apple.com>> wrote: Hi Geoff, Please go to https://webkit.org/auth/wlogout/ and make sure you are not logged in. Then go to https://www.webkit.org/meeting and make sure the pages says "2019 WebKit Contributors Meeting". After that, try logging in and register again. The "https://webkit.org/auth/wregister; is not used for registration this year. ... ling On 10/24/19 9:12 PM, Geoffrey Garen wrote: https://webkit.org/auth/wregister Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at ad...@webkit.org <mailto:ad...@webkit.org> to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. On Oct 23, 2019, at 4:06 PM, Jonathan Davis <mailto:j...@apple.com>> wrote: Hello WebKit Contributors, This is a short reminder that your chance to register to attend the WebKit Contributors Meeting is closing after Friday, October 25th! Please be sure you’ve registered for the meeting at https://webkit.org/meeting/ The schedule of topics is filling in, but there are still a couple of larger time slots available. If you have a topic you’d like to present for discussion, please send me an email to secure a spot on the schedule. Note that the longer prepared talks are anywhere between 30-40 minutes leaving time for questions and discussions before the next session. If you have a short topic to present, email me about giving a 5-10 minute lightning talk. See you next Friday! Jon Davis On Sep 18, 2019, at 1:47 PM, Jonathan Davis <mailto:j...@apple.com>> wrote: Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis ___________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
Seems like an issue to look into. However this should not prevent you from registering, because you do have a Trac account (it's the same thing as your svn account). - Alexey > 25 окт. 2019 г., в 8:07 AM, Geoffrey Garen написал(а): > > The Login page looks like this: > > > > If you click the link, it takes you to > https://webkit.org/auth/wregister <https://webkit.org/auth/wregister>. > > I’m not sure what “not used for registration this year means”; but what I > mean is that this link is present on the page, and clicking it loads an error > page. > > Thanks, > Geoff > >> On Oct 24, 2019, at 11:11 PM, Ling Ho > <mailto:lin...@apple.com>> wrote: >> >> Hi Geoff, >> >> Please go to https://webkit.org/auth/wlogout/ >> <https://webkit.org/auth/wlogout/> and make sure you are not logged in. Then >> go to https://www.webkit.org/meeting <https://www.webkit.org/meeting> and >> make sure the pages says "2019 WebKit Contributors Meeting". After that, try >> logging in and register again. The "https://webkit.org/auth/wregister >> <https://webkit.org/auth/wregister>" is not used for registration this year. >> >> ... >> ling >> >> On 10/24/19 9:12 PM, Geoffrey Garen wrote: >>> https://webkit.org/auth/wregister <https://webkit.org/auth/wregister> >>> >>> Internal Server Error >>> >>> The server encountered an internal error or misconfiguration and was unable >>> to complete your request. >>> >>> Please contact the server administrator at ad...@webkit.org >>> <mailto:ad...@webkit.org> to inform them of the time this error occurred, >>> and the actions you performed just before this error. >>> >>> More information about this error may be available in the server error log. >>> >>> >>>> On Oct 23, 2019, at 4:06 PM, Jonathan Davis >>> <mailto:j...@apple.com>> wrote: >>>> >>>> Hello WebKit Contributors, >>>> >>>> This is a short reminder that your chance to register to attend the WebKit >>>> Contributors Meeting is closing after Friday, October 25th! >>>> >>>> Please be sure you’ve registered for the meeting at >>>> https://webkit.org/meeting/ <https://webkit.org/meeting/> >>>> >>>> The schedule of topics is filling in, but there are still a couple of >>>> larger time slots available. If you have a topic you’d like to present for >>>> discussion, please send me an email to secure a spot on the schedule. >>>> >>>> Note that the longer prepared talks are anywhere between 30-40 minutes >>>> leaving time for questions and discussions before the next session. If you >>>> have a short topic to present, email me about giving a 5-10 minute >>>> lightning talk. >>>> >>>> See you next Friday! >>>> >>>> Jon Davis >>>> >>>>> On Sep 18, 2019, at 1:47 PM, Jonathan Davis >>>> <mailto:j...@apple.com>> wrote: >>>>> >>>>> Hello WebKit Contributors, >>>>> >>>>> You are invited to attend the annual WebKit Contributors Meeting to be >>>>> held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 >>>>> AM to 6 PM Pacific. >>>>> >>>>> Breakfast and sign-in will begin at 8 AM. Presentations will run between >>>>> 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a >>>>> mid-afternoon snack break. A reception is planned at the venue after the >>>>> meeting with dinner and drinks from 6 PM to 9 PM. >>>>> >>>>> To attend you must be an active WebKit contributor. The meeting will be >>>>> free of charge, and registration is open. Register at >>>>> https://webkit.org/meeting/ <https://webkit.org/meeting/> >>>>> >>>>> The event format will include a mix of prepared talks around 40 minutes >>>>> long with 10-15 minutes of questions, and spontaneous lightning talks >>>>> about 5-10 minutes long. If you have a topic idea that you want to >>>>> present, please email me directly. >>>>> >>>>> We look forward to seeing you there! >>>>> >>>>> Thank you, >>>>> Jon Davis >>>> >>>> ___ >>>> webkit-dev mailing list >>>> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>>> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >>> >>> >>> >>> ___ >>> webkit-dev mailing list >>> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >> > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
The Login page looks like this: If you click the link, it takes you to https://webkit.org/auth/wregister <https://webkit.org/auth/wregister>. I’m not sure what “not used for registration this year means”; but what I mean is that this link is present on the page, and clicking it loads an error page. Thanks, Geoff > On Oct 24, 2019, at 11:11 PM, Ling Ho wrote: > > Hi Geoff, > > Please go to https://webkit.org/auth/wlogout/ > <https://webkit.org/auth/wlogout/> and make sure you are not logged in. Then > go to https://www.webkit.org/meeting <https://www.webkit.org/meeting> and > make sure the pages says "2019 WebKit Contributors Meeting". After that, try > logging in and register again. The "https://webkit.org/auth/wregister > <https://webkit.org/auth/wregister>" is not used for registration this year. > > ... > ling > > On 10/24/19 9:12 PM, Geoffrey Garen wrote: >> https://webkit.org/auth/wregister <https://webkit.org/auth/wregister> >> >> Internal Server Error >> >> The server encountered an internal error or misconfiguration and was unable >> to complete your request. >> >> Please contact the server administrator at ad...@webkit.org >> <mailto:ad...@webkit.org> to inform them of the time this error occurred, >> and the actions you performed just before this error. >> >> More information about this error may be available in the server error log. >> >> >>> On Oct 23, 2019, at 4:06 PM, Jonathan Davis >> <mailto:j...@apple.com>> wrote: >>> >>> Hello WebKit Contributors, >>> >>> This is a short reminder that your chance to register to attend the WebKit >>> Contributors Meeting is closing after Friday, October 25th! >>> >>> Please be sure you’ve registered for the meeting at >>> https://webkit.org/meeting/ <https://webkit.org/meeting/> >>> >>> The schedule of topics is filling in, but there are still a couple of >>> larger time slots available. If you have a topic you’d like to present for >>> discussion, please send me an email to secure a spot on the schedule. >>> >>> Note that the longer prepared talks are anywhere between 30-40 minutes >>> leaving time for questions and discussions before the next session. If you >>> have a short topic to present, email me about giving a 5-10 minute >>> lightning talk. >>> >>> See you next Friday! >>> >>> Jon Davis >>> >>>> On Sep 18, 2019, at 1:47 PM, Jonathan Davis >>> <mailto:j...@apple.com>> wrote: >>>> >>>> Hello WebKit Contributors, >>>> >>>> You are invited to attend the annual WebKit Contributors Meeting to be >>>> held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 >>>> AM to 6 PM Pacific. >>>> >>>> Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 >>>> AM to 6 PM. Lunch will be provided with all day coffee, tea and a >>>> mid-afternoon snack break. A reception is planned at the venue after the >>>> meeting with dinner and drinks from 6 PM to 9 PM. >>>> >>>> To attend you must be an active WebKit contributor. The meeting will be >>>> free of charge, and registration is open. Register at >>>> https://webkit.org/meeting/ <https://webkit.org/meeting/> >>>> >>>> The event format will include a mix of prepared talks around 40 minutes >>>> long with 10-15 minutes of questions, and spontaneous lightning talks >>>> about 5-10 minutes long. If you have a topic idea that you want to >>>> present, please email me directly. >>>> >>>> We look forward to seeing you there! >>>> >>>> Thank you, >>>> Jon Davis >>> >>> ___ >>> webkit-dev mailing list >>> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >> >> >> >> ___ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >> https://lists.webkit.org/mailman/listinfo/webkit-dev >> <https://lists.webkit.org/mailman/listinfo/webkit-dev> > ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
Hi Geoff, Please go to https://webkit.org/auth/wlogout/ and make sure you are not logged in. Then go to https://www.webkit.org/meeting and make sure the pages says "2019 WebKit Contributors Meeting". After that, try logging in and register again. The "https://webkit.org/auth/wregister; is not used for registration this year. ... ling On 10/24/19 9:12 PM, Geoffrey Garen wrote: https://webkit.org/auth/wregister Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at ad...@webkit.org <mailto:ad...@webkit.org> to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. On Oct 23, 2019, at 4:06 PM, Jonathan Davis <mailto:j...@apple.com>> wrote: Hello WebKit Contributors, This is a short reminder that your chance to register to attend the WebKit Contributors Meeting is closing after Friday, October 25th! Please be sure you’ve registered for the meeting at https://webkit.org/meeting/ The schedule of topics is filling in, but there are still a couple of larger time slots available. If you have a topic you’d like to present for discussion, please send me an email to secure a spot on the schedule. Note that the longer prepared talks are anywhere between 30-40 minutes leaving time for questions and discussions before the next session. If you have a short topic to present, email me about giving a 5-10 minute lightning talk. See you next Friday! Jon Davis On Sep 18, 2019, at 1:47 PM, Jonathan Davis <mailto:j...@apple.com>> wrote: Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis _______________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev ___________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
https://webkit.org/auth/wregister <https://webkit.org/auth/wregister> Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at ad...@webkit.org to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. > On Oct 23, 2019, at 4:06 PM, Jonathan Davis wrote: > > Hello WebKit Contributors, > > This is a short reminder that your chance to register to attend the WebKit > Contributors Meeting is closing after Friday, October 25th! > > Please be sure you’ve registered for the meeting at > https://webkit.org/meeting/ <https://webkit.org/meeting/> > > The schedule of topics is filling in, but there are still a couple of larger > time slots available. If you have a topic you’d like to present for > discussion, please send me an email to secure a spot on the schedule. > > Note that the longer prepared talks are anywhere between 30-40 minutes > leaving time for questions and discussions before the next session. If you > have a short topic to present, email me about giving a 5-10 minute lightning > talk. > > See you next Friday! > > Jon Davis > >> On Sep 18, 2019, at 1:47 PM, Jonathan Davis > <mailto:j...@apple.com>> wrote: >> >> Hello WebKit Contributors, >> >> You are invited to attend the annual WebKit Contributors Meeting to be held >> at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 >> PM Pacific. >> >> Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 >> AM to 6 PM. Lunch will be provided with all day coffee, tea and a >> mid-afternoon snack break. A reception is planned at the venue after the >> meeting with dinner and drinks from 6 PM to 9 PM. >> >> To attend you must be an active WebKit contributor. The meeting will be free >> of charge, and registration is open. Register at https://webkit.org/meeting/ >> <https://webkit.org/meeting/> >> >> The event format will include a mix of prepared talks around 40 minutes long >> with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 >> minutes long. If you have a topic idea that you want to present, please >> email me directly. >> >> We look forward to seeing you there! >> >> Thank you, >> Jon Davis > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Hurry! Registration is Closing!
Hello WebKit Contributors, This is a short reminder that your chance to register to attend the WebKit Contributors Meeting is closing after Friday, October 25th! Please be sure you’ve registered for the meeting at https://webkit.org/meeting/ The schedule of topics is filling in, but there are still a couple of larger time slots available. If you have a topic you’d like to present for discussion, please send me an email to secure a spot on the schedule. Note that the longer prepared talks are anywhere between 30-40 minutes leaving time for questions and discussions before the next session. If you have a short topic to present, email me about giving a 5-10 minute lightning talk. See you next Friday! Jon Davis > On Sep 18, 2019, at 1:47 PM, Jonathan Davis wrote: > > Hello WebKit Contributors, > > You are invited to attend the annual WebKit Contributors Meeting to be held > at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 > PM Pacific. > > Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM > to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon > snack break. A reception is planned at the venue after the meeting with > dinner and drinks from 6 PM to 9 PM. > > To attend you must be an active WebKit contributor. The meeting will be free > of charge, and registration is open. Register at https://webkit.org/meeting/ > > The event format will include a mix of prepared talks around 40 minutes long > with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 > minutes long. If you have a topic idea that you want to present, please email > me directly. > > We look forward to seeing you there! > > Thank you, > Jon Davis _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Unprefix -webkit-clip-path
Hi, I’d like to unprefix the -webkit-clip-path implementation. The spec for clip-path is CSS Masking ED: https://drafts.fxtf.org/css-masking-1/ CR: https://www.w3.org/TR/css-masking-1/ Currently, WebKit has 2 independent(!) implementations: 1. The SVG clip-path CSS property that only applies to SVG elements and only allows referencing of clipPath SVG elements. 2. The -webkit-clip-path CSS property that started with basic shapes (CSS shape functions) and added support for referencing of clipPath SVG elements. While initially it just worked on HTML elements it covers SVG elements as well now. Therefore, the -webkit-clip-path implementation is a superset of the clip-path implementation and I intend to replace the latter with the former entirely. -webkit-clip-path will get an alias for clip-path. “Unprefixing" clip-path (ship with newly supported features) has been in discussion at Mozilla as well: https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path%7Csort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ<https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path|sort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ> https://groups.google.com/forum/#!msg/mozilla.dev.platform/RM5O36MZ4x4/mU0cOsT7EgAJ Main concern was the confusion around the path() CSS shape function which was the only CSS shape function not defined in CSS Shapes Level 1 (but defined in the Motion spec). As a result, the CSS WG moved the function to CSS Shapes Level 1 which should address the concerns of the Mozilla community. The work happens here: https://bugs.webkit.org/show_bug.cgi?id=187888 There are a few low-priority issues left (see master bug https://bugs.webkit.org/show_bug.cgi?id=126207). They should not have a real-world affect though as they are corner cases. Please raise your concerns here on the mailing list or send your support. Thanks a lot, Dirk Schulze _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
Cool, that worked—thanks! On 9/18/19, 2:33 PM, "lin...@apple.com on behalf of Ling Ho" wrote: Hi Ross, There was a duplicate entry in the Trac's database causing the error. Can you please try again? I am also fixing another bug where the page will display "None" if the credential is not correct. So, you might want to try logging into trac.webkit.org first, and use the same username (email address) and password to sign on at the registration page. Thanks, ... ling On 9/18/19 2:12 PM, ross.kirsl...@sony.com wrote: > Seems like the login form isn't working—I see: > > MultipleObjectsReturned at /auth/wlogin/ > get() returned more than one MyUser -- it returned 2! > > Perhaps I just need to be more patient? :) > > Thanks, > Ross > > On 9/18/19, 1:49 PM, "webkit-dev on behalf of Jonathan Davis" wrote: > > Hello WebKit Contributors, > > You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. > > Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. > > To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ > > The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. > > We look forward to seeing you there! > > Thank you, > Jon Davis > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > > > ___________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
Hi Ross, There was a duplicate entry in the Trac's database causing the error. Can you please try again? I am also fixing another bug where the page will display "None" if the credential is not correct. So, you might want to try logging into trac.webkit.org first, and use the same username (email address) and password to sign on at the registration page. Thanks, ... ling On 9/18/19 2:12 PM, ross.kirsl...@sony.com wrote: Seems like the login form isn't working—I see: MultipleObjectsReturned at /auth/wlogin/ get() returned more than one MyUser -- it returned 2! Perhaps I just need to be more patient? :) Thanks, Ross On 9/18/19, 1:49 PM, "webkit-dev on behalf of Jonathan Davis" wrote: Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
You need to first login to: trac.webkit.org <http://trac.webkit.org/> You'll get an email to verify your email. After verifying, you'll be able to login on webkit.org <http://webkit.org/> (Thanks to Tadeu for figuring this out) - Saam > On Sep 18, 2019, at 2:14 PM, Chris Dumez wrote: > > Did not work for me either, got a page with text “None” shortly after logging > in. > > -- > Chris Dumez > > > > >> On Sep 18, 2019, at 2:12 PM, > <mailto:ross.kirsl...@sony.com>> > <mailto:ross.kirsl...@sony.com>> wrote: >> >> Seems like the login form isn't working—I see: >> >> MultipleObjectsReturned at /auth/wlogin/ >> get() returned more than one MyUser -- it returned 2! >> >> Perhaps I just need to be more patient? :) >> >> Thanks, >> Ross >> >> On 9/18/19, 1:49 PM, "webkit-dev on behalf of Jonathan Davis" >> > <mailto:webkit-dev-boun...@lists.webkit.org> on behalf of j...@apple.com >> <mailto:j...@apple.com>> wrote: >> >>Hello WebKit Contributors, >> >>You are invited to attend the annual WebKit Contributors Meeting to be >> held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM >> to 6 PM Pacific. >> >>Breakfast and sign-in will begin at 8 AM. Presentations will run between >> 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a >> mid-afternoon snack break. A reception is planned at the venue after the >> meeting with dinner and drinks from 6 PM to 9 PM. >> >>To attend you must be an active WebKit contributor. The meeting will be >> free of charge, and registration is open. Register at >> https://webkit.org/meeting/ <https://webkit.org/meeting/> >> >>The event format will include a mix of prepared talks around 40 minutes >> long with 10-15 minutes of questions, and spontaneous lightning talks about >> 5-10 minutes long. If you have a topic idea that you want to present, please >> email me directly. >> >>We look forward to seeing you there! >> >>Thank you, >>Jon Davis >>___________ >>webkit-dev mailing list >>webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>https://lists.webkit.org/mailman/listinfo/webkit-dev >> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >> >> >> _______________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >> https://lists.webkit.org/mailman/listinfo/webkit-dev > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
Did not work for me either, got a page with text “None” shortly after logging in. -- Chris Dumez > On Sep 18, 2019, at 2:12 PM, > wrote: > > Seems like the login form isn't working—I see: > > MultipleObjectsReturned at /auth/wlogin/ > get() returned more than one MyUser -- it returned 2! > > Perhaps I just need to be more patient? :) > > Thanks, > Ross > > On 9/18/19, 1:49 PM, "webkit-dev on behalf of Jonathan Davis" > wrote: > >Hello WebKit Contributors, > >You are invited to attend the annual WebKit Contributors Meeting to be > held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM > to 6 PM Pacific. > >Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 > AM to 6 PM. Lunch will be provided with all day coffee, tea and a > mid-afternoon snack break. A reception is planned at the venue after the > meeting with dinner and drinks from 6 PM to 9 PM. > >To attend you must be an active WebKit contributor. The meeting will be > free of charge, and registration is open. Register at > https://webkit.org/meeting/ > >The event format will include a mix of prepared talks around 40 minutes > long with 10-15 minutes of questions, and spontaneous lightning talks about > 5-10 minutes long. If you have a topic idea that you want to present, please > email me directly. > >We look forward to seeing you there! > >Thank you, >Jon Davis >_______ >webkit-dev mailing list >webkit-dev@lists.webkit.org >https://lists.webkit.org/mailman/listinfo/webkit-dev > > > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
Seems like the login form isn't working—I see: MultipleObjectsReturned at /auth/wlogin/ get() returned more than one MyUser -- it returned 2! Perhaps I just need to be more patient? :) Thanks, Ross On 9/18/19, 1:49 PM, "webkit-dev on behalf of Jonathan Davis" wrote: Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2019 WebKit Contributors Meeting - Registration is Open
Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hilton Santa Clara hotel on Friday, November 1st, 2019 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with dinner and drinks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Register at https://webkit.org/meeting/ The event format will include a mix of prepared talks around 40 minutes long with 10-15 minutes of questions, and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Updated WebKit components
Hello all, Here is a list of recent updates made to the WebKit Bugzilla components: Added a Compositing component: Bugs related to layerization for transforms, video, scrolling etc Added a Scrolling component: Bugs related to main thread and off-main thread scrolling Added a DOM component and combined all bugs from XML DOM, HTML DOM, and HTML Events into it. Removed XML DOM, HTML DOM, HTML Events components. Renamed Event Handling to “UI Events: For bugs related to user interactions like keyboard, mouse, and touch events” Renamed WebKit Gtk to WebKitGTK+ Renamed WebKit WPE to WPE WebKit Renamed Media Elements to Media Please let me know if you have any questions or concerns Thanks, Lucas ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2018 WebKit Contributors Meeting - Last Change to Register!
Hello WebKit Contributors, This Friday, September 28th is the last chance to register to attend the annual WebKit Contributors Meeting to be held at the Hyatt House San Jose/Silicon Valley hotel on Friday, October 12th, 2018 from 8 AM to 6 PM Pacific. If you haven’t registered yet, you should register soon. We have limited space and spots are filling up! Sign up at https://webkit.org/meeting/ <https://webkit.org/meeting/> to reserve your spot. The meeting is free of charge, but to attend you must be an active WebKit contributor. If you are traveling internationally and require a formal invitation letter, please email me. The event includes a mix of proposed talks of around 40 minutes long and spontaneous lightning talks between 5-10 minutes long. We look forward to seeing you there! Regards, Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2018 WebKit Contributors Meeting - Registration is Open!
Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hyatt House San Jose/Silicon Valley hotel on Friday, October 12th, 2018 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with drinks and snacks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is now open. Sign up at https://webkit.org/meeting/ to reserve your spot. The registration deadline is Friday, September 14th, 2018. If you are traveling internationally and require a formal invitation letter, please email me. The event format will follow last year’s mix of proposed talks of around 40 minutes long and spontaneous lightning talks about 5-10 minutes long. CALL FOR SPEAKERS This year we have 6 openings for 30-40 minute talks with 10 minutes of Q If you’d like to present at the meeting, please email me directly. Have something to share, but it won’t take that long? Consider emailing me about reserving a spot for a 5-10 minute Lightning Talk. Email me soon to reserve your spot before they fill up. We look forward to seeing you there! Thank you, Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2018 WebKit Contributors Meeting - Save the Date
Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hyatt House San Jose/Silicon Valley hotel on Friday, October 12th, 2018 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9:30 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with drinks and snacks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration will open shortly. The event format will include a mix of proposed talks of around 40 minutes long and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you want to present, please email me directly.. We look forward to seeing you there! Thank you, Jon Davis smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Compiling Webkit --wincairo
uot;) > -- Found LibXml2: D:/WebKit/webkit/WebKitLibraries/win/lib64/xml2.lib (found > suitable version "2.9.7", minimum required is "2.9.7") > -- Found OpenSSL: D:/WebKit/webkit/WebKitLibraries/win/lib64/libeay32.lib > (found suitable version "2.0.0", minimum required is "2.0.0") > -- Found ZLIB: D:/WebKit/webkit/WebKitLibraries/win/lib64/zlib.lib (found > version "1.2.11") > -- Found PNG: D:/WebKit/webkit/WebKitLibraries/win/lib64/libpng16.lib (found > suitable version "1.6.34", minimum required is "1.6.34") > -- Found Sqlite: D:/WebKit/webkit/WebKitLibraries/win/include (Required is at > least version "3.21.0") > -- Found ZLIB: D:/WebKit/webkit/WebKitLibraries/win/lib64/zlib.lib (found > suitable version "1.2.11", minimum required is "1.2.11") > -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) > -- Found WebP: > D:/WebKit/webkit/WebKitLibraries/win/include;D:/WebKit/webkit/WebKitLibraries/win/include > (Required is at least version "0.6.0") > -- Found LibXslt: D:/WebKit/webkit/WebKitLibraries/win/lib64/xslt.lib (found > suitable version "1.1.32", minimum required is "1.1.32") > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/WTF/wtf/PlatformWin.cmake > -- The ASM_MASM compiler identification is MSVC > -- Found assembler: > D:/VisualStudio2017/VC/Tools/MSVC/14.12.25827/bin/Hostx64/x64/ml64.exe > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/JavaScriptCore/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/JavaScriptCore/shell/PlatformWin.cmake > -- Using source list file: Sources.txt > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/ThirdParty/ANGLE/PlatformWin.cmake > -- Performing Test CXX_COMPILER_SUPPORTS_-Wno-undef > -- Performing Test CXX_COMPILER_SUPPORTS_-Wno-undef - Failed > -- Performing Test CXX_COMPILER_SUPPORTS_-Wno-suggest-attribute=format > -- Performing Test CXX_COMPILER_SUPPORTS_-Wno-suggest-attribute=format - > Failed > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/WebCore/PAL/pal/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/WebCore/PlatformWin.cmake > -- Using source list file: Sources.txt > -- Using source list file: platform/SourcesCairo.txt > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/WebKitLegacy/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Source/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Tools/DumpRenderTree/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Tools/ImageDiff/PlatformWin.cmake > -- Using platform-specific CMakeLists: > D:/WebKit/webkit/Tools/TestWebKitAPI/PlatformWin.cmake > -- Platform-specific CMakeLists not found: > D:/WebKit/webkit/PerformanceTests/PlatformWin.cmake > -- Enabled features: > -- ENABLE_3D_TRANSFORMS .. ON > -- ENABLE_ACCELERATED_2D_CANVAS OFF > -- ENABLE_ACCELERATED_OVERFLOW_SCROLLING . OFF > -- ENABLE_API_TESTS ON > -- ENABLE_ATTACHMENT_ELEMENT . ON > -- ENABLE_CHANNEL_MESSAGING ON > -- ENABLE_CSS3_TEXT .. OFF > -- ENABLE_CSS_BOX_DECORATION_BREAK ON > -- ENABLE_CSS_COMPOSITING OFF > -- ENABLE_CSS_SELECTORS_LEVEL4 ON > -- ENABLE_CURSOR_VISIBILITY .. ON > -- ENABLE_CUSTOM_SCHEME_HANDLER OFF > -- ENABLE_DATALIST_ELEMENT ... OFF > -- ENABLE_DEVICE_ORIENTATION OFF > -- ENABLE_DRAG_SUPPORT ... ON > -- ENABLE_FETCH_API ON > -- ENABLE_FTL_JIT OFF > -- ENABLE_FULLSCREEN_API ON > -- ENABLE_GAMEPAD OFF > -- ENABLE_GEOLOCATION ON > -- ENABLE_ICONDATABASE ....... ON > -- ENABLE_INDEXED_DATABASE ON > -- ENABLE_INDEXED_DATABASE_IN_WORKERS ON > -- ENABLE_INPUT_TYPE_COLOR OFF > -- ENABLE_INPUT_TYPE_DATE OFF > -- ENABLE_INPUT_TYPE_DATETIMELOCAL OFF > -- ENABLE_INPUT_TYPE_DATETIME_INCOMPLETE . OFF > -- ENABLE_INPUT_TYPE_MONTH OFF > -- ENABLE_INPUT_TYPE_TIME OFF > -- ENABLE_INPUT_TYPE_WEEK OFF > -- ENABLE_INTL ... ON > -- ENABLE_LEGACY_CSS_VENDOR_PREFIXES ON > -- ENABLE_LEGACY_CUSTOM_PROTOCOL_MANAGER . OFF > -- ENABLE_LEGACY_ENCRYPTED_MEDIA OFF > -- ENABLE_MATHML . ON > -- ENABLE_MEDIA_CONTROLS_SCRIPT ON > -- ENABLE_MEDIA_SOURCE ... OFF > -- ENABLE_MEDIA_STATISTICS ON > -- ENABLE_METER_ELEMENT .. ON > -- ENABLE_MOUSE_CURSOR_SCALE ON > -- ENABLE_NAVIGATOR_CONTENT_UTILS OFF > -- ENABLE_NOTIFICATIONS OFF > -- ENABLE_QUOTA .. OFF > -- ENABLE_STREAMS_API ON > -- ENABLE_SVG_FONTS .. ON > -- ENABLE_VIDEO ON > -- ENABLE_VIDEO_TRACK ON > -- ENABLE_WEBGL ON > -- ENABLE_WEBVTT_REGIONS . ON > -- ENABLE_WEB_AUDIO OFF > -- ENABLE_XSLT ... ON > -- Configuring done > -- Generating done > CMake Warning: > Manually-specified variables were not used by the project: > > CMAKE_EXPORT_COMPILE_COMMANDS > -- > > Am I missing something? > > Can someone give me some hints on how to better control the output of the > build process? > > Thanks in advance > > Have a Nice Day > , > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Compiling Webkit --wincairo
On Thu, Apr 19, 2018 at 9:24 AM, Barone Ashura <bar0n3ash...@gmail.com> wrote: Can someone give me some hints on how to better control the output of the build process? I would just use CMake directly, so you won't need to deal with build-webkit getting in the way. That script is not really intended to be used for production builds, despite the --release option Alternatively you could try to update FeatureList.pm to ensure it is able to disable all the things you want disabled, but this seems like a lost cause to me, as your mail shows clearly. Good luck! Michael ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Compiling Webkit --wincairo
cmake -- Using platform-specific CMakeLists: D:/WebKit/webkit/Tools/TestWebKitAPI/PlatformWin.cmake -- Platform-specific CMakeLists not found: D:/WebKit/webkit/PerformanceTests/PlatformWin.cmake -- Enabled features: -- ENABLE_3D_TRANSFORMS .. ON -- ENABLE_ACCELERATED_2D_CANVASOFF -- ENABLE_ACCELERATED_OVERFLOW_SCROLLING . OFF -- ENABLE_API_TESTSON -- ENABLE_ATTACHMENT_ELEMENT . ON -- ENABLE_CHANNEL_MESSAGINGON -- ENABLE_CSS3_TEXT .. OFF -- ENABLE_CSS_BOX_DECORATION_BREAK ON -- ENABLE_CSS_COMPOSITING OFF -- ENABLE_CSS_SELECTORS_LEVEL4 ON -- ENABLE_CURSOR_VISIBILITY .. ON -- ENABLE_CUSTOM_SCHEME_HANDLEROFF -- ENABLE_DATALIST_ELEMENT ... OFF -- ENABLE_DEVICE_ORIENTATION OFF -- ENABLE_DRAG_SUPPORT ... ON -- ENABLE_FETCH_APION -- ENABLE_FTL_JIT OFF -- ENABLE_FULLSCREEN_API ON -- ENABLE_GAMEPAD OFF -- ENABLE_GEOLOCATION ON -- ENABLE_ICONDATABASE ... ON -- ENABLE_INDEXED_DATABASE ON -- ENABLE_INDEXED_DATABASE_IN_WORKERS ON -- ENABLE_INPUT_TYPE_COLOR OFF -- ENABLE_INPUT_TYPE_DATE OFF -- ENABLE_INPUT_TYPE_DATETIMELOCAL OFF -- ENABLE_INPUT_TYPE_DATETIME_INCOMPLETE . OFF -- ENABLE_INPUT_TYPE_MONTH OFF -- ENABLE_INPUT_TYPE_TIME OFF -- ENABLE_INPUT_TYPE_WEEK OFF -- ENABLE_INTL ... ON -- ENABLE_LEGACY_CSS_VENDOR_PREFIXES ON -- ENABLE_LEGACY_CUSTOM_PROTOCOL_MANAGER . OFF -- ENABLE_LEGACY_ENCRYPTED_MEDIA OFF -- ENABLE_MATHML . ON -- ENABLE_MEDIA_CONTROLS_SCRIPTON -- ENABLE_MEDIA_SOURCE ... OFF -- ENABLE_MEDIA_STATISTICS ON -- ENABLE_METER_ELEMENT .. ON -- ENABLE_MOUSE_CURSOR_SCALE ON -- ENABLE_NAVIGATOR_CONTENT_UTILS OFF -- ENABLE_NOTIFICATIONSOFF -- ENABLE_QUOTA .. OFF -- ENABLE_STREAMS_API ON -- ENABLE_SVG_FONTS .. ON -- ENABLE_VIDEOON -- ENABLE_VIDEO_TRACK ON -- ENABLE_WEBGL ON -- ENABLE_WEBVTT_REGIONS . ON -- ENABLE_WEB_AUDIOOFF -- ENABLE_XSLT ... ON -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_COMPILE_COMMANDS -- Am I missing something? Can someone give me some hints on how to better control the output of the build process? Thanks in advance Have a Nice Day ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Update WebKit style to better accommodate accepted Obj-C block syntax
+1 for no space between ^ and { Simon > On Oct 3, 2017, at 4:51 PM, Megan Gardner <megan_gard...@apple.com> wrote: > > > Currently, the webkit style checker does not allow ^{ at the beginning of > Obj-C blocks. It demands that there is a space between the ^ and the {. This > is not how obj-c code is usually styled, and there is plenty of code already > in webkit that is formatted with the carrot and and brace together. This > seems to have been changed recently with > https://bugs.webkit.org/show_bug.cgi?id=161247. I think we should revisit > this, as ^ { is much less common that ^{ and is canonical style in pure Obj-C. > > Megan Gardner > _______________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Update WebKit style to better accommodate accepted Obj-C block syntax
Whatever we decide, we should probably also get it in https://webkit.org/code-style-guidelines/ > On Oct 3, 2017, at 4:51 PM, Megan Gardner <megan_gard...@apple.com> wrote: > > > Currently, the webkit style checker does not allow ^{ at the beginning of > Obj-C blocks. It demands that there is a space between the ^ and the {. This > is not how obj-c code is usually styled, and there is plenty of code already > in webkit that is formatted with the carrot and and brace together. This > seems to have been changed recently with > https://bugs.webkit.org/show_bug.cgi?id=161247. I think we should revisit > this, as ^ { is much less common that ^{ and is canonical style in pure Obj-C. > > Megan Gardner > _______________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Update WebKit style to better accommodate accepted Obj-C block syntax
Currently, the webkit style checker does not allow ^{ at the beginning of Obj-C blocks. It demands that there is a space between the ^ and the {. This is not how obj-c code is usually styled, and there is plenty of code already in webkit that is formatted with the carrot and and brace together. This seems to have been changed recently with https://bugs.webkit.org/show_bug.cgi?id=161247. I think we should revisit this, as ^ { is much less common that ^{ and is canonical style in pure Obj-C. Megan Gardner ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building WebKit for an iOS device
Le 12/07/2017 à 19:19, Alex Christensen a écrit : > WebKit can be built and run on the iOS simulator by anyone with the > public iOS SDK. I > use https://webkit.org/blog/3457/building-webkit-for-ios-simulator/ when > I forget how to do this. > > I guess WebKit can be built for device, but I’m pretty sure WebKit > cannot be put as the system framework on an iOS device without > Apple-internal tools. With a lot of work you might be able to > statically link everything into a custom app for local debugging, but > I’m pretty sure such an app would be rejected by the App Store based > on section 2.5.6 > of https://developer.apple.com/app-store/review/guidelines/ > Yes, I'm already using the simulator for running tests and testing local ios builds. I was just wondering whether it was possible to produce and install a local build for development and testing purpose on a device. Apparently from your reply and Michael's this seems quite unlikely with the public iOS SDK :-( I guess it would be nice to mention this limitation on https://webkit.org/building-webkit/ Thanks. -- Frédéric Wang signature.asc Description: OpenPGP digital signature _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building WebKit for an iOS device
I’ll add a little to Alex’s comments. I doubt you could build all of WebKit with the public iOS SDK. You certainly can’t sign JavaScriptCore to use JIT memory. Even if could build WebKit and statically linked your code with what you built, there will likely be some mismatch between the WebKit you built and the System frameworks that WebKit links against, such as UIKit, that will cause your app to crash on startup. - Michael > On Jul 12, 2017, at 10:19 AM, Alex Christensen <achristen...@apple.com> wrote: > > WebKit can be built and run on the iOS simulator by anyone with the public > iOS SDK. I use > https://webkit.org/blog/3457/building-webkit-for-ios-simulator/ > <https://webkit.org/blog/3457/building-webkit-for-ios-simulator/> when I > forget how to do this. > > I guess WebKit can be built for device, but I’m pretty sure WebKit cannot be > put as the system framework on an iOS device without Apple-internal tools. > With a lot of work you might be able to statically link everything into a > custom app for local debugging, but I’m pretty sure such an app would be > rejected by the App Store based on section 2.5.6 of > https://developer.apple.com/app-store/review/guidelines/ > <https://developer.apple.com/app-store/review/guidelines/> > >> On Jul 12, 2017, at 8:31 AM, Frédéric WANG <fred.w...@free.fr >> <mailto:fred.w...@free.fr>> wrote: >> >> Hello, >> >> For development and testing purpose, I was wondering if there is a way >> to produce a build of WebKit/Safari-mobile and to install it on a device >> (instead of using the iOS simulator)? And is there any specific >> requirement like having an Apple developer license and a registered device? >> >> I know that we have a builder [1] and I just noticed the "--ios-device" >> parameter for the build-webkit script but I can't find any information >> on the official documentation [2] or on the WebKit wiki. I also tried >> searching this mailing list about the topic but could not find any >> relevant thread. >> >> Thanks, >> >> Frédéric >> >> [1] https://build.webkit.org/builders/Apple%20iOS%2010%20Release%20(Build) >> <https://build.webkit.org/builders/Apple%20iOS%2010%20Release%20(Build)> >> [2] https://webkit.org/building-webkit/ <https://webkit.org/building-webkit/> >> >> >> ___________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >> https://lists.webkit.org/mailman/listinfo/webkit-dev > > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building WebKit for an iOS device
WebKit can be built and run on the iOS simulator by anyone with the public iOS SDK. I use https://webkit.org/blog/3457/building-webkit-for-ios-simulator/ <https://webkit.org/blog/3457/building-webkit-for-ios-simulator/> when I forget how to do this. I guess WebKit can be built for device, but I’m pretty sure WebKit cannot be put as the system framework on an iOS device without Apple-internal tools. With a lot of work you might be able to statically link everything into a custom app for local debugging, but I’m pretty sure such an app would be rejected by the App Store based on section 2.5.6 of https://developer.apple.com/app-store/review/guidelines/ <https://developer.apple.com/app-store/review/guidelines/> > On Jul 12, 2017, at 8:31 AM, Frédéric WANG <fred.w...@free.fr> wrote: > > Hello, > > For development and testing purpose, I was wondering if there is a way > to produce a build of WebKit/Safari-mobile and to install it on a device > (instead of using the iOS simulator)? And is there any specific > requirement like having an Apple developer license and a registered device? > > I know that we have a builder [1] and I just noticed the "--ios-device" > parameter for the build-webkit script but I can't find any information > on the official documentation [2] or on the WebKit wiki. I also tried > searching this mailing list about the topic but could not find any > relevant thread. > > Thanks, > > Frédéric > > [1] https://build.webkit.org/builders/Apple%20iOS%2010%20Release%20(Build) > [2] https://webkit.org/building-webkit/ > > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Building WebKit for an iOS device
Hello, For development and testing purpose, I was wondering if there is a way to produce a build of WebKit/Safari-mobile and to install it on a device (instead of using the iOS simulator)? And is there any specific requirement like having an Apple developer license and a registered device? I know that we have a builder [1] and I just noticed the "--ios-device" parameter for the build-webkit script but I can't find any information on the official documentation [2] or on the WebKit wiki. I also tried searching this mailing list about the topic but could not find any relevant thread. Thanks, Frédéric [1] https://build.webkit.org/builders/Apple%20iOS%2010%20Release%20(Build) [2] https://webkit.org/building-webkit/ signature.asc Description: OpenPGP digital signature _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 2017 WebKit Contributors Meeting – Registration is Open!
Hello WebKit Contributors, You are invited to attend the annual WebKit Contributors Meeting to be held at the Hyatt House San Jose/Silicon Valley hotel on Friday, October 13th, 2017 from 8 AM to 6 PM Pacific. Breakfast and sign-in will begin at 8 AM. Presentations will run between 9:30 AM to 6 PM. Lunch will be provided with all day coffee, tea and a mid-afternoon snack break. A reception is planned at the venue after the meeting with drinks and snacks from 6 PM to 9 PM. To attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is now open. Sign up at https://webkit.org/meeting/ to reserve your spot. The registration deadline is Friday, September 29th, 2017. If you are traveling internationally and require a formal invitation letter, please email me. The event format will follow last year’s mix of proposed talks of around 40 minutes long and spontaneous lightning talks about 5-10 minutes long. If you have a topic idea that you to present, please email me directly. We look forward to seeing you there! Thank you, Jon Davis smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Port WebKit to GNUstep
No. The bar is much higher for introducing a new port to WebKit. Geoff > On May 11, 2017, at 7:54 PM, Daniel Ferreira (theiostream) <bnm...@gmail.com> > wrote: > > Hi there, > > My name is Daniel Ferreira and as a Google Summer of Code project I > decided to tackle the ten-year-long[1] effort of porting WebKit to > GNUstep one more time (and hopefully get somewhere this time). > > Since 2009, GNUstep has gained a lot of maturity in its graphics stack > and on its implementation of CoreFoundation, so now having a WebKit > port in it seems like a more plausible goal – as well as a fun > challenge. This is very important to GS since it still has no web > browser running on top of it. > > Also since 2009, it seems like WebKit has gained mature ports on GTK > and Qt, which has made the demand for a GNUstep port quite smaller for > the project. However, it does seem interesting to offer a > cross-platform port that adds portability to a lot of currently > Mac-specific code – a goal a GNUstep port would fulfill. > > In an ideal world, GNUstep would be mature enough for us to build the > Mac port on a Linux machine pointing to GNUstep libraries and all > would be well. Sadly, this is not the case and a GNUstep port on > WebKit would require some adjustments on WebKit (although GNUstep > certainly would receive many patches as well implementing stuff WebKit > would use). > > That being said, I decided to try compiling WTF as a first approach to > this undertaking, and I introduced a "PlatformGNUstep.cmake" file that > is mostly a copy of PlatformMac.cmake. It ends up defining > WTF_PLATFORM_MAC and WTF_PLATFORM_GNUSTEP as code macros, and whenever > there is some Mac-specific code that GNUstep can't tackle, we try a > cross-platform alternative. Otherwise, the behavior is just like that > of the Mac port. > > Through some adjustments to WebKit code (e.g. GNUstep does not support > XPC, QOS, Mach kernel memory operations, so in these cases we either > do nothing or use Linux-specific code as an implementation) and > GNUstep adjustments (regarding some missing CoreFoundation functions), > I managed to get WTF compiled and linked. I'm now moving on to > JavaScriptCore to be able to test everything (and very likely spend > quite some time figuring out the most diverse issues that will show > up). > > That being said, I will send a patch as soon as I get JSC in a > semi-decent state. However I wondered if this introduce new platform + > do the same thing as Mac port with some exceptions approach seems > reasonable to the project now that I have realized it is actually > feasible. > > Thanks, > -- Daniel. > > [1]: https://lists.webkit.org/pipermail/webkit-dev/2009-October/010333.html > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
Currently, Android port uses cURL for network and cairo for graphics. Those popups you see are asking if you'll allow https connections. Popups should be removed once proper certfication check is implemented. I see you want to display videos with Android WebKit. Sadly, I don't think that is possible for now because the media player backend is not yet implemented - and I have to tell you that implementing it is not trivial :( I'm going to implement core functionalities including video but it would take some weeks. If you'd like to do it yourself, I can give you some leads. Please send me email then :) -Original Message- From: "Patrick Wright"wrigh...@gmail.com To: "장대웅"daewoong.j...@navercorp.com; Cc: "Konstantin Tokarev"annu...@yandex.ru; webkit-dev@lists.webkit.org; Sent: 2017-03-19 (일) 05:05:13 Subject: Re: [webkit-dev] Introduce WebKit Android port I agree. a small and peppy webkit or way to render a webpage on Android would be awesome. I tried Chromium (too slow!), Chromium Embedded framework (not on android), and QT5.8 QtWebview (lacks customization). I would like to help if possible. I built the libraries on my system but was unable to get the MiniBrowser apk to build with ant and older built tools recommended. I imported into Android Studio ran it with a few additions to gradle. I posted the running version to Github, It loads to a device, granted a bit slowly. have yet to try an emulator. https://github.com/wrightpt/android2 I am not able to load https://www.youtube.com/ . I get the following errors. According to stack overflow: "From the following threads this looks to be a bug with the WebView and can happen more often on enumerators when use host GPU is off." 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3338/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.491 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.501 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.501 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.501 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.501 3130-3338/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.531 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.531 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.531 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.571 3130-3130/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.611 3130-3338/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:44.621 3130-3338/org.webkit.minibrowser W/art: Attempt to remove non-JNI local reference, dumping thread 03-18 15:27:45.27
Re: [webkit-dev] Introduce WebKit Android port
I agree that JSC for Android should be useful as JSC is the fastest JavaScript engine. I will try build JSCOnly for Android soon then. Thank you for your suggestion. :) -Original Message- From: "Konstantin Tokarev"annu...@yandex.ru To: "장대웅"daewoong.j...@navercorp.com; "Michael Catanzaro"mcatanz...@igalia.com; "webkit-dev@lists.webkit.org"webkit-dev@lists.webkit.org; Cc: hsz...@icloud.com; "Eric Wing"ewmail...@gmail.com; Sent: 2017-03-18 (토) 04:23:45 Subject: Re: [webkit-dev] Introduce WebKit Android port 17.03.2017, 21:04, "장대웅" daewoong.j...@navercorp.com: Hi. It is not just a code drop and I will continue maintain it. Actually, I’d like to code together with anyone who is interested in it. I think WebKit is a really great project and I hope Android port make WebKit more widely used and encourage Android developers to contribute. I wrote Android port because it must be useful on Android platforms. Of course we have powerful Chromium on Android - but sometimes we need a cleaner and smaller renderer than a powerful one. I believe Android port can fit this need. I think it would be great if Android port is able to join upstream. I would appreciate if you let me know what is needed to upstream. Thank you for your feedback :) I think you should start with upstreaming WTF and JavaScriptCore changes, including build system. There are people interested in using JSC on Android as standalone JavaScript engine, I've CC'ed some of them. We have JSCOnly port intended for building JSC with minimum dependencies, and it would be great if it had Android support. As for upstreaming complete Android port, feasibility of that depends on how much full-time developers are working on it, and on amount of Android-specific code. But of course you can start from contributing fixes to port-independent code. Regards, Daewoong. -Original Message- From: "Michael Catanzaro"mcatanz...@igalia.com To: "장대웅"daewoong.j...@navercorp.com; webkit-dev@lists.webkit.org; Cc: Sent: 2017-03-17 (금) 11:26:19 Subject: Re: [webkit-dev] Introduce WebKit Android port Hi, Is this just a code drop? Or will you be committing to its maintenance and attempting to upstream it? It's interesting regardless! Michael , _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
17.03.2017, 21:04, "장대웅" <daewoong.j...@navercorp.com>: > Hi. > > It is not just a code drop and I will continue maintain it. Actually, I’d > like to code > together with anyone who is interested in it. I think WebKit is a really > great project and > I hope Android port make WebKit more widely used and encourage Android > developers to contribute. > > I wrote Android port because it must be useful on Android platforms. Of course > we have powerful Chromium on Android - but sometimes we need a cleaner and > smaller > renderer than a powerful one. I believe Android port can fit this need. > > I think it would be great if Android port is able to join upstream. I would > appreciate > if you let me know what is needed to upstream. Thank you for your feedback :) I think you should start with upstreaming WTF and JavaScriptCore changes, including build system. There are people interested in using JSC on Android as standalone JavaScript engine, I've CC'ed some of them. We have JSCOnly port intended for building JSC with minimum dependencies, and it would be great if it had Android support. As for upstreaming complete Android port, feasibility of that depends on how much full-time developers are working on it, and on amount of Android-specific code. But of course you can start from contributing fixes to port-independent code. > > Regards, > Daewoong. > > -Original Message- > From: "Michael Catanzaro"<mcatanz...@igalia.com> > To: "장대웅"<daewoong.j...@navercorp.com>; <webkit-dev@lists.webkit.org>; > Cc: > Sent: 2017-03-17 (금) 11:26:19 > Subject: Re: [webkit-dev] Introduce WebKit Android port > > Hi, > > Is this just a code drop? Or will you be committing to its maintenance > and attempting to upstream it? > > It's interesting regardless! > > Michael > > , > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
Hi. It is not just a code drop and I will continue maintain it. Actually, I’d like to code together with anyone who is interested in it. I think WebKit is a really great project and I hope Android port make WebKit more widely used and encourage Android developers to contribute. I wrote Android port because it must be useful on Android platforms. Of course we have powerful Chromium on Android - but sometimes we need a cleaner and smaller renderer than a powerful one. I believe Android port can fit this need. I think it would be great if Android port is able to join upstream. I would appreciate if you let me know what is needed to upstream. Thank you for your feedback :) Regards, Daewoong. -Original Message- From: "Michael Catanzaro"mcatanz...@igalia.com To: "장대웅"daewoong.j...@navercorp.com; webkit-dev@lists.webkit.org; Cc: Sent: 2017-03-17 (금) 11:26:19 Subject: Re: [webkit-dev] Introduce WebKit Android port Hi, Is this just a code drop? Or will you be committing to its maintenance and attempting to upstream it? It's interesting regardless! Michael _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
Hi, Is this just a code drop? Or will you be committing to its maintenance and attempting to upstream it? It's interesting regardless! Michael ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
12.03.2017, 12:36, "Yusuke SUZUKI" <utatane@gmail.com>: > Interesting. > Can JSCOnly port accepts the Android porting things into JSC? > I think this should be small enough. That would be great indeed! > > On Sun, Mar 12, 2017 at 9:21 장대웅 <daewoong.j...@navercorp.com> wrote: >> Hello, >> >> I'd like to let you know: WebKit Android port is available. Please check >> repository on GitHub: >> >> https://github.com/daewoong-jang/webkit-android >> >> It is based on our web engine project and is totally different from the old >> Android port which had been packaged with AOSP. >> >> The most important difference is that this new Android port adopts modern >> WebKit2 architecture. And it designed to be cross-platform itself so it can >> be built and run on other platforms(only for Windows, for now). >> >> You can see more details on GitHub. It is still far from complete, but I'd >> like to let you know that it has begun. I hope this project will help the >> WebKit community to thrive. If you have any questions, send me on email: >> daewoong.j...@navercorp.com(Weekdays) daewoon...@aol.com(Weekends and >> holidays). >> >> Regards, >> >> Daewoong. >> >> NAVER WebKit Team >> >> ___ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> https://lists.webkit.org/mailman/listinfo/webkit-dev > -- > Regards, > Yusuke Suzuki > , > > _______________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Introduce WebKit Android port
Interesting. Can JSCOnly port accepts the Android porting things into JSC? I think this should be small enough. On Sun, Mar 12, 2017 at 9:21 장대웅 <daewoong.j...@navercorp.com> wrote: > Hello, > > > > I'd like to let you know: WebKit Android port is available. Please check > repository on GitHub: > > https://github.com/daewoong-jang/webkit-android > > > > It is based on our web engine project and is totally different from the > old Android port which had been packaged with AOSP. > > The most important difference is that this new Android port adopts modern > WebKit2 architecture. And it designed to be cross-platform itself so it can > be built and run on other platforms(only for Windows, for now). > > > You can see more details on GitHub. It is still far from complete, but I'd > like to let you know that it has begun. I hope this project will help the > WebKit community to thrive. If you have any questions, send me on email: > daewoong.j...@navercorp.com(Weekdays) daewoon...@aol.com(Weekends and > holidays). > > Regards, > > Daewoong. > > > > NAVER WebKit Team > > > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > -- Regards, Yusuke Suzuki ___________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Introduce WebKit Android port
Hello, I'd like to let you know: WebKit Android port is available. Please check repository on GitHub: https://github.com/daewoong-jang/webkit-android It is based on our web engine project and is totally different from the old Android port which had been packaged with AOSP. The most important difference is that this new Android port adopts modern WebKit2 architecture. And it designed to be cross-platform itself so it can be built and run on other platforms(only for Windows, for now). You can see more details on GitHub. It is still far from complete, but I'd like to let you know that it has begun. I hope this project will help the WebKit community to thrive. If you have any questions, send me on email: daewoong.j...@navercorp.com(Weekdays) daewoon...@aol.com(Weekends and holidays). Regards, Daewoong. NAVER WebKit Team ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] The WebKit tree is OPEN!
Hi folks, We’re back in action! – we should have enough of our infrastructure up to keep the build green & guard against regressions, so the repository is open again to commits. We’d really like to minimize broken builds over the next day as any backlog of patches is being landed. We can all do our part to help with this. It would be greatly appreciated if everyone could update their patches to ToT and give them a fresh run through EWS before committing, to make make sure they’re still passing EWS. Thanks all for your understanding & apologies again for the inconvenience, Gavin > On Nov 8, 2016, at 8:07 PM, Ryosuke Niwa <rn...@webkit.org> wrote: > > Hi all, > > We're in the final process of verifying that our infrastructure is up & > running again. I've landed two patches manually to go through our buildbot > pipeline to make sure everything is working again. > > We're sorry for the inconvenience and we appreciate your cooperation & > patience. > > - R. Niwa > > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] https://webkit-queues.webkit.org down?
Hi all, It seems https://webkit-queues.webkit.org is down (I got 503 responses). Can somebody check this? Thanks y ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building Webkit on Windows
Hi Alex and all Friends here , Its finally build . I have a question, I wanna contribute and i would like to start with easy and baby steps kinda bugs. Any suggestions ? regards RSadhu Subject: Re: [webkit-dev] Building Webkit on Windows From: achristen...@apple.com Date: Mon, 29 Feb 2016 10:26:00 -0800 CC: thomas.br...@porabo.ch; bfulg...@apple.com; mmaxfi...@apple.com; webkit-dev@lists.webkit.org To: rakeshsa...@hotmail.com Rakesh, you are building the AppleWin port of WebKit, which only has 32-bit binaries available, but you probably want to use the WinCairo port because the license of WebKitSupportLibrary.zip says you’re not allowed to redistribute it. To build the WinCairo port, you will need to run update-webkit --wincairo and build-webkit --wincairo --64-bit. This is not the source of your build failure, though. It looks like you have your gperf executable inside of C:\Program Files… somewhere, and I believe we have never had anyone build WebKit with a configuration like this. I think the solution is to put quotes around the %s at the very end of Source/WebCore/platform/network/create-http-header-name-table. There might be a few more places where this is needed. Could you please file a bug a bugs.webkit.org with a patch if you get it working? On Feb 27, 2016, at 2:01 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: Hi Thomas, Thank for your answer . However my build suddenly fails and I notice , its creating 32 bit binaries . I am attaching a build log file here . regards RSadhu To: achristen...@apple.com From: thomas.brodt.li...@porabo.ch Date: Fri, 26 Feb 2016 09:15:06 +0100 CC: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Building Webkit on Windows Hi Alex thank you for your prompt answer. That is good news because in the past I had different difficulties in setting up a functional environment with several trial and error steps inbetween, although I tried to exactly follow the installation guide. I tend to create a virtual machine for a reliable building environment, so with my next one I will try without the cygwin installation. We use Webkit via COM interface on Windows in our application here, so I build rather infrequently, and with a working build, we then can live for some time. But for our use we would need 32bit dependencies, and if I understood correctly, there are currently only 64bit available. That doesn't matter at the moment, but when I am ready for our next build, I would ask again if you don't mind. Thanks for your help! Thomas Am 25.02.2016 um 19:17 schrieb Alex Christensen: That also applies to the WinCairo port. I don’t think you’ll need GNU Make any more now that we use CMake for Windows. You also shouldn’t need to install iTunes to build and run WinCairo. With WinCairo, you will also need the WinCairoDependencies.zip which you can get by running Tools/Scripts/update-webkit-wincairo-libs. Right now, only the 64-bit dependencies are included in that zip, but let me know if you need 32-bit dependencies. They are from https://github.com/peavo/WinCairoRequirements Then you should be able to build with Tools/Scripts/build-webkit --wincairo --64-bit We really should update the instructions on webkit.org On Feb 25, 2016, at 12:17 AM, Thomas Brodt <thomas.brodt.li...@porabo.ch> wrote:Does this also apply for the WinCairo port? Or does this port still require cygwin? Thomas Am 24.02.2016 um 20:32 schrieb Alex Christensen: Those instructions are out of date. The most up-to-date instructions about building on Windows are http://trac.webkit.org/wiki/WindowsWithoutCygwin On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com> wrote:What is the error you are seeing? On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: Hello , I am trying to build webkit on Windows . I am following steps from https://webkit.org/building-webkit-on-windows/ However I am unable to find a way to build webkit using MSVS2015 or Cygwin . Can anyone guide here please? regards RSadhu_______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___webkit-dev mailing listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev _______ webkit-dev mailing list webkit-dev@lists.webkit.org
Re: [webkit-dev] Building Webkit on Windows
Rakesh, you are building the AppleWin port of WebKit, which only has 32-bit binaries available, but you probably want to use the WinCairo port because the license of WebKitSupportLibrary.zip says you’re not allowed to redistribute it. To build the WinCairo port, you will need to run update-webkit --wincairo and build-webkit --wincairo --64-bit. This is not the source of your build failure, though. It looks like you have your gperf executable inside of C:\Program Files… somewhere, and I believe we have never had anyone build WebKit with a configuration like this. I think the solution is to put quotes around the %s at the very end of Source/WebCore/platform/network/create-http-header-name-table. There might be a few more places where this is needed. Could you please file a bug a bugs.webkit.org with a patch if you get it working? > On Feb 27, 2016, at 2:01 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: > > > Hi Thomas, > Thank for your answer . > However my build suddenly fails and I notice , its creating 32 bit binaries . > I am attaching a build log file here . > > regards > RSadhu > > > To: achristen...@apple.com > From: thomas.brodt.li...@porabo.ch > Date: Fri, 26 Feb 2016 09:15:06 +0100 > CC: webkit-dev@lists.webkit.org > Subject: Re: [webkit-dev] Building Webkit on Windows > > Hi Alex > > thank you for your prompt answer. That is good news because in the past I had > different difficulties in setting up a functional environment with several > trial and error steps inbetween, although I tried to exactly follow the > installation guide. I tend to create a virtual machine for a reliable > building environment, so with my next one I will try without the cygwin > installation. > > We use Webkit via COM interface on Windows in our application here, so I > build rather infrequently, and with a working build, we then can live for > some time. But for our use we would need 32bit dependencies, and if I > understood correctly, there are currently only 64bit available. That doesn't > matter at the moment, but when I am ready for our next build, I would ask > again if you don't mind. > > Thanks for your help! > > Thomas > > Am 25.02.2016 um 19:17 schrieb Alex Christensen: > That also applies to the WinCairo port. I don’t think you’ll need GNU Make > any more now that we use CMake for Windows. You also shouldn’t need to > install iTunes to build and run WinCairo. With WinCairo, you will also need > the WinCairoDependencies.zip which you can get by running > Tools/Scripts/update-webkit-wincairo-libs. Right now, only the 64-bit > dependencies are included in that zip, but let me know if you need 32-bit > dependencies. They are from > <https://github.com/peavo/WinCairoRequirements>https://github.com/peavo/WinCairoRequirements > <https://github.com/peavo/WinCairoRequirements> Then you should be able to > build with Tools/Scripts/build-webkit --wincairo --64-bit > > We really should update the instructions on webkit.org <http://webkit.org/> > On Feb 25, 2016, at 12:17 AM, Thomas Brodt <thomas.brodt.li...@porabo.ch > <mailto:thomas.brodt.li...@porabo.ch>> wrote: > > Does this also apply for the WinCairo port? Or does this port still require > cygwin? > > Thomas > > Am 24.02.2016 um 20:32 schrieb Alex Christensen: > Those instructions are out of date. The most up-to-date instructions about > building on Windows are > <http://trac.webkit.org/wiki/WindowsWithoutCygwin>http://trac.webkit.org/wiki/WindowsWithoutCygwin > <http://trac.webkit.org/wiki/WindowsWithoutCygwin> > > On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com > <mailto:mmaxfi...@apple.com>> wrote: > > What is the error you are seeing? > > On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com > <mailto:rakeshsa...@hotmail.com>> wrote: > > Hello , > I am trying to build webkit on Windows . > I am following steps from > <https://webkit.org/building-webkit-on-windows/>https://webkit.org/building-webkit-on-windows/ > <https://webkit.org/building-webkit-on-windows/> > However I am unable to find a way to build webkit using MSVS2015 or Cygwin . > Can anyone guide here please? > regards > RSadhu > _______ > webkit-dev mailing list > webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> > https://lists.webkit.org/mailman/listinfo/webkit-dev > <https://lists.webkit.org/mailman/listinfo/webkit-dev> > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> &
Re: [webkit-dev] Building Webkit on Windows
Hi Thomas, Thank for your answer . However my build suddenly fails and I notice , its creating 32 bit binaries . I am attaching a build log file here . regards RSadhu To: achristen...@apple.com From: thomas.brodt.li...@porabo.ch Date: Fri, 26 Feb 2016 09:15:06 +0100 CC: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Building Webkit on Windows Hi Alex thank you for your prompt answer. That is good news because in the past I had different difficulties in setting up a functional environment with several trial and error steps inbetween, although I tried to exactly follow the installation guide. I tend to create a virtual machine for a reliable building environment, so with my next one I will try without the cygwin installation. We use Webkit via COM interface on Windows in our application here, so I build rather infrequently, and with a working build, we then can live for some time. But for our use we would need 32bit dependencies, and if I understood correctly, there are currently only 64bit available. That doesn't matter at the moment, but when I am ready for our next build, I would ask again if you don't mind. Thanks for your help! Thomas Am 25.02.2016 um 19:17 schrieb Alex Christensen: That also applies to the WinCairo port. I don’t think you’ll need GNU Make any more now that we use CMake for Windows. You also shouldn’t need to install iTunes to build and run WinCairo. With WinCairo, you will also need the WinCairoDependencies.zip which you can get by running Tools/Scripts/update-webkit-wincairo-libs. Right now, only the 64-bit dependencies are included in that zip, but let me know if you need 32-bit dependencies. They are from https://github.com/peavo/WinCairoRequirements Then you should be able to build with Tools/Scripts/build-webkit --wincairo --64-bit We really should update the instructions on webkit.org On Feb 25, 2016, at 12:17 AM, Thomas Brodt <thomas.brodt.li...@porabo.ch> wrote: Does this also apply for the WinCairo port? Or does this port still require cygwin? Thomas Am 24.02.2016 um 20:32 schrieb Alex Christensen: Those instructions are out of date. The most up-to-date instructions about building on Windows are http://trac.webkit.org/wiki/WindowsWithoutCygwin On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com> wrote: What is the error you are seeing? On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: Hello , I am trying to build webkit on Windows . I am following steps from https://webkit.org/building-webkit-on-windows/ However I am unable to find a way to build webkit using MSVS2015 or Cygwin . Can anyone guide here please? regards RSadhu ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/l
Re: [webkit-dev] Building Webkit on Windows
Hi Alex thank you for your prompt answer. That is good news because in the past I had different difficulties in setting up a functional environment with several trial and error steps inbetween, although I tried to exactly follow the installation guide. I tend to create a virtual machine for a reliable building environment, so with my next one I will try without the cygwin installation. We use Webkit via COM interface on Windows in our application here, so I build rather infrequently, and with a working build, we then can live for some time. But for our use we would need 32bit dependencies, and if I understood correctly, there are currently only 64bit available. That doesn't matter at the moment, but when I am ready for our next build, I would ask again if you don't mind. Thanks for your help! Thomas Am 25.02.2016 um 19:17 schrieb Alex Christensen: That also applies to the WinCairo port. I don’t think you’ll need GNU Make any more now that we use CMake for Windows. You also shouldn’t need to install iTunes to build and run WinCairo. With WinCairo, you will also need the WinCairoDependencies.zip which you can get by running Tools/Scripts/update-webkit-wincairo-libs. Right now, only the 64-bit dependencies are included in that zip, but let me know if you need 32-bit dependencies. They are from https://github.com/peavo/WinCairoRequirements Then you should be able to build with Tools/Scripts/build-webkit --wincairo --64-bit We really should update the instructions on webkit.org <http://webkit.org> On Feb 25, 2016, at 12:17 AM, Thomas Brodt <thomas.brodt.li...@porabo.ch <mailto:thomas.brodt.li...@porabo.ch>> wrote: Does this also apply for the WinCairo port? Or does this port still require cygwin? Thomas Am 24.02.2016 um 20:32 schrieb Alex Christensen: Those instructions are out of date. The most up-to-date instructions about building on Windows are http://trac.webkit.org/wiki/WindowsWithoutCygwin On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com <mailto:mmaxfi...@apple.com>> wrote: What is the error you are seeing? On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: Hello , I am trying to build webkit on Windows . I am following steps fromhttps://webkit.org/building-webkit-on-windows/ However I am unable to find a way to build webkit using MSVS2015 or Cygwin . Can anyone guide here please? regards RSadhu _______________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev ___________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building Webkit on Windows
That also applies to the WinCairo port. I don’t think you’ll need GNU Make any more now that we use CMake for Windows. You also shouldn’t need to install iTunes to build and run WinCairo. With WinCairo, you will also need the WinCairoDependencies.zip which you can get by running Tools/Scripts/update-webkit-wincairo-libs. Right now, only the 64-bit dependencies are included in that zip, but let me know if you need 32-bit dependencies. They are from https://github.com/peavo/WinCairoRequirements <https://github.com/peavo/WinCairoRequirements> Then you should be able to build with Tools/Scripts/build-webkit --wincairo --64-bit We really should update the instructions on webkit.org <http://webkit.org/> > On Feb 25, 2016, at 12:17 AM, Thomas Brodt <thomas.brodt.li...@porabo.ch> > wrote: > > Does this also apply for the WinCairo port? Or does this port still require > cygwin? > > Thomas > > Am 24.02.2016 um 20:32 schrieb Alex Christensen: >> Those instructions are out of date. The most up-to-date instructions about >> building on Windows are >> <http://trac.webkit.org/wiki/WindowsWithoutCygwin>http://trac.webkit.org/wiki/WindowsWithoutCygwin >> <http://trac.webkit.org/wiki/WindowsWithoutCygwin> >> >>> On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com >>> <mailto:mmaxfi...@apple.com>> wrote: >>> >>> What is the error you are seeing? >>> >>> On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu < >>> <mailto:rakeshsa...@hotmail.com>rakeshsa...@hotmail.com >>> <mailto:rakeshsa...@hotmail.com>> wrote: >>> >>>> Hello , >>>> I am trying to build webkit on Windows . >>>> I am following steps from >>>> <https://webkit.org/building-webkit-on-windows/>https://webkit.org/building-webkit-on-windows/ >>>> <https://webkit.org/building-webkit-on-windows/> >>>> However I am unable to find a way to build webkit using MSVS2015 or >>>> Cygwin . >>>> Can anyone guide here please? >>>> regards >>>> RSadhu >>>> _______ >>>> webkit-dev mailing list >>>> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>>> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >>> ___ >>> webkit-dev mailing list >>> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >>> https://lists.webkit.org/mailman/listinfo/webkit-dev >>> <https://lists.webkit.org/mailman/listinfo/webkit-dev> >> >> >> _______________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >> https://lists.webkit.org/mailman/listinfo/webkit-dev >> <https://lists.webkit.org/mailman/listinfo/webkit-dev> > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building Webkit on Windows
Does this also apply for the WinCairo port? Or does this port still require cygwin? Thomas Am 24.02.2016 um 20:32 schrieb Alex Christensen: Those instructions are out of date. The most up-to-date instructions about building on Windows are http://trac.webkit.org/wiki/WindowsWithoutCygwin On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com <mailto:mmaxfi...@apple.com>> wrote: What is the error you are seeing? On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com <mailto:rakeshsa...@hotmail.com>> wrote: Hello , I am trying to build webkit on Windows . I am following steps fromhttps://webkit.org/building-webkit-on-windows/ However I am unable to find a way to build webkit using MSVS2015 or Cygwin . Can anyone guide here please? regards RSadhu _______ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev ___________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev _______________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building Webkit on Windows
Those instructions are out of date. The most up-to-date instructions about building on Windows are http://trac.webkit.org/wiki/WindowsWithoutCygwin > On Feb 24, 2016, at 9:57 AM, Myles C. Maxfield <mmaxfi...@apple.com> wrote: > > What is the error you are seeing? > > On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com > <mailto:rakeshsa...@hotmail.com>> wrote: > >> Hello , >> I am trying to build webkit on Windows . >> I am following steps from https://webkit.org/building-webkit-on-windows/ >> <https://webkit.org/building-webkit-on-windows/> >> However I am unable to find a way to build webkit using MSVS2015 or Cygwin . >> Can anyone guide here please? >> regards >> RSadhu >> ___ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> >> https://lists.webkit.org/mailman/listinfo/webkit-dev >> <https://lists.webkit.org/mailman/listinfo/webkit-dev> > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> > https://lists.webkit.org/mailman/listinfo/webkit-dev > <https://lists.webkit.org/mailman/listinfo/webkit-dev> ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building Webkit on Windows
What is the error you are seeing? > On Feb 24, 2016, at 9:26 AM, Rakesh Sadhu <rakeshsa...@hotmail.com> wrote: > > Hello , > I am trying to build webkit on Windows . > I am following steps from https://webkit.org/building-webkit-on-windows/ > However I am unable to find a way to build webkit using MSVS2015 or Cygwin . > Can anyone guide here please? > regards > RSadhu > ___________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev ___________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Building Webkit on Windows
Hello , I am trying to build webkit on Windows . I am following steps from https://webkit.org/building-webkit-on-windows/ However I am unable to find a way to build webkit using MSVS2015 or Cygwin . Can anyone guide here please? regards RSadhu___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Fall WebKit Contributors Meeting
Hi WebKit Contributors! I have some details for you about the Contributors Meeting starting tomorrow. We will be starting at 9:30 AM on Wednesday morning to set the agenda. Be sure to add your ideas for discussion topics at: http://trac.webkit.org/wiki/November%202015%20Meeting When you arrive at 1 Infinite Loop you’ll want to drive around to IL4 and park in the lots in front of the building. Next head in through the front entrance of IL4. Once inside, take the stairs on the left to the second floor. Name tags will be available for you there. Find yours and head to conference room Garage I. Attendees to the meeting There will be a reception after the meeting at BJ’s Brewhouse on Thursday from 6-8 PM. If you have any questions, or need help with anything, feel free to reach out to me or ping me on Twitter @jonathandavis. Thanks for attending being part of the WebKit project. Look forward to seeing all of you tomorrow! Jon Davis Web Technology Evangelist smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Fall WebKit Contributors Meeting - Registration Open
I've created a new wiki page as usual: http://trac.webkit.org/wiki/November%202015%20Meeting ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Fall WebKit Contributors Meeting - Registration Open
Hello WebKit Contributors, Apple will again be hosting a WebKit Contributors Meeting this year. We’re moving the meeting to the fall timeframe in order to align contributor input with feature development. It will be held on Apple’s Infinite Loop campus in Cupertino on Wednesday, November 11, and Thursday, November 12. Following the precedent, the event will use an "unconference" format, allowing time for impromptu sessions, discussions, and hacking. As always, to attend you must be an active WebKit contributor. The meeting will be free of charge, and registration is open. Sign up at http://www.webkit.org/meeting to reserve your spot. Registration deadline is Thursday, October 29. We look forward to seeing you there! Thanks, Jon Davis smime.p7s Description: S/MIME cryptographic signature _______ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Updated WebKit Project Logo
On Aug 1, 2015, at 12:11 AM, Chris Aljoudi ch...@chrismatic.io wrote: Now that you mention the WebKit nightly builds on OS X, though, it seems like that icon could use an update, too. We were in the process of getting an updated nightly icon from Apple’s design team. I posted a patch to swap-in what they created. https://bugs.webkit.org/show_bug.cgi?id=147684 I put together an idea (see attached image) for one possible design. Thanks for showing what you designed. The blueprint look is something Jon has been exploring for parts of the redesigned website. — Timothy Hatcher ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Updated WebKit Project Logo
I’d like to introduce the mailing list to the newly redesigned WebKit project logo! The new logo moves the project away from the Safari logo while paying homage to the project heritage. It carries over over familiar elements from the old icon including the yellow/gold and compass rose. Our intent is to start using this art for the WebKit project on a redesigned web site, presentations and the like to represent the WebKit technology stack. We do not intend for this to be used as the app icon for WebKit Nightly builds or for other applications. -- Jon Davis ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests and run-perf-tests scripts now use WebKitTestRunner by default
On Mar 5, 2015, at 12:14 PM, Chris Dumez cdu...@apple.com wrote: Hi, I just wanted to let you know that run-webkit-tests and run-perf-tests now use WebKitTestRunner by default after [1]. Passing —webkit-test-runner or -2 to these scripts is no longer needed (and no longer works). If you wish to run DumpRenderTree, you should pass —dump-render-tree or -1 to these scripts. I think that now we’ve done this, we should make LayoutTests/platform/mac/ contain WK2 results by default, and place WK1 exceptions in platform/mac-wk1. Same for other platforms. Thoughts? Simon ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests and run-perf-tests scripts now use WebKitTestRunner by default
On Apr 12, 2015, at 10:29 AM, Simon Fraser simon.fra...@apple.com wrote: I think that now we’ve done this, we should make LayoutTests/platform/mac/ contain WK2 results by default, and place WK1 exceptions in platform/mac-wk1. Same for other platforms. Thoughts? I agree, we should do that. — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] run-webkit-tests and run-perf-tests scripts now use WebKitTestRunner by default
Hi, I just wanted to let you know that run-webkit-tests and run-perf-tests now use WebKitTestRunner by default after [1]. Passing —webkit-test-runner or -2 to these scripts is no longer needed (and no longer works). If you wish to run DumpRenderTree, you should pass —dump-render-tree or -1 to these scripts. Kr, -- Chris Dumez - Apple Inc. - Cupertino, CA [1] https://trac.webkit.org/r181093 https://trac.webkit.org/r181093___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Move WebKit Objective-C code to ARC?
On Feb 24, 2015, at 9:34 AM, Anders Carlsson ander...@apple.com wrote: ARC doesn’t work on 32-bit Intel. It also doesn’t work with GC. Oops. OK, some day when we don’t need to support either of those on Mac. I guess it will be a while. — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Move WebKit Objective-C code to ARC?
Hi folks. I believe that WebKit tip of tree on the Cocoa platforms now supports platforms with a new-enough version of the Objective-C runtime that we could move our Objective-C code to use ARC instead of manual retain/release. Does anyone know of a reason we couldn’t start making this change to WebKit? I thought of this when I saw recent patches Joe did to fix retain/release mistakes with RetainPtr on Objective-C objects. Those mistakes would be nearly impossible if we moved to ARC. — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Move WebKit Objective-C code to ARC?
ARC doesn’t work on 32-bit Intel. It also doesn’t work with GC. - Anders On Feb 24, 2015, at 9:27 AM, Darin Adler da...@apple.com wrote: Hi folks. I believe that WebKit tip of tree on the Cocoa platforms now supports platforms with a new-enough version of the Objective-C runtime that we could move our Objective-C code to use ARC instead of manual retain/release. Does anyone know of a reason we couldn’t start making this change to WebKit? I thought of this when I saw recent patches Joe did to fix retain/release mistakes with RetainPtr on Objective-C objects. Those mistakes would be nearly impossible if we moved to ARC. — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Friday, January 23, 2015, Darin Adler da...@apple.com wrote: On Jan 22, 2015, at 10:36 PM, Alexey Proskuryakov a...@webkit.org javascript:; wrote: 22 янв. 2015 г., в 17:57, Darin Adler da...@apple.com javascript:; написал(а): What about the test I cited? svg/css/svg-resource-fragment-identifier-img-src.html This particular test is buggy - it is a hidpi test, so it dumps results as a 1600x1200 image, but its -expected.html is not hidpi, and is dumped as 800x600, so hashes are obviously different. I now filed https://bugs.webkit.org/show_bug.cgi?id=140815 about this test. When we compare pixels, we draw both images into bitmaps of the same size, so they become similar enough for ImageDiff to consider them identical. Earlier today, Simon and I agreed that we should just silence the error message, because it only tells us about minor color differences that are inevitable when comparing compositing vs. non-compositing. Looks like it tells us about more actionable issues, too. Also, I just found https://bugs.webkit.org/show_bug.cgi?id=69444, and I think that its rationale applies in this case, too. So we should probably keep this error message. I'm not sure whether we should make it a hard error though. I think that to improve things we should make an informative message for this particular mistake where the expected file has the wrong size or resolution. For me, the bad thing about the current message is not simply that it’s a false positive, but that it’s an unclear error message that covers too many different possibilities. I’m not sure that keeping things as is will be a good strategy. A message that is often expected but sometimes indicates a real problem is not good for the project. The average engineer has no idea whether to ignore these or act on them! We could add a new test expectation like ImageDiff to suppress these or we could expose a new internals or testRunner methods to mark a test as such. - R. Niwa -- - R. Niwa ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Jan 23, 2015, at 10:01 AM, Ryosuke Niwa rn...@webkit.org wrote: On Friday, January 23, 2015, Darin Adler da...@apple.com mailto:da...@apple.com wrote: On Jan 22, 2015, at 10:36 PM, Alexey Proskuryakov a...@webkit.org javascript:; wrote: 22 янв. 2015 г., в 17:57, Darin Adler da...@apple.com javascript:; написал(а): What about the test I cited? svg/css/svg-resource-fragment-identifier-img-src.html This particular test is buggy - it is a hidpi test, so it dumps results as a 1600x1200 image, but its -expected.html is not hidpi, and is dumped as 800x600, so hashes are obviously different. I now filed https://bugs.webkit.org/show_bug.cgi?id=140815 https://bugs.webkit.org/show_bug.cgi?id=140815 about this test. When we compare pixels, we draw both images into bitmaps of the same size, so they become similar enough for ImageDiff to consider them identical. Earlier today, Simon and I agreed that we should just silence the error message, because it only tells us about minor color differences that are inevitable when comparing compositing vs. non-compositing. Looks like it tells us about more actionable issues, too. Also, I just found https://bugs.webkit.org/show_bug.cgi?id=69444 https://bugs.webkit.org/show_bug.cgi?id=69444, and I think that its rationale applies in this case, too. So we should probably keep this error message. I'm not sure whether we should make it a hard error though. I think that to improve things we should make an informative message for this particular mistake where the expected file has the wrong size or resolution. For me, the bad thing about the current message is not simply that it’s a false positive, but that it’s an unclear error message that covers too many different possibilities. I’m not sure that keeping things as is will be a good strategy. A message that is often expected but sometimes indicates a real problem is not good for the project. The average engineer has no idea whether to ignore these or act on them! Agreed. The size difference certainly needs to be a failure. We could add a new test expectation like ImageDiff to suppress these or we could expose a new internals or testRunner methods to mark a test as such. I don’t think that addresses the issue. Darin’s point is that if a developer sees this output (possibly when running tests after making a change), it needs to describe something actionable. Just suppressing this output for existing tests doesn’t help when the output crops up unexpectedly. Simon ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
23 янв. 2015 г., в 10:01, Ryosuke Niwa rn...@webkit.org написал(а): We could add a new test expectation like ImageDiff to suppress these or we could expose a new internals or testRunner methods to mark a test as such. Good idea! An ImageHashMismatch expectation seems like a reasonable way to silence the noise. Also, I am surprised that we weren't getting a specific message about size mismatch here, as Darin suggested. In fact, we used to have this very output on other tests until very recently (see https://bugs.webkit.org/show_bug.cgi?id=139884). - Alexey ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Jan 22, 2015, at 10:36 PM, Alexey Proskuryakov a...@webkit.org wrote: 22 янв. 2015 г., в 17:57, Darin Adler da...@apple.com написал(а): What about the test I cited? svg/css/svg-resource-fragment-identifier-img-src.html This particular test is buggy - it is a hidpi test, so it dumps results as a 1600x1200 image, but its -expected.html is not hidpi, and is dumped as 800x600, so hashes are obviously different. I now filed https://bugs.webkit.org/show_bug.cgi?id=140815 about this test. When we compare pixels, we draw both images into bitmaps of the same size, so they become similar enough for ImageDiff to consider them identical. Earlier today, Simon and I agreed that we should just silence the error message, because it only tells us about minor color differences that are inevitable when comparing compositing vs. non-compositing. Looks like it tells us about more actionable issues, too. Also, I just found https://bugs.webkit.org/show_bug.cgi?id=69444, and I think that its rationale applies in this case, too. So we should probably keep this error message. I'm not sure whether we should make it a hard error though. I think that to improve things we should make an informative message for this particular mistake where the expected file has the wrong size or resolution. For me, the bad thing about the current message is not simply that it’s a false positive, but that it’s an unclear error message that covers too many different possibilities. I’m not sure that keeping things as is will be a good strategy. A message that is often expected but sometimes indicates a real problem is not good for the project. The average engineer has no idea whether to ignore these or act on them! — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Thu, Jan 22, 2015 at 1:56 PM, Darin Adler da...@apple.com wrote: On Jan 22, 2015, at 12:58 PM, Dirk Pranke dpra...@chromium.org wrote: Of course, Chromium was more willing to incur the cost of keeping all of the pixel tests up to date when trivial things changed the output This comment, and much of the discussion, seems to be about pixel tests. But what does this have to do with reference tests? The message has nothing to do with whether the test is a pixel test or a ref test. My reply was intended to explain why we had the hashes didn't match but diff passed message, and the discrepancy around fuzzy matching; on the Chromium ports, if run-webkit-tests had printed this message, it would've served as a warning to the user/developer that there was something weird going on. If you all decide you wanted to keep fuzzy matching enabled (and hence that message would happen regularly and could be safely ignored), I would either delete the message outright or at least make it be a debug message. You could also decide you wanted to do fuzzy matching only on ref tests, or only on pixel tests, and change the logic accordingly, of course. -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Jan 22, 2015, at 11:30 AM, Simon Fraser simon.fra...@apple.com wrote: For example, some of the tests in question render a green box either via CALayers, or by painting, and there’s a slight color difference between the two code paths. What about the test I cited? svg/css/svg-resource-fragment-identifier-img-src.html I don’t think the layer vs. painting explains the difference. Is there any reason to expect that one to have a “close but not identical” result? — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
On Jan 22, 2015, at 8:44 AM, Darin Adler da...@apple.com wrote: I noticed that when running tests I get messages like this: svg/css/svg-resource-fragment-identifier-img-src.html - ref test hashes didn't match but diff passed I understand that we can have hash mismatches in actual checked in images (expected.png files), and there, at least, I believe the fix might be to regenerate the image. But for a ref test I am really unclear on this. And further, I think it’s distracting to get messages like this unless you are specifically working on the testing infrastructure. Why should the average WebKit engineer care about this? Does this reflect a real performance problem when running tests? If so, who would fix it and what would that person do? Alexey, Tim and I looked at this yesterday. This happens when the expected and actual images are very close, but not identical. ImageDiff has some built-in rounding that effectively acts as a small tolerance, so the hashes are different, but ImageDiff incorrectly says the images are the same. For example, some of the tests in question render a green box either via CALayers, or by painting, and there’s a slight color difference between the two code paths. My preference for how to fix this would be to fix ImageDiff to remove its slight built-in tolerance, and then to expose testRunner API to allow a test to set an explicit tolerance. There are many cases where we’d like to use ref tests, but are unable to because of slight, justifiable rendering differences, and having an explicit tolerance would permit the use of ref tests in these cases. Simon ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
22 янв. 2015 г., в 11:30, Simon Fraser simon.fra...@apple.com написал(а): This happens when the expected and actual images are very close, but not identical. ImageDiff has some built-in rounding that effectively acts as a small tolerance, so the hashes are different, but ImageDiff incorrectly says the images are the same. For example, some of the tests in question render a green box either via CALayers, or by painting, and there’s a slight color difference between the two code paths. My preference for how to fix this would be to fix ImageDiff to remove its slight built-in tolerance, and then to expose testRunner API to allow a test to set an explicit tolerance. There are many cases where we’d like to use ref tests, but are unable to because of slight, justifiable rendering differences, and having an explicit tolerance would permit the use of ref tests in these cases. One thing about tolerance is that it is super confusing - are we talking about the number of pixels that are different, or about how different the pixels are? Also, a lot of failures only cause small differences in pixel results. Even a 100x100 box that becomes red instead of green is only a small portion of the 800x600 image, and it's even more the case for tests that check e.g. text rendering. It is not currently known what the root causes are for the tests that say ref test hashes didn't match but diff passed. Given that the differences are very tiny, one guess is that even though compositing and non-compositing code paths are mathematically equivalent, there are different rendering steps taken, and rounding at each step adds up to slight differences. Another theory is that we have actual bugs, such as with color management. If it's just rounding differences, then the right thing to do is probably to silence the console output, keeping behavior the same otherwise. - Alexey ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] run-webkit-tests question; hashes when comparing ref test output
I noticed that when running tests I get messages like this: svg/css/svg-resource-fragment-identifier-img-src.html - ref test hashes didn't match but diff passed I understand that we can have hash mismatches in actual checked in images (expected.png files), and there, at least, I believe the fix might be to regenerate the image. But for a ref test I am really unclear on this. And further, I think it’s distracting to get messages like this unless you are specifically working on the testing infrastructure. Why should the average WebKit engineer care about this? Does this reflect a real performance problem when running tests? If so, who would fix it and what would that person do? — Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] run-webkit-tests question; hashes when comparing ref test output
22 янв. 2015 г., в 17:57, Darin Adler da...@apple.com написал(а): What about the test I cited? svg/css/svg-resource-fragment-identifier-img-src.html This particular test is buggy - it is a hidpi test, so it dumps results as a 1600x1200 image, but its -expected.html is not hidpi, and is dumped as 800x600, so hashes are obviously different. I now filed https://bugs.webkit.org/show_bug.cgi?id=140815 about this test. When we compare pixels, we draw both images into bitmaps of the same size, so they become similar enough for ImageDiff to consider them identical. Earlier today, Simon and I agreed that we should just silence the error message, because it only tells us about minor color differences that are inevitable when comparing compositing vs. non-compositing. Looks like it tells us about more actionable issues, too. Also, I just found https://bugs.webkit.org/show_bug.cgi?id=69444, and I think that its rationale applies in this case, too. So we should probably keep this error message. I'm not sure whether we should make it a hard error though. - Alexey ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing WebKit for Wayland
as a shared library and loaded by the Wayland compositor, enabling the WebProcess to act as a direct client of the compositor while still being controlled by the UIProcess. EGL, the Wayland EGL platform, and OpenGL ES are used for hardware-accelerated compositing of the rendered Web content. GLib, Libsoup and Cairo are used under the hood. The port serves as a good base for building systems and environments that are mostly or completely relying on the Web platform technologies for building the desired interface. Overall the port is still in its early days, with some basic functionality (e.g. functional keyboard and mouse input support) and many other Web platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it.https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing WebKit for Wayland
platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it.https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev -- Sent from Gyuyoung Iphone ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing WebKit for Wayland
-accelerated compositing of the rendered Web content. GLib, Libsoup and Cairo are used under the hood. The port serves as a good base for building systems and environments that are mostly or completely relying on the Web platform technologies for building the desired interface. Overall the port is still in its early days, with some basic functionality (e.g. functional keyboard and mouse input support) and many other Web platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it.https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev -- Sent from Gyuyoung Iphone ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Announcing WebKit for Wayland
Hi, Igalia is happy to announce the Wayland port of WebKit. This port avoids using traditional GUI toolkits in favor of directly operating with the Wayland display protocol. Leveraging the WebKit2 multi-process architecture, the UIProcess is implemented as a shared library and loaded by the Wayland compositor, enabling the WebProcess to act as a direct client of the compositor while still being controlled by the UIProcess. EGL, the Wayland EGL platform, and OpenGL ES are used for hardware-accelerated compositing of the rendered Web content. GLib, Libsoup and Cairo are used under the hood. The port serves as a good base for building systems and environments that are mostly or completely relying on the Web platform technologies for building the desired interface. Overall the port is still in its early days, with some basic functionality (e.g. functional keyboard and mouse input support) and many other Web platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it. https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing WebKit for Wayland
Hi, now with proper formatting, Igalia is happy to announce the Wayland port of WebKit. This port avoids using traditional GUI toolkits in favor of directly operating with the Wayland display protocol. Leveraging the WebKit2 multi-process architecture, the UIProcess is implemented as a shared library and loaded by the Wayland compositor, enabling the WebProcess to act as a direct client of the compositor while still being controlled by the UIProcess. EGL, the Wayland EGL platform, and OpenGL ES are used for hardware-accelerated compositing of the rendered Web content. GLib, Libsoup and Cairo are used under the hood. The port serves as a good base for building systems and environments that are mostly or completely relying on the Web platform technologies for building the desired interface. Overall the port is still in its early days, with some basic functionality (e.g. functional keyboard and mouse input support) and many other Web platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it. https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards, Zan Dobersek On Tue, Dec 9, 2014 at 7:28 AM, Žan Doberšek zandober...@gmail.com wrote: Hi, Igalia is happy to announce the Wayland port of WebKit. This port avoids using traditional GUI toolkits in favor of directly operating with the Wayland display protocol. Leveraging the WebKit2 multi-process architecture, the UIProcess is implemented as a shared library and loaded by the Wayland compositor, enabling the WebProcess to act as a direct client of the compositor while still being controlled by the UIProcess. EGL, the Wayland EGL platform, and OpenGL ES are used for hardware-accelerated compositing of the rendered Web content. GLib, Libsoup and Cairo are used under the hood. The port serves as a good base for building systems and environments that are mostly or completely relying on the Web platform technologies for building the desired interface. Overall the port is still in its early days, with some basic functionality (e.g. functional keyboard and mouse input support) and many other Web platform features still not supported. But with Wayland EGL support constantly growing in graphics drivers for different GPUs, it can already be tested on devices like the Raspberry Pi or the Jetson TK1 development board. In terms of supported Wayland compositors, for the moment we only support Weston (the reference Wayland compositor implementation), which is also used for development purposes. It's also used for running the layout tests by again pushing WebKitTestRunner functionality into a shared library, though all that is still in very early stages. The code is available on GitHub. There are also short instructions for building the dependencies and the port, and how to run it. https://github.com/WebKitForWayland/webkit There's also additional repositories there (for Cairo, Weston), containing changes that haven't yet been pushed upstream. In the following days we'll also be providing Buildroot configurations that can be used for cross-compiling the whole software stack for the supported hardware. We look forward to continuing evolving this work, enabling further features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing WebKit for Wayland
features and improving performance on the software side and adding support for additional devices. As with all open-source projects, contributions are welcome. Regards,Zan Dobersek ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev