On 12/7/15 9:15 PM, Patrick McManus wrote:
...you should be able to just use asyncopen2 - it will do security checks
for you that you may have needed to do outside asyncopen (e.g. csp) and
will reliably deal with things like redirects.
Note that asyncOpen2 depends on there being correctly set u
..you should be able to just use asyncopen2 - it will do security checks
for you that you may have needed to do outside asyncopen (e.g. csp) and
will reliably deal with things like redirects. :sicking or :ckerschb for
followups.
On Mon, Dec 7, 2015 at 6:00 PM, Philip Chee wrote:
> I came across
I am also curious about this.
On Tue, Dec 8, 2015 at 1:00 AM, Philip Chee wrote:
> I came across Bug 1182535 [tracking bug] change all callsites to
> asyncOpen2 instead of asyncOpen
>
> What's the difference and why should I switch?
>
> Can I just do |s/asyncOpen\(/asyncOpen2\(/g| or are there s
I came across Bug 1182535 [tracking bug] change all callsites to
asyncOpen2 instead of asyncOpen
What's the difference and why should I switch?
Can I just do |s/asyncOpen\(/asyncOpen2\(/g| or are there some
subtleties I should be aware of?
Phil
--
Philip Chee ,
http://flashblock.mozdev.org/ h
4 matches
Mail list logo