On Fri, Sep 29, 2017 at 11:33:08PM -0400, Boris Zbarsky wrote:
On 9/29/17 3:32 PM, Kris Maglione wrote:
For instance, the following should all capture the caller principal
for the `src` URL at call time:
document.write(`http://example.com/favicon.ico";>`);
div.innerHTML = `http://example
On 9/29/17 3:32 PM, Kris Maglione wrote:
For instance, the following should all capture the
caller principal for the `src` URL at call time:
document.write(`http://example.com/favicon.ico";>`);
div.innerHTML = `http://example.com/favicon.ico";>`;
img.setAttribute("src", "http://exam
Summary:
All content injected into web content pages is currently subject to the
same Content Security Policy, regardless of who injected it. For
privileged callers, such as extension content scripts, this means that
some functionality can behave erratically, depending on the page they're
run
As someone who has had wonderful times with ALSA & headaches with PA it's time
to say goodbye FireFox.
FireFox was my first goto browser for years now I'll add it to my purge script
just under pulseaudio.
Expecting users to give up 2 hours & 15Gb just to get alsa support in a browser
is tbf poi
Now instead we will get to try to phrase code in a way that
clang-format will preserve readably?
I should think "it doesn't always produce nice formatting, but it's at
least consistent" sounds like a major warning sign, particularly given
that we definitely have tricky code for which we have made
Le 28/09/2017 à 23:21, Randell Jesup a écrit :
>> On Thursday, September 28, 2017 at 10:15:05 AM UTC+2, Chris Pearce wrote:
>> Oh d'oh! Looks like I replied to an old thread, and the plan now is in fact
>> to clang-format the entire tree after 57. Sweet as!
> Where did you find that? Was this plan
6 matches
Mail list logo
