Hi,
On 2011-02-28 19:01, Leandro Graciá Gil wrote:
I'm glad we agree on the importance of allowing the user to revoke
device access. However we think that this point is important at the
design level rather than the implementation level. If access revoking
is introduced, then the concept of
Hi,
El 22 de febrero de 2011 12:20, Adam Bergkvist
adam.bergkv...@ericsson.comescribió:
Hi,
On 2011-02-15 17:50, Leandro Graciá Gil wrote:
Yes, the platform independent code in the device element will
determine
if a selection has been made, or altered, in the list of available
Hi,
On 2011-02-15 17:50, Leandro Graciá Gil wrote:
Yes, the platform independent code in the device element will determine
if a selection has been made, or altered, in the list of available
devices
Provided by the platform. Before passing it to the device element, the
Hi,
El 10 de febrero de 2011 15:15, Adam Bergkvist
adam.bergkv...@ericsson.comescribió:
Hi,
On 2011-02-09 22:10, Leandro Graciá Gil wrote:
So, does that mean that a WebCore platform-independent code is going
to determine if a new device handler should be created? I think that
some UAs
Hi,
On 2011-02-09 22:10, Leandro Graciá Gil wrote:
So, does that mean that a WebCore platform-independent code is going
to determine if a new device handler should be created? I think that
some UAs may like to, for example, keep a track of trusted pages for
specific types of devices to
Hi,
El 7 de febrero de 2011 18:56, Adam Bergkvist adam.bergkv...@ericsson.com
escribió:
Hi,
On 2011-02-04 19:21, Leandro Graciá Gil wrote:
This is good news! Especially for the situations where WebCore can't
directly access the hardware. One existing case of this we should keep
in mind
Hi,
On 2011-02-04 19:21, Leandro Graciá Gil wrote:
This is good news! Especially for the situations where WebCore can't
directly access the hardware. One existing case of this we should keep
in mind are the sandboxed environments, where both the probing and the
connections must be
El 3 de febrero de 2011 18:59, Adam Bergkvist adam.bergkv...@ericsson.com
escribió:
Hi,
Leandro Graciá Gil wrote:
The approach proposed in https://bugs.webkit.org/show_bug.cgi?id=47264
brings the device probing and selection to the WebCore level. It does
so by first creating a list of
El 4 de febrero de 2011 18:21, Leandro Graciá Gil
leandrogra...@chromium.org escribió:
I have also created a small diagram to explain how our implementation
works:
https://docs.google.com/a/google.com/drawings/edit?id=1jSW-6MJd8mp2qPvwnvZnBVzll6UtBz3r1viZgTE4XVAhl=enauthkey=CPLpy5oJ
It
Hi,
Leandro Graciá Gil wrote:
The approach proposed in https://bugs.webkit.org/show_bug.cgi?id=47264
brings the device probing and selection to the WebCore level. It does
so by first creating a list of available devices using an interface to
a platform-dependent client and then it passes
I have created a patch to introduce compilation guards for the device
element implementation. These should be the same independently of the design
approach we decide to take while enabling us to propose more specific
patches later. Here's the link:
https://bugs.webkit.org/show_bug.cgi?id=53595
I have created a patch to introduce compilation guards for the device
element implementation. These should be the same independently of the design
approach we decide to take while enabling us to propose more specific
patches later. Here's the link:
https://bugs.webkit.org/show_bug.cgi?id=53595
Hi,
We have recently noticed a patch to implement the device element in
WebKit. Since this is an important new feature, I thought we should have a
discussion about the best way to implement it. Here's the actual
specification for it:
13 matches
Mail list logo
