I'm concerned this will discourage websites from reporting WebGL
issues because it will be easier just to block whatever device has the
problem they're running in to. This creates an additional burden on
the web developer and essentially creates the user agent problem all
over again, but at much
On Mon, Jun 15, 2015 at 04:39:50PM -0700, Chris Peterson wrote:
On 6/15/15 4:16 PM, Jeff Gilbert wrote:
Web Developer Use-Cases:
* Sites can collate and cross-reference drivers and hardware when tracking
issues both user-reported and auto-detected, which both helps sites
identify problematic
Further to what Jeff suggested, I know that we resisted shipping this
feature when Google initially proposed it. What has changed since then
that we are considering changing our previous stance here?
On 2015-06-15 9:18 PM, Jeff Muizelaar wrote:
I'm concerned this will discourage websites
Bug 1156135 https://bugzilla.mozilla.org/show_bug.cgi?id=1156135 will
enable Runtime Hardware Testing for Firefox Desktop. Once enabled, we'll
test the rendering capabilities of the current user's hardware prior to
enabling features that depend on that hardware.
A more detailed overview is posted
!!! \o/ !!!
We'll also post the proposed spec on this wiki page:
https://wiki.mozilla.org/CanvasFilters
--Jet
On Mon, Jun 15, 2015 at 10:15 AM, Markus Stange msta...@themasta.com
wrote:
Summary: The filter property on CanvasRenderingContext2D allows authors
to specify a filter that will get
Hi everyone,
You can find below the list of new issues found and filed by the Desktop
Manual QA team last week (Week 24: June 08 - June 12).
Additional details on the team's priorities last week, as well as the plans
for the current week can be found at:
This proposed feature would allow authors to annotate when an element and
its descendants will not (or should not) affect the rest of the page. The
primary intended benefit of such annotations is to allow browsers various
layout and rendering optimizations.
As currently described
Summary: The filter property on CanvasRenderingContext2D allows
authors to specify a filter that will get applied during canvas drawing.
It accepts the same values as the CSS filter property, so CSS filter
shorthand functions, references to SVG filters, and chained combinations
of the two.
Great news! I'm super excited to see this go in!
On Mon, Jun 15, 2015 at 10:15 AM, Markus Stange msta...@themasta.com
wrote:
Summary: The filter property on CanvasRenderingContext2D allows authors
to specify a filter that will get applied during canvas drawing. It accepts
the same values as
On Tue, Jun 16, 2015 at 3:15 AM, Markus Stange msta...@themasta.com wrote:
Summary: The filter property on CanvasRenderingContext2D allows authors
to specify a filter that will get applied during canvas drawing. It accepts
the same values as the CSS filter property, so CSS filter shorthand
Summary:
The WEBGL_debug_renderer_info extension allows for querying which driver
(and commonly GPU) a WebGL context is running on. Specifically, it allows
querying the RENDERER and VENDOR strings of the underlying OpenGL driver.
By default, RENDERER and VENDOR queries in WebGL yield safe but
Markus, Tobias, and Tantek will update the wiki page with our proposed
normative text.
Our key use case here is Shumway, where graphics filter implementations in
JS code have not (yet) been able to offer acceptable performance
characteristics in Canvas2D. We've proven that it's polyfillable in
On Tue, Jun 16, 2015 at 11:05 AM, Xidorn Quan quanxunz...@gmail.com wrote:
On Tue, Jun 16, 2015 at 3:15 AM, Markus Stange msta...@themasta.com
wrote:
Summary: The filter property on CanvasRenderingContext2D allows authors
to specify a filter that will get applied during canvas drawing. It
On Tue, Jun 16, 2015 at 9:23 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Tue, Jun 16, 2015 at 11:05 AM, Xidorn Quan quanxunz...@gmail.com
wrote:
On Tue, Jun 16, 2015 at 3:15 AM, Markus Stange msta...@themasta.com
wrote:
Summary: The filter property on CanvasRenderingContext2D
On 6/15/15 4:16 PM, Jeff Gilbert wrote:
Web Developer Use-Cases:
* Sites can collate and cross-reference drivers and hardware when tracking
issues both user-reported and auto-detected, which both helps sites
identify problematic hardware, and helps browsers fix these issues in turn.
YouTube
On Tue, Jun 16, 2015 at 11:23 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
I think we're not quite there yet, but we're very close. There are two
things I want before we ship:
-- Get normative spec text up somewhere.
-- Get a signal from some other browser vendor that they're OK with
On 2015-06-15 8:15 PM, Robert O'Callahan wrote:
On Tue, Jun 16, 2015 at 11:23 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
I think we're not quite there yet, but we're very close. There are two
things I want before we ship:
-- Get normative spec text up somewhere.
-- Get a signal from
17 matches
Mail list logo
