[webkit-dev] Questions about ports

[Jacques-Olivier]

Hi everyone,

I have a couple of questions regarding the different ports of WebKit:

1) I suppose the port used by Safari Mac OS X is the Apple’s mac port (built by 
default)
Is there a planing of when a version of WebKit is being publicly released in 
Safari Mac?

2) Which port is being used by Safari iOS and how to build it?
Is there a release planning?
What is the flag to build this port?
How to test it?

3) Which port is being used to power third party applications on iOS? and how 
to build it?
Is there a release planning?
What is the flag to build this port?
How to test it?

Regards,
J-O H

--
Haché Jacques-Olivier
R&D Engineer at Temasys Communications Pte Ltd
Fr : 06 45 85 48 80
Sg : 9086 3673 

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

Re: [webkit-dev] Is anyone interested in maintaining INPUT_SPEECH?

[Chris Fleizach]

It’s never been supported on Mac, so I don’t think there are any complaints here

> On Aug 5, 2014, at 8:14 PM, TAMURA, Kent  wrote:
> 
> FYI. It was removed from Blink too.
> 
> 
> On Wed, Aug 6, 2014 at 11:40 AM, Benjamin Poulain  > wrote:
> Hi,
> 
> Is anyone interested in INPUT_SPEECH?
> 
> It looks like no port enable that feature. The code looks unmaintained. 
> Everyone skip all the tests.
> 
> I will remove the code if nobody maintains it.
> 
> Benjamin
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org 
> https://lists.webkit.org/mailman/listinfo/webkit-dev 
> 
> 
> 
> 
> -- 
> TAMURA Kent 
> Software Engineer, Google 
> 
> 
> ___
> 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] Is anyone interested in maintaining INPUT_SPEECH?

[Benjamin Poulain]

Hi,

Is anyone interested in INPUT_SPEECH?

It looks like no port enable that feature. The code looks unmaintained. 
Everyone skip all the tests.


I will remove the code if nobody maintains it.

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

Re: [webkit-dev] Is anyone interested in maintaining INPUT_SPEECH?

[TAMURA, Kent]

FYI. It was removed from Blink too.


On Wed, Aug 6, 2014 at 11:40 AM, Benjamin Poulain 
wrote:


Hi,



Is anyone interested in INPUT_SPEECH?



It looks like no port enable that feature. The code looks unmaintained.
Everyone skip all the tests.



I will remove the code if nobody maintains it.



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





--
TAMURA Kent
Software Engineer, Google



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

Re: [webkit-dev] Mixed content checking

[Michael Catanzaro]

On Tue, 2014-08-05 at 11:03 +0200, Mike West wrote:
> Apologies for digging up an old thread; I didn't see it until now.
> 
> On Thu, Jul 24, 2014 at 7:59 AM, Alexey Proskuryakov 
> wrote:
> > In other words, how is "active content" defined here?
> 
> Note that the WebAppSec WG is working on a mixed content spec that
> drops the "active"/"passive" distinction in favor of "stuff we can
> block without breaking the web"/"images":
> http://w3c.github.io/webappsec/specs/mixedcontent/#categories Feedback
> on that document would be welcome.
> 
> As Michael notes in his response, Chrome is busy tightening its
> implementation to match that spec. Some details on that in
> https://groups.google.com/a/chromium.org/d/msg/security-dev/Uxzvrqb6IeU/wb51F3nV7csJ
> 
> -mike

Thanks Mike, I will definitely read that spec and keep it in mind as an
end goal. Our mixed content blocking will probably not be so
comprehensive at first, but it's good to have a formal goal and also
indicates that I might have been mistaken to expose "block active mixed
content" and "block passive mixed content" as separate settings --
probably "block all mixed content" and "block selected mixed content"
would be more sensible levers for browsers to have.

Michael

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

Re: [webkit-dev] Mixed content checking

[Mike West]

Apologies for digging up an old thread; I didn't see it until now.

On Thu, Jul 24, 2014 at 7:59 AM, Alexey Proskuryakov  wrote:
> In other words, how is "active content" defined here?

Note that the WebAppSec WG is working on a mixed content spec that drops
the "active"/"passive" distinction in favor of "stuff we can block without
breaking the web"/"images":
http://w3c.github.io/webappsec/specs/mixedcontent/#categories Feedback on
that document would be welcome.

As Michael notes in his response, Chrome is busy tightening its
implementation to match that spec. Some details on that in
https://groups.google.com/a/chromium.org/d/msg/security-dev/Uxzvrqb6IeU/wb51F3nV7csJ

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