Hi all,
I've spent the last month or so 'finishing' the implementation of
OffscreenCanvas[1], based on Žan Doberšek's work from a year ago[2].
OffscreenCanvas is an API for being able to use canvas drawing without a
visible canvas, and from within Workers. It's supported by Blink and has
partial s
Hi Chris!
Canvas is a very popular GPU fingerprinting vector and allowing it offscreen
sounds like a more convenient way to perform such an attack on user privacy. Do
you know if Blink or Gecko have elaborated on this? What is your assessment?
Given the cross-engine effort to fight device finge
On 09/10/2019 21:53, Maciej Stachowiak wrote:
> In terms of legalities:
>
> The WebKit logo (as well as the term WebKit) is trademarked by Apple, but
> there are acceptable use guidelines in the Terms of Use:
> https://webkit.org/terms-of-use/ . I am not a lawyer and cannot give legal
> advice,
Hi John,
I don't know what the current state is of counter-measures for such an
attack, but I don't immediately imagine OffscreenCanvas would make them
more effective. The patch series doesn't add any new rendering paths, so
whatever was possible before will likely still be possible and whatever
w
For clarity, it’s already possible to render to a regular canvas offscreen. The
can be hidden using any of the techniques that can make any other
canvas invisible. Name notwithstanding, OffscreenCanvas is mainly about being
able to render from a Worker, not about enabling rendering offscreen.
> On Oct 10, 2019, at 9:42 AM, Maciej Stachowiak wrote:
>
> For clarity, it’s already possible to render to a regular canvas offscreen.
> The can be hidden using any of the techniques that can make any
> other canvas invisible. Name notwithstanding, OffscreenCanvas is mainly about
> being abl
> On Oct 10, 2019, at 10:18 AM, John Wilander wrote:
>
>> On Oct 10, 2019, at 9:42 AM, Maciej Stachowiak wrote:
>>
>> For clarity, it’s already possible to render to a regular canvas offscreen.
>> The can be hidden using any of the techniques that can make any
>> other canvas invisible. Na
Hi Chris,
I'm excited that you're working on OffscreenCanvas because I think it would
be a valuable feature, and I'm confident we can come up with a strategy to
limit its privacy & security risk as we see fit.
However, many of your patches seem to ignore the fact most of WebCore
objects aren't th
On Thu, Oct 10, 2019 at 9:03 AM Carlos Alberto Lopez Perez <
clo...@igalia.com> wrote:
> On 09/10/2019 21:53, Maciej Stachowiak wrote:
> > In terms of legalities:
> >
> > The WebKit logo (as well as the term WebKit) is trademarked by Apple,
> but there are acceptable use guidelines in the Terms of
> On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa wrote:
>
> Hi Chris,
>
> I'm excited that you're working on OffscreenCanvas because I think it would
> be a valuable feature
Me too!!!
> , and I'm confident we can come up with a strategy to limit its privacy &
> security risk as we see fit.
>
On Thu, Oct 10, 2019 at 2:07 PM Myles C. Maxfield
wrote:
>
>
> On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa wrote:
>
> Hi Chris,
>
> I'm excited that you're working on OffscreenCanvas because I think it
> would be a valuable feature
>
>
> Me too!!!
>
> , and I'm confident we can come up with a str
Sorry for the delay.
We agree that scroll anchoring has unrealized potential to be valuable for
the web at large, and to make that happen we should be investing a lot more
working with y'all (and if we can't succeed, probably removing it from
chromium). Concretely +Chris Harrelson who leads render
12 matches
Mail list logo
