On Thursday, June 18, 2015 at 9:32:30 PM UTC+2, Chris Peterson wrote:
> It sounds like there are three use cases for WEBGL_debug_renderer_info:
>
> 1. Correlating GPU info with bug reports (e.g. YouTube).
> 2. Web content workarounds for GPU bugs.
> 3. Fingerprinting for user tracking.
There are
On Tue, May 5, 2015 at 12:03 AM, Daniel Holbert
wrote:
> Without getting too deep into the exact details about animation /
> notifications / permissions, it sounds like Florian's concern RE
> "browsers want to disable fullscreen if you are not serving the website
> over HTTPS" may be unfounded, t
On Mon, May 4, 2015 at 8:06 PM, Eric Rescorla wrote:
>
> I'm going to refer you at this point to the W3C HTML design principles of
> priority of constituencies
> (http://www.w3.org/TR/html-design-principles/#priority-of-constituencies).
>
> "In case of conflict, consider users over authors over im
On Mon, May 4, 2015 at 3:38 PM, Adam Roach wrote:
> others who want to work for a better future
>
A client of mine whom I polled if they can move to HTTPs with their server
stated they do not have the time and resources to do so. So the fullscreen
button will just stop working. That's an amazing
On Mon, May 4, 2015 at 6:33 PM, Adam Roach wrote:
> You have made some well-thought-out contributions to conversations at
> Mozilla in the past. I'm a little sad that you're choosing not to
> participate in a useful way here.
>
I think this is a pretty relevant contribution. Obviously it's not
On Sat, May 2, 2015 at 11:57 AM, Nicholas Nethercote wrote:
> Please refrain from further discussion until you can avoid making
> crude personal attacks such as these.
>
I now mandate that you (and everyone you know) shall only do ethernet
trough pigeon carriers. There are great advantages to doi
6 matches
Mail list logo
