public-fxtf-archive@w3.org from May 2017 by subject

[fxtf-drafts] [compositing-1] Lighter compositing operator as a blend mode

[fxtf-drafts] [css-masking-1] Clarify how mask-mode & mask-composite behave with layered mask images

[fxtf-drafts] [css-masking] Change percentage value of clip-path

[fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping

[fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed

[fxtf-drafts] [css-masking] Support <g> element is clipping paths

[fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow()

[fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default

[fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation

[fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend

[fxtf-drafts] [filter-effects] For filter() image function, do you use intrinsic or extrinsic image dimensions

[fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?

[fxtf-drafts] [filter-effects] Why can't opacity() filter function every increase opacity

[fxtf-drafts] [filter-effects][compositing] What is "no-composite" blending?

[fxtf-drafts] [geometry] " The IDL in this specification is currently in ..."

[fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect

[fxtf-drafts] [geometry] "Rectangles have the following properties:"

[fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D

[fxtf-drafts] [geometry] Add a Historical section discussing old interfaces

[fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string)

[fxtf-drafts] [geometry] Define serialize/deserialize steps

[fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser

[fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations

[fxtf-drafts] [geometry] DOMMatrix stringifier in workers

[fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax

[fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases

[fxtf-drafts] [geometry] Limit DOMMatrix's special stringifier to Window

[fxtf-drafts] [geometry] Parse as CSS 'transform' instead of SVG transform=""

[fxtf-drafts] [geometry] Remove inline issue about experimental API shape

[fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations

[fxtf-drafts] [geometry] Structured serialization should branch on is 2D

[fxtf-drafts] [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity

[fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout

[fxtf-drafts] [geometry] Update the Changes section

[fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists

[fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO…

[fxtf-drafts] [motion] Define 'sides' value for ray size.

[fxtf-drafts] [motion] none value considerations

[fxtf-drafts] [paint] "outside stroke" and "group outline"

[fxtf-drafts] Allow nesting filters instead of using 'in', 'in2' and 'result' attributes

[fxtf-drafts] offset-rotate syntax is resolved

[fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces

[fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations

[fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject]

[fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps

[fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix

[fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window

[fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform=""

[fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity

[fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout

[fxtf-drafts] Pull Request: [geometry] Update the Changes section

[fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix

[fxtf-drafts] Pull Request: [motion] computed distance now supports calc

[fxtf-drafts] Pull Request: [motion] Create containing blocks

[fxtf-drafts] Pull Request: [motion] Define 'sides' value for ray size.

[fxtf-drafts] Pull Request: [motion] Interaction of offset-position and shapes

[fxtf-drafts] Pull Request: [motion] Link to Motion Path's size definition

[fxtf-drafts] Pull Request: [motion] Remove Overview.html

[fxtf-drafts] Pull Request: [motion] Specify offset-rotate 0deg in examples

[fxtf-drafts] Pull Request: [motion] Supply size in ray examples

[fxtf-drafts] Pull Request: offset-rotate syntax is resolved

Closed: [fxtf-drafts] [css-masking] Change percentage value of clip-path

Closed: [fxtf-drafts] [geometry] " The IDL in this specification is currently in ..."

Closed: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D

Closed: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix

Closed: [fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string)

Closed: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser

Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations

Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers

Closed: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax

Closed: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases

Closed: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D

Closed: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists

Closed: [fxtf-drafts] [motion] defining "computed distance" (aka "used distance")

Closed: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation

Closed: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?

Closed: [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions

Last message date: Tuesday, 30 May 2017 12:58:10 UTC