On 07/03/14 07:13, Henri Sivonen wrote:
So part of the difficulty of document.write comes from the fact
that it has to interact with the script loading / document
lifecycle. Therefore it's going to be hard to get those parts of
(any) parser right until we actually implement a more correct
model
> >> I think the biggest unknown is memory management.
> >
> > Is this the only thing that's blocking compilation
>
> Unfortunately it's not. Some other problems I ran into:
OK. It looks like writing a new parser directly in Rust (possibly using a
translated Tokenizer.java as a tokenizer starti
On 2014-02-20 8:19 PM, John Daggett wrote:
Hmm. My point is that preventing fingerprinting is not something that
I think we can do by simply tweaking features here and there like
this. I think we actually need to disable a large set of features
available from script to be able to prevent sniffin
> OK. It looks like writing a new parser directly in Rust (possibly using a
> translated Tokenizer.java as a tokenizer starting point) is the sensible way
> forward. I'm sorry about wasting your time with the translator.
Not at all :) It was an interesting project and definitely an approach worth
4 matches
Mail list logo