Re: [webkit-dev] First stab at exporting tests to WPT

[Alexandre GOUAILLARD]

thanks anne for correcting me.

I'm getting well identified, automated "waves" of sync commits from google,
but I had left the mozilla ones pass me.

thanks young for the info on apple policy moving forward. That explain why
a lot of the messages today were about the Fetch API i guess ;-)

On Wed, Mar 22, 2017 at 11:08 PM, youenn fablet  wrote:

> Yes, Mozilla and Chromium are doing two-side synchronization, with
> different variants.
> The current strategy here is doing export on a per-bug basis.
>
>
> Le mer. 22 mars 2017 à 08:06, Anne van Kesteren  a
> écrit :
>
>> On Wed, Mar 22, 2017 at 3:55 PM, Alexandre GOUAILLARD
>>  wrote:
>> > that s great to have now chrome AND webkit doing it. I hope mozilla and
>> the
>> > other will follow, as discussed on the side of BlinkOn last year.
>>
>> FWIW, Mozilla already periodically synchronizes with WPT. Think we
>> were first even.
>>
>>
>> --
>> https://annevankesteren.nl/
>>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] First stab at exporting tests to WPT

[Alexandre GOUAILLARD]

yeah, I saw you flooding my wpt mailbox today :-)

that s great to have now chrome AND webkit doing it. I hope mozilla and the
other will follow, as discussed on the side of BlinkOn last year.

We' ll try to review everything as fast as possible.

cheers.

On Wed, Mar 22, 2017 at 10:53 PM, youenn fablet  wrote:

> Hi,
>
> I started writing a script to automate PRs to W3C WPT Github repository at
> https://bugs.webkit.org/show_bug.cgi?id=169462.
> One can author changes directly to LayoutTests/imported/w3c/web-platform-tests
> and use the script to create a branch on your GitHub WPT clone and also the
> PR from it on W3C WPT repository.
>
> If you are interested, please have a try and contact me for any feedback
> or issue you may have.
>
> I may also be interested in hearing about any change you may have wanted
> to do on W3C tests to accommodate WebKit test environment (e.g. use of
> internals API, runtime flags...).
>
> Thanks
>y
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] minimum version of MacOSX to have the VTB?

[Alexandre GOUAILLARD]

OK great.
Current version of chrome and libwebrtc compile against 10.11+ and run on
10.9+
I will port 210974 <https://trac.webkit.org/changeset/210974> directly.
thanks jer.

On Sat, Jan 28, 2017 at 2:04 AM, Jer Noble  wrote:

>
> On Jan 25, 2017, at 10:41 PM, Alexandre GOUAILLARD 
> wrote:
>
> Dear all,
>
> I'm trying to port https://trac.webkit.org/changeset/210974 upstream.
>
> I would need to know what was the first version of MacOs X to support the
> VTB to be sure we're not breaking upstream build first.
>
> I could not find any definitive answer online, even though I saw hints
> that 10.8 might be it.
>
>
> The APIs are marked up to indicate they’re available as far back as 10.8.
> However, they may have been private in that release as well as 10.9.
> They’re definitely public in 10.10.  So builds which target 10.10 or later
> will run against OS’s as early as 10.8.
>
> -Jer
>
> Does anybody know?
>
> thanks in advance.
>
> Alex.
>
> --
> Alex. Gouaillard, PhD, PhD, MBA
> 
> 
> President - CoSMo Software Consulting, Singapore
> 
> 
> sg.linkedin.com/agouaillard
>
>-
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] minimum version of MacOSX to have the VTB?

[Alexandre GOUAILLARD]

Dear all,

I'm trying to port https://trac.webkit.org/changeset/210974 upstream.

I would need to know what was the first version of MacOs X to support the
VTB to be sure we're not breaking upstream build first.

I could not find any definitive answer online, even though I saw hints that
10.8 might be it.

Does anybody know?

thanks in advance.

Alex.

-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] exposing getUserMedia and RTCPeerConnection in Tech Preview?

[Alexandre GOUAILLARD]

To be thorough and keep everything on one thread, here is the public answer
from the original reporter:

"""
Philipp Hancke‏@HCornflower
@agouaillard @warrenjmcdonald @steely_glint @dan_jenkins @appear_in
i couldn't care less, safari is blacklisted already
"""


On Mon, Dec 12, 2016 at 6:55 AM, Alexandre GOUAILLARD  wrote:

> Patch was finalised by eric and already pushed to webkit.
>
> On Fri, Dec 2, 2016 at 8:52 PM, Alexandre GOUAILLARD <
> agouaill...@gmail.com> wrote:
>
>> first patch uploaded for your kind review.
>>
>>
>> On Thu, Dec 1, 2016 at 8:55 PM, Alexandre GOUAILLARD <
>> agouaill...@gmail.com> wrote:
>>
>>> supposedly those two?
>>>
>>> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules
>>> /mediastream/NavigatorMediaDevices.idl
>>> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules
>>> /mediastream/RTCPeerConnection.idl
>>>
>>> I opened a bug, https://bugs.webkit.org/show_bug.cgi?id=165251
>>>
>>> I'm waiting for a fresh clone, and I ll go ahead with a patch.
>>>
>>> Alex.
>>>
>>> On Thu, Dec 1, 2016 at 7:10 PM, youenn fablet  wrote:
>>>
>>>> It is good if we already have these runtime flags.
>>>> Then we might just need to make the related IDLs exposed according that
>>>> flag through EnabledAtRuntime keyword.
>>>>   y
>>>>
>>>>
>>>>
>>>> Le jeu. 1 déc. 2016 à 11:55, Alexandre GOUAILLARD <
>>>> agouaill...@gmail.com> a écrit :
>>>>
>>>>> Bonjour youenn,
>>>>>
>>>>> Eric avait fait ca en mars cette année. Tu peux regarder les commits
>>>>> ci-dessous. J'ai vérifie hier, les flags de compil sont toujours a OFF, et
>>>>> les runtimes sont aussi gardes. Je ne sais pas pourquoi les API sont
>>>>> accessibles.
>>>>>
>>>>> https://bugs.webkit.org/show_bug.cgi?id=158393
>>>>> https://trac.webkit.org/browser/trunk/Source/WebCore/binding
>>>>> s/generic/RuntimeEnabledFeatures.h?rev=202704
>>>>>
>>>>> https://trac.webkit.org/changeset/198492
>>>>>
>>>>> Note that I documented those two flags on the webkit wiki on march 26
>>>>> this year, after eric split the original MEDIA_STREAM into two:
>>>>> https://trac.webkit.org/wiki/FeatureFlags
>>>>>
>>>>> Alex.
>>>>>
>>>>>
>>>>> On Thu, Dec 1, 2016 at 6:48 PM, youenn fablet 
>>>>> wrote:
>>>>>
>>>>> Hi Philipp,
>>>>>
>>>>> Thanks for bringing that up.
>>>>> I think we should add runtime flags for getUserMedia and
>>>>> RTCPeerConnection and set them to off in Safari Tech Preview until stable
>>>>> enough.
>>>>>
>>>>> y
>>>>>
>>>>>
>>>>> Le mer. 30 nov. 2016 à 14:40, Philipp Hancke  a
>>>>> écrit :
>>>>>
>>>>> It has been brought to my attention that apparently Safari Tech
>>>>> Preview Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing
>>>>> RTCPeerConnection and navigator.mediaDevices.getUserMedia.
>>>>>
>>>>> Since a check for
>>>>>navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
>>>>> and redirecting browsers that support neither is pretty common this is
>>>>> rather unfortunate.
>>>>>
>>>>> The getUserMedia implementation does not seems to work on one of the
>>>>> most basic GUM samples at
>>>>> https://webrtc.github.io/samples/src/content/getusermedia/gum/
>>>>> I am actually not seeing GUM resolve or reject the promise at all.
>>>>>
>>>>> And RTCPeerConnection did not work either in
>>>>> https://webrtc.github.io/samples/src/content/peerconnection/pc1/
>>>>>
>>>>> What is the plan here?
>>>>>
>>>>> Philipp
>>>>> ___
>>>>> webkit-dev mailing list
>>>>> webkit-dev@lists.webkit.org
>>>>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>>>>>
>>>>>
>>>>> ___
>>>>> webkit-dev mailing list

Re: [webkit-dev] exposing getUserMedia and RTCPeerConnection in Tech Preview?

[Alexandre GOUAILLARD]

Patch was finalised by eric and already pushed to webkit.

On Fri, Dec 2, 2016 at 8:52 PM, Alexandre GOUAILLARD 
wrote:

> first patch uploaded for your kind review.
>
>
> On Thu, Dec 1, 2016 at 8:55 PM, Alexandre GOUAILLARD <
> agouaill...@gmail.com> wrote:
>
>> supposedly those two?
>>
>> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules
>> /mediastream/NavigatorMediaDevices.idl
>> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules
>> /mediastream/RTCPeerConnection.idl
>>
>> I opened a bug, https://bugs.webkit.org/show_bug.cgi?id=165251
>>
>> I'm waiting for a fresh clone, and I ll go ahead with a patch.
>>
>> Alex.
>>
>> On Thu, Dec 1, 2016 at 7:10 PM, youenn fablet  wrote:
>>
>>> It is good if we already have these runtime flags.
>>> Then we might just need to make the related IDLs exposed according that
>>> flag through EnabledAtRuntime keyword.
>>>   y
>>>
>>>
>>>
>>> Le jeu. 1 déc. 2016 à 11:55, Alexandre GOUAILLARD 
>>> a écrit :
>>>
>>>> Bonjour youenn,
>>>>
>>>> Eric avait fait ca en mars cette année. Tu peux regarder les commits
>>>> ci-dessous. J'ai vérifie hier, les flags de compil sont toujours a OFF, et
>>>> les runtimes sont aussi gardes. Je ne sais pas pourquoi les API sont
>>>> accessibles.
>>>>
>>>> https://bugs.webkit.org/show_bug.cgi?id=158393
>>>> https://trac.webkit.org/browser/trunk/Source/WebCore/binding
>>>> s/generic/RuntimeEnabledFeatures.h?rev=202704
>>>>
>>>> https://trac.webkit.org/changeset/198492
>>>>
>>>> Note that I documented those two flags on the webkit wiki on march 26
>>>> this year, after eric split the original MEDIA_STREAM into two:
>>>> https://trac.webkit.org/wiki/FeatureFlags
>>>>
>>>> Alex.
>>>>
>>>>
>>>> On Thu, Dec 1, 2016 at 6:48 PM, youenn fablet 
>>>> wrote:
>>>>
>>>> Hi Philipp,
>>>>
>>>> Thanks for bringing that up.
>>>> I think we should add runtime flags for getUserMedia and
>>>> RTCPeerConnection and set them to off in Safari Tech Preview until stable
>>>> enough.
>>>>
>>>> y
>>>>
>>>>
>>>> Le mer. 30 nov. 2016 à 14:40, Philipp Hancke  a
>>>> écrit :
>>>>
>>>> It has been brought to my attention that apparently Safari Tech Preview
>>>> Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing RTCPeerConnection
>>>> and navigator.mediaDevices.getUserMedia.
>>>>
>>>> Since a check for
>>>>navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
>>>> and redirecting browsers that support neither is pretty common this is
>>>> rather unfortunate.
>>>>
>>>> The getUserMedia implementation does not seems to work on one of the
>>>> most basic GUM samples at
>>>> https://webrtc.github.io/samples/src/content/getusermedia/gum/
>>>> I am actually not seeing GUM resolve or reject the promise at all.
>>>>
>>>> And RTCPeerConnection did not work either in
>>>> https://webrtc.github.io/samples/src/content/peerconnection/pc1/
>>>>
>>>> What is the plan here?
>>>>
>>>> Philipp
>>>> ___
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Alex. Gouaillard, PhD, PhD, MBA
>>>> 
>>>> 
>>>> President - CoSMo Software Consulting, Singapore
>>>> 
>>>> 
>>>> sg.linkedin.com/agouaillard
>>>>
>>>>-
>>>>
>>>>
>>
>>
>> --
>> Alex. Gouaillard, PhD, PhD, MBA
>> 
>> 
>> President - CoSMo Software Consulting, Singapore
>> 
>> 
>> sg.linkedin.com/agouaillard
>>
>>-
>>
>>
>
>
> --
> Alex. Gouaillard, PhD, PhD, MBA
> 
> 
> President - CoSMo Software Consulting, Singapore
> 
> 
> sg.linkedin.com/agouaillard
>
>-
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] exposing getUserMedia and RTCPeerConnection in Tech Preview?

[Alexandre GOUAILLARD]

first patch uploaded for your kind review.


On Thu, Dec 1, 2016 at 8:55 PM, Alexandre GOUAILLARD 
wrote:

> supposedly those two?
>
> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream/
> NavigatorMediaDevices.idl
> https://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream/
> RTCPeerConnection.idl
>
> I opened a bug, https://bugs.webkit.org/show_bug.cgi?id=165251
>
> I'm waiting for a fresh clone, and I ll go ahead with a patch.
>
> Alex.
>
> On Thu, Dec 1, 2016 at 7:10 PM, youenn fablet  wrote:
>
>> It is good if we already have these runtime flags.
>> Then we might just need to make the related IDLs exposed according that
>> flag through EnabledAtRuntime keyword.
>>   y
>>
>>
>>
>> Le jeu. 1 déc. 2016 à 11:55, Alexandre GOUAILLARD 
>> a écrit :
>>
>>> Bonjour youenn,
>>>
>>> Eric avait fait ca en mars cette année. Tu peux regarder les commits
>>> ci-dessous. J'ai vérifie hier, les flags de compil sont toujours a OFF, et
>>> les runtimes sont aussi gardes. Je ne sais pas pourquoi les API sont
>>> accessibles.
>>>
>>> https://bugs.webkit.org/show_bug.cgi?id=158393
>>> https://trac.webkit.org/browser/trunk/Source/WebCore/binding
>>> s/generic/RuntimeEnabledFeatures.h?rev=202704
>>>
>>> https://trac.webkit.org/changeset/198492
>>>
>>> Note that I documented those two flags on the webkit wiki on march 26
>>> this year, after eric split the original MEDIA_STREAM into two:
>>> https://trac.webkit.org/wiki/FeatureFlags
>>>
>>> Alex.
>>>
>>>
>>> On Thu, Dec 1, 2016 at 6:48 PM, youenn fablet  wrote:
>>>
>>> Hi Philipp,
>>>
>>> Thanks for bringing that up.
>>> I think we should add runtime flags for getUserMedia and
>>> RTCPeerConnection and set them to off in Safari Tech Preview until stable
>>> enough.
>>>
>>> y
>>>
>>>
>>> Le mer. 30 nov. 2016 à 14:40, Philipp Hancke  a écrit :
>>>
>>> It has been brought to my attention that apparently Safari Tech Preview
>>> Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing RTCPeerConnection
>>> and navigator.mediaDevices.getUserMedia.
>>>
>>> Since a check for
>>>navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
>>> and redirecting browsers that support neither is pretty common this is
>>> rather unfortunate.
>>>
>>> The getUserMedia implementation does not seems to work on one of the
>>> most basic GUM samples at
>>> https://webrtc.github.io/samples/src/content/getusermedia/gum/
>>> I am actually not seeing GUM resolve or reject the promise at all.
>>>
>>> And RTCPeerConnection did not work either in
>>> https://webrtc.github.io/samples/src/content/peerconnection/pc1/
>>>
>>> What is the plan here?
>>>
>>> Philipp
>>> ___
>>> 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
>>>
>>>
>>>
>>>
>>> --
>>> Alex. Gouaillard, PhD, PhD, MBA
>>> 
>>> 
>>> President - CoSMo Software Consulting, Singapore
>>> 
>>> 
>>> sg.linkedin.com/agouaillard
>>>
>>>-
>>>
>>>
>
>
> --
> Alex. Gouaillard, PhD, PhD, MBA
> 
> 
> President - CoSMo Software Consulting, Singapore
> 
> 
> sg.linkedin.com/agouaillard
>
>-
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] exposing getUserMedia and RTCPeerConnection in Tech Preview?

[Alexandre GOUAILLARD]

supposedly those two?

https://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream/NavigatorMediaDevices.idl
https://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream/RTCPeerConnection.idl

I opened a bug, https://bugs.webkit.org/show_bug.cgi?id=165251

I'm waiting for a fresh clone, and I ll go ahead with a patch.

Alex.

On Thu, Dec 1, 2016 at 7:10 PM, youenn fablet  wrote:

> It is good if we already have these runtime flags.
> Then we might just need to make the related IDLs exposed according that
> flag through EnabledAtRuntime keyword.
>   y
>
>
>
> Le jeu. 1 déc. 2016 à 11:55, Alexandre GOUAILLARD 
> a écrit :
>
>> Bonjour youenn,
>>
>> Eric avait fait ca en mars cette année. Tu peux regarder les commits
>> ci-dessous. J'ai vérifie hier, les flags de compil sont toujours a OFF, et
>> les runtimes sont aussi gardes. Je ne sais pas pourquoi les API sont
>> accessibles.
>>
>> https://bugs.webkit.org/show_bug.cgi?id=158393
>> https://trac.webkit.org/browser/trunk/Source/WebCore/bindings/generic/
>> RuntimeEnabledFeatures.h?rev=202704
>>
>> https://trac.webkit.org/changeset/198492
>>
>> Note that I documented those two flags on the webkit wiki on march 26
>> this year, after eric split the original MEDIA_STREAM into two:
>> https://trac.webkit.org/wiki/FeatureFlags
>>
>> Alex.
>>
>>
>> On Thu, Dec 1, 2016 at 6:48 PM, youenn fablet  wrote:
>>
>> Hi Philipp,
>>
>> Thanks for bringing that up.
>> I think we should add runtime flags for getUserMedia and
>> RTCPeerConnection and set them to off in Safari Tech Preview until stable
>> enough.
>>
>> y
>>
>>
>> Le mer. 30 nov. 2016 à 14:40, Philipp Hancke  a écrit :
>>
>> It has been brought to my attention that apparently Safari Tech Preview
>> Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing RTCPeerConnection
>> and navigator.mediaDevices.getUserMedia.
>>
>> Since a check for
>>navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
>> and redirecting browsers that support neither is pretty common this is
>> rather unfortunate.
>>
>> The getUserMedia implementation does not seems to work on one of the most
>> basic GUM samples at
>> https://webrtc.github.io/samples/src/content/getusermedia/gum/
>> I am actually not seeing GUM resolve or reject the promise at all.
>>
>> And RTCPeerConnection did not work either in
>> https://webrtc.github.io/samples/src/content/peerconnection/pc1/
>>
>> What is the plan here?
>>
>> Philipp
>> ___
>> 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
>>
>>
>>
>>
>> --
>> Alex. Gouaillard, PhD, PhD, MBA
>> 
>> 
>> President - CoSMo Software Consulting, Singapore
>> 
>> 
>> sg.linkedin.com/agouaillard
>>
>>-
>>
>>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] exposing getUserMedia and RTCPeerConnection in Tech Preview?

[Alexandre GOUAILLARD]

Bonjour youenn,

Eric avait fait ca en mars cette année. Tu peux regarder les commits
ci-dessous. J'ai vérifie hier, les flags de compil sont toujours a OFF, et
les runtimes sont aussi gardes. Je ne sais pas pourquoi les API sont
accessibles.

https://bugs.webkit.org/show_bug.cgi?id=158393
https://trac.webkit.org/browser/trunk/Source/WebCore/bindings/generic/
RuntimeEnabledFeatures.h?rev=202704

https://trac.webkit.org/changeset/198492

Note that I documented those two flags on the webkit wiki on march 26 this
year, after eric split the original MEDIA_STREAM into two:
https://trac.webkit.org/wiki/FeatureFlags

Alex.


On Thu, Dec 1, 2016 at 6:48 PM, youenn fablet  wrote:

> Hi Philipp,
>
> Thanks for bringing that up.
> I think we should add runtime flags for getUserMedia and RTCPeerConnection
> and set them to off in Safari Tech Preview until stable enough.
>
> y
>
>
> Le mer. 30 nov. 2016 à 14:40, Philipp Hancke  a écrit :
>
>> It has been brought to my attention that apparently Safari Tech Preview
>> Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing RTCPeerConnection
>> and navigator.mediaDevices.getUserMedia.
>>
>> Since a check for
>>navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
>> and redirecting browsers that support neither is pretty common this is
>> rather unfortunate.
>>
>> The getUserMedia implementation does not seems to work on one of the most
>> basic GUM samples at
>> https://webrtc.github.io/samples/src/content/getusermedia/gum/
>> I am actually not seeing GUM resolve or reject the promise at all.
>>
>> And RTCPeerConnection did not work either in
>> https://webrtc.github.io/samples/src/content/peerconnection/pc1/
>>
>> What is the plan here?
>>
>> Philipp
>> ___
>> 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
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA

President - CoSMo Software Consulting, Singapore

sg.linkedin.com/agouaillard

   -
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Trying to turn WebRTC's code on - MEDIA_STREAM flags

[Alexandre GOUAILLARD]

Benjamin,

For clarification of the  goals and the scope, we intend to provide patches
in webkit for webRTC. We would love to see webRTC support in iOS and we
understand that having it in apple provided webkit (UIWebView) to comply to
apple store rule 2.17. We understand we do not have complete control over
the entire process, especially the eventual packaging and deployment, and
the timelines, and that apple does not comment about this, but we thought
implementing it in webkit was a necessary prerequisite in any case. For the
rest we will have faith :-)

During a phone conversation with eric C, we've ben told that we should
start by making it happen in the macOS X port as we would snot be able to
build for iOS and because the differences were not so big between the iOS
and the macOS ports.

JO has been working on the Media Capture and Stream and webRTC APIs for
almost a year, and developed an IE and Safari plugin that implements all of
the APIs. He reads/speaks/write web IDL fluently now, and now all the
subtleties of the constraints, streams, tracks, ect. I sit at the standard
committees and help with everything that is not clear from the specs.
Unfortunately, that does not help understand webkit intricacies and that's
where we are today.

We reached out to Eric C, Thiago from nokia (NIX port), kirun from samsung,
and started from there. I also speak regularly with adam Be. from ericson
at the w3c meetings. I will jump in the project and add an additional
senior staff, so we should be 2~3 FTE starting tuesday. Looking at philippe
N works in WK2, it looks like you would be a reviewer of any patch we would
submit, correct? (bug )

With our target (iOS/MacOS X) should we target WK1 or WK2? We plan to
finalize the webcore part first, but we need to target an app, and a port
for testing. NIX does not seem to be an option anymore.

There also seem to have been a discussion about the design (platform vs
client) triggered by adam Be.. Anybody knows if there was a conclusion? (bug
) We would prefer putting a
maximum of common code in webcore, as proposed by adam.

We are also contributing some tests to w3c (based on testharness.js,
testing the bindings and IDL only) that we plan to use for testing.
Dominique has recently committed the tests for steams and tracks using the
latest spec (here
).
Is there anything we should prepare in the layout tests for this as well?
It looks like the media stream tests have been excluded from the tests for
the time being.

We are trying to have a working implementation by oct 15th, so we could
send it for test around and get feedback in time for discussion during the
W3C technical plenary and advisory committee meeting on oct. 27th, in San
Jose, CA.

looking forward to any feedback.

regards,


   - Alex.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev