On Mon, Jan 19, 2015 at 12:29 PM, Simon Thum simon.t...@gmx.de wrote:
On 01/19/2015 05:28 AM, Nikos Andronikos wrote:
I'm not quite following what you've written here. I think you're saying
you would like the initial values of color-interpolation to be changed
to linearRGB but I'm not sure how
On Wed, Mar 25, 2015 at 5:03 AM, Dirk Schulze dschu...@adobe.com wrote:
On Mar 25, 2015, at 9:47 AM, Simon Pieters sim...@opera.com wrote:
OK, thanks. The current situation is inconsistent, which seems bad for Web
developers.
I admit that I can see confusion here.
I agree that we should keep
On Thu, Apr 16, 2015 at 12:33 AM, Erik Dahlström e...@opera.com wrote:
Hi,
forwarding on behalf of Eric Willigers, who found some inconsistencies in
how the starting point and direction works in the motion path draft compared
to svg2. In the definition of the motion-path[1] property the
On Wed, Jun 17, 2015 at 11:42 AM, Bob Hopgood frahopg...@gmail.com wrote:
It is unclear to me that CSS has any idea what it is letting itself in for
if it decides to style or animate the d attribute of the SVG path
I have a very low definition outline of Australia which is a 50,000 bytes d
On Mon, Jun 22, 2015 at 12:10 AM, Shane Stephens sh...@google.com wrote:
On Wed, Jun 17, 2015 at 6:53 AM Amelia Bellamy-Royds
amelia.bellamy.ro...@gmail.com wrote:
Although the SVG WG agreed to neuter `attributeType` for SMIL animations
(so that the animation always applies to a style property
EXPLICITLY PINGING DIRK
On Wed, Jul 1, 2015 at 2:51 PM, Philip Jägenstedt phil...@opera.com wrote:
On Thu, May 28, 2015 at 12:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, May 27, 2015 at 6:21 AM, Philip Jägenstedt phil...@opera.com wrote:
http://dev.w3.org/fxtf/geometry/ says
On Tue, May 19, 2015 at 11:18 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/10/15 10:42 PM, Tab Atkins Jr. wrote:
On Wed, Feb 11, 2015 at 1:54 PM, Boris Zbarsky bzbar...@mit.edu wrote:
2) The canvas background, which comes from either the root element or
the
body. This should possibly
On Fri, Aug 21, 2015 at 3:22 PM, Shane Stephens sh...@google.com wrote:
Hi list,
When interpolating between rotations with different axis alignment, we
always fall back on matrix decomposition.
However, if one of the angles is 0, then the resulting behavior is that the
rotation axis snaps
On Thu, Aug 13, 2015 at 2:55 PM, Rik Cabanier caban...@gmail.com wrote:
On Thu, Aug 13, 2015 at 2:46 PM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 2:29 PM, Rik Cabanier caban...@gmail.com wrote:
On Thu, Aug 13, 2015 at 2:20 PM, Rik Cabanier caban...@gmail.com
wrote
On Thu, Aug 13, 2015 at 2:29 PM, Rik Cabanier caban...@gmail.com wrote:
On Thu, Aug 13, 2015 at 2:20 PM, Rik Cabanier caban...@gmail.com wrote:
You execute an extra pass where you render everything upto your nearest
sibling, but you ignore any opacity, filters and compositiing.
Then you use
In our recent Intent To Implement for backdrop-filter, Enne brought up
a case that is seemingly circular:
body
AAA
div style=opacity: .5
BBB
div style=backdrop-filter: blur(5px)foo/div
/div
/body
What does BBB look like blur filter? Is it half-opaque, as if you'd
already done all
On Mon, Oct 12, 2015 at 1:16 PM, Jonathan Wilkes wrote:
> Hi web animators,
> Two questions:
> 1) I have played around with the element.animate method in Chrome, with an
> image "i":
> var my_animation = i.animate([ { width: "10px" }, { width: "100px" } ],
> 1000);
>
> When
On Wed, Oct 14, 2015 at 9:10 PM, Simon Fraser wrote:
> I would like the clip-path: property[1] to actually support bezier paths (as
> a naive interpretation of the property name would have you expect).
>
> The syntax would be a path function with an SVG-style path as a string, for
>
On Mon, Jul 6, 2015 at 8:31 PM, Shane Stephens sh...@google.com wrote:
Hi list,
Here's how we currently define quaternion SLERPing during interpolation:
http://dev.w3.org/csswg/css-transforms/#interpolation-of-decomposed-3d-matrix-values
When quatA = [0, 1, 0, 0] and quatB = [0, -1, 0, 0],
On Mon, Sep 14, 2015 at 5:04 PM, Robert O'Callahan wrote:
> A better idea might be to provide a way to pass in resources as parameters,
> including from a CSS style sheet. This might even perform better if you have
> a lot of SVG images using the same resources. Sketch:
>
On Mon, Sep 14, 2015 at 5:42 PM, Robert O'Callahan <rob...@ocallahan.org> wrote:
> On Tue, Sep 15, 2015 at 12:26 PM, Tab Atkins Jr. <jackalm...@gmail.com>
> wrote:
>> We've switched url() over to a function, so we can add arguments to it.
>
> Doesn't
On Mon, Sep 28, 2015 at 12:27 PM, Erik Dahlström wrote:
> Hi,
> I was reviewing the 'transform-box' section in the css transforms spec,
> https://drafts.csswg.org/css-transforms/#transform-box.
>
> The initial value of 'transform-box' is 'border-box', which is fine.
> However,
On Thu, Nov 5, 2015 at 6:16 AM, L. David Baron wrote:
> https://drafts.fxtf.org/css-masking-1/#the-mask-image defines a
> property that can use the url() function to link to either an SVG
> mask element or to an image.
>
> I don't see where it specifies how to tell which one of
On Tue, Dec 8, 2015 at 3:30 PM, Tab Atkins Jr. <jackalm...@gmail.com> wrote:
> On Thu, Nov 5, 2015 at 6:16 AM, L. David Baron <dba...@dbaron.org> wrote:
>> https://drafts.fxtf.org/css-masking-1/#the-mask-image defines a
>> property that can use the url() function to li
On Mon, Nov 23, 2015 at 10:30 PM, Rachel Nabors wrote:
> I see the need. I would argue that this would be more of an "exit-transition"
> than exit-animation, though: fires once and describes how values should
> change (upon application and in accordance with :detached)
On Wed, Feb 24, 2016 at 3:58 PM, Dean Jackson <d...@apple.com> wrote:
>> On 25 Feb 2016, at 10:56 AM, Tab Atkins Jr. <jackalm...@gmail.com> wrote:
>> On Wed, Feb 24, 2016 at 1:41 PM, Dean Jackson <d...@apple.com> wrote:
>>> On 25 Feb 2016, at 8:29 AM, Robert
On Wed, Feb 24, 2016 at 1:41 PM, Dean Jackson wrote:
> On 25 Feb 2016, at 8:29 AM, Robert O'Callahan wrote:
>> On Thu, Feb 25, 2016 at 9:58 AM, Dean Jackson wrote:
>>> Although it's not just that it is a standalone property. It would be nice
After some discussion with Shane, we have a new proposal:
1. Drop fill-rule from path() and polygon(). This keeps all the shape
functions as just specifying the path geometry, so they're usable
everywhere without confusion.
2. In properties that need to know the shape's fill, just accompany
23 matches
Mail list logo