Friday, 30 November 2018
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
Thursday, 29 November 2018
- Re: [svgwg] Marker element percentages are missing reference values (#64)
- Re: [svgwg] patternTransform browser implementations do not match spec (#293)
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render? (#580)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
Wednesday, 28 November 2018
- Re: [svgwg] Rewrite all element descriptions to use normative language (#111)
- Re: [svgwg] Reference W3C Web Animations (#22)
- Re: [svgwg] Rewrite all element descriptions to use normative language (#111)
- Re: [svgwg] Rewrite all element descriptions to use normative language (#111)
Tuesday, 27 November 2018
- Re: [svgwg] Reference W3C Web Animations (#22)
- Re: [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs (#195)
- Closed: [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs (#195)
- Re: [svgwg] Support SVG 1.1 baseline value for baseline-shift (#246)
- Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (#249)
- Closed: [svgwg] Rotating text (#260)
- Re: [svgwg] Rotating text (#260)
- Closed: [svgwg] UTF-16 code points for addressable characters (#259)
- Re: [svgwg] UTF-16 code points for addressable characters (#259)
- Closed: [svgwg] Keep xlink:href in examples linked to in spec. (#105)
- Closed: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context (#207)
- Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context (#207)
- Re: [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs (#195)
- Re: [svgwg] Update default role mapping table to match latest SVG-AAM (#176)
- Re: [svgwg] definition of character (#263)
- Closed: [svgwg] definition of character (#263)
- Re: [svgwg] 'typographic character' should mention grapheme clusters (#262)
- Closed: [svgwg] 'typographic character' should mention grapheme clusters (#262)
- Re: [svgwg] Rewrite all element descriptions to use normative language (#111)
- Re: [svgwg] Figure out where the list of aria-properties comes from, & sort them in logical/alphabetical order (#117)
- Re: [svgwg] Reference W3C Web Animations (#22)
- Closed: [svgwg] Reference W3C Web Animations (#22)
- Re: [svgwg] Marker element percentages are missing reference values (#64)
- Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (#335)
- Re: [svgwg] [Basic Data Types and Interfaces chapter] Should specifiy the presentation attribute of a SVG unitless length (#319)
- Closed: [svgwg] [Basic Data Types and Interfaces chapter] Should specifiy the presentation attribute of a SVG unitless length (#319)
- Re: [svgwg] getScreenCTM (and friends?) results for elements that are not in the rendering tree? (#307)
- Re: [svgwg] Support for 3D ancestor transforms in `getScreenCTM()` (#302)
- Re: [svgwg] Support for 3D ancestor transforms in `getScreenCTM()` (#302)
- Re: [svgwg] patternTransform browser implementations do not match spec (#293)
- [svgwg] Issue: The 'direction' property (#287) marked as Needs editing
- Re: [svgwg] Scientific notation has been removed from the path EBNF (#286)
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render? (#580)
- Closed: [svgwg] Merge CR changes into master & update to track changes vs CR (#275)
- Re: [svgwg] SVG 2 has un-used references (#71)
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (#537)
- Re: [svgwg] Defer pointer-events bounding-box? (#573)
Monday, 26 November 2018
- Closed: [svgwg] Place of SVG presentation attributes in the CSS cascade (#596)
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Fixes #596
- Re: [svgwg] Fixes #596 (#598)
- [svgwg] new commits pushed by dirkschulze
- Closed: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics (#456)
- Closed: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images (#322)
- Re: [svgwg] Adapt host coordinate space def of vector-effect to implemented behav… (#585)
- [svgwg] Closed Pull Request: Painting: numeric stroke-width, stroke-dashoffset
- Re: [svgwg] Painting: numeric stroke-width, stroke-dashoffset (#593)
- Re: [svgwg] Update property definitions to use new CSS approach to "animatable" (#555)
- Closed: [svgwg] Update property definitions to use new CSS approach to "animatable" (#555)
- Closed: [svgwg] stroke-width initial value must include units (#529)
- Re: [svgwg] stroke-width initial value must include units (#529)
- Re: [svgwg] Review property value definitions to ensure unitless lengths are correctly included (#534)
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Unify CSS properties, use new animation type attributes, allow number…
Sunday, 25 November 2018
- [svgwg] Merged Pull Request: stop-opacity computed value is clamped
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Pull Request: stop-opacity computed value is clamped
- [svgwg] Pull Request: stop-opacity computed value is clamped
- Re: [svgwg] Replace <opacity-value> with <alpha-value> (#403)
Saturday, 24 November 2018
Friday, 23 November 2018
- Re: [svgwg] Fixes #596 (#598)
- Closed: [svgwg] Add non-attached elements to non-rendered elements (#599)
- [svgwg] Merged Pull Request: Add detached elements to non-rendered elements. #599
- [svgwg] new commits pushed by ewilligers
- [svgwg] Pull Request: Add detached elements to non-rendered elements. #599
- Re: [svgwg] Fixes #596 (#598)
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Clarify possible UA behavior on getTotalLength, getPointAtLength, get…
- Re: [svgwg] Clarify possible UA behavior on getTotalLength, getPointAtLength, get… (#594)
- [svgwg] Add non-attached elements to non-rendered elements (#599)
- [svgwg] Issue: Add non-attached elements to non-rendered elements (#599) marked as Needs editing
- [svgwg] Merged Pull Request: CSS pointer-events on (raster) images does not require scanning pixels
- [svgwg] new commits pushed by dirkschulze
- Re: [svgwg] Clarify possible UA behavior on getTotalLength, getPointAtLength, get… (#594)
- Re: [svgwg] Fixes #596 (#598)
- Re: [svgwg] Fixes #596 (#598)
- Re: [svgwg] Fixes #596 (#598)
- [svgwg] Issue: Place of SVG presentation attributes in the CSS cascade (#596) marked as Needs editing
Thursday, 22 November 2018
- [svgwg] Pull Request: Fixes #596
- Re: [svgwg] Place of SVG presentation attributes in the CSS cascade (#596)
- Re: [svgwg] Place of SVG presentation attributes in the CSS cascade (#596)
- [svgwg] new commits pushed by birtles
Wednesday, 21 November 2018
- Closed: [svgwg] Possible inconsistency with set element and href attribute (#595)
- [svgwg] new commits pushed by birtles
- [svgwg] Merged Pull Request: Fix href in animation
- Re: [svgwg] Fix href in animation (#597)
- [svgwg] Pull Request: Fix href in animation
- [svgwg] Place of SVG presentation attributes in the CSS cascade (#596)
- [svgwg] Possible inconsistency with set element and href attribute
Monday, 19 November 2018
- Re: [svgwg] Mark 4 text properties at risk
- Re: [svgwg] Replace <opacity-value> with <alpha-value>
- [svgwg] Pull Request: Clarify possible UA behavior on getTotalLength, getPointAtLength, get…
- Re: [svgwg] Replace <opacity-value> with <alpha-value>
- [svgwg] Merged Pull Request: isPointInStroke must take vector-effect property into account. #559
- [svgwg] new commits pushed by svgeesus
- [svgwg] new commits pushed by svgeesus
- [svgwg] Merged Pull Request: inline-size has initial value auto
- Re: [svgwg] 'image' element not defined to fire 'load' event when load happens
- Re: [svgwg] Replace <opacity-value> with <alpha-value>
Saturday, 17 November 2018
- Re: [svgwg] Painting: numeric stroke-width, stroke-dashoffset
- [svgwg] Pull Request: Painting: numeric stroke-width, stroke-dashoffset
- [svgwg] Pull Request: Painting: numeric stroke-width, stroke-dashoffset
- Re: [svgwg] Review property value definitions to ensure unitless lengths are correctly included
- Re: [svgwg] Mark 4 text properties at risk
- [svgwg] Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs'
- [svgwg] Issue: Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' marked as SVG2
- Re: [svgwg] Replace <opacity-value> with <alpha-value>
- [svgwg] Issue: Replace <opacity-value> with <alpha-value> marked as SVG2
- [svgwg] Issue: Mark 4 text properties at risk marked as Text chapter
- [svgwg] Mark 4 text properties at risk
Tuesday, 13 November 2018
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] inline-size has initial value auto
- [svgwg] Pull Request: inline-size has initial value auto
- [svgwg] Pull Request: inline-size has initial value auto
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Develop a new standard for describing "layers" in SVG authoring tools
- [svgwg] Issue: Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? marked as Agenda+
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- [svgwg] Issue: SVGGeometry.prototype.isPointInStroke vs. vector-effects marked as Needs tests
- [svgwg] Issue: Update property definitions to use new CSS approach to "animatable" marked as Needs editing
- [svgwg] Issue: 'image' element not defined to fire 'load' event when load happens marked as Agenda+
- Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
Monday, 12 November 2018
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties
- Re: [svgwg] vector-effect host coordinate space is not "screen"
- Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrix2DInit
- Re: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images
- Re: [svgwg] <foreignObject> and <svg:use>
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] Defer text content area
- [svgwg] Issue: Defer text content area marked as Text chapter
- [svgwg] Defer text content area
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Closed: [svgwg] Defer z-index due to lack of implementations
- Re: [svgwg] Defer z-index due to lack of implementations
- Re: [svgwg] Defer z-index due to lack of implementations
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
Sunday, 11 November 2018
- Closed: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] 'stop-color' property resolving with 'inherit' value
- [svgwg] 'stop-color' property resolving with 'inherit' value
- Re: [svgwg] The filter region clipping
- Re: [svgwg] The filter region clipping
- Re: [svgwg] The filter region clipping
- Re: [svgwg] The filter region clipping
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] The filter region clipping
- Closed: [svgwg] The filter region clipping
- Re: [svgwg] The filter region clipping
- Re: [svgwg] The filter region clipping
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- [svgwg] The filter region clipping
- Re: [svgwg] vector-effect host coordinate space is not "screen"
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- [svgwg] Issue: isPointInFill/isPointInStroke and display: none and other specifics marked as Agenda+
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] Unify CSS properties, use new animation type attributes, allow number…
Saturday, 10 November 2018
- Closed: [svgwg] stroke-miterlimit: invalid value behavior?
- Re: [svgwg] stroke-miterlimit: invalid value behavior?
- [svgwg] Pull Request: Unify CSS properties, use new animation type attributes, allow number…
- [svgwg] Pull Request: Adapt host coordinate space def of vector-effect to implemented behav…
- Re: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
Friday, 9 November 2018
- Re: [svgwg] should textPath elements parented to tspans or other textPaths render?
- Re: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images
- [svgwg] Pull Request: Clarify pointer-events with clipping path on bounding-box and remove …
- Re: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images
- Closed: [svgwg] pointer-events: remove requirement to scan pixels on images
- Re: [svgwg] pointer-events: remove requirement to scan pixels on images
- Re: [svgwg] Remove un-implemented `pointer-events` "painted" rules for images
- [svgwg] Issue: Remove un-implemented `pointer-events` "painted" rules for images marked as Agenda+
- [svgwg] Pull Request: isPointInStroke must take vector-effect property into account. #559
- Re: [svgwg] vector-effect host coordinate space is not "screen"
- Re: [svgwg] vector-effect host coordinate space is not "screen"
- Re: [svgwg] vector-effect host coordinate space is not "screen"
- [svgwg] Issue: vector-effect host coordinate space is not "screen" marked as Agenda+
- [svgwg] vector-effect host coordinate space is not "screen"
- Re: [svgwg] pointer-events bounding-box
Thursday, 8 November 2018
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Re: [svgwg] pointer-events: remove requirement to scan pixels on images
- Re: [svgwg] pointer-events: remove requirement to scan pixels on images
- [svgwg] Issue: SVGTransform's setMatrix method should take a DOMMatrixInit marked as Agenda+
- Re: [svgwg] pointer-events bounding-box
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- [svgwg] pointer-events: remove requirement to scan pixels on images
- [svgwg] Issue: pointer-events: remove requirement to scan pixels on images marked as Agenda+
- Re: [svgwg] pointer-events bounding-box
- Re: [svgwg] how should display:contents affect SVG conditional processing attributes?
- [svgwg] Issue: how should display:contents affect SVG conditional processing attributes? marked as Styling chapter
- [svgwg] Issue: should textPath elements parented to tspans or other textPaths render? marked as Needs editing
- Re: [svgwg] Remove at-risk flag from vector-effect values
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- [svgwg] should textPath elements parented to tspans or other textPaths render?
- [svgwg] how should display:contents affect SVG conditional processing attributes?
Wednesday, 7 November 2018
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Re: [svgwg] pointer-events bounding-box
- [svgwg] Drawing vector-effects mentions SVG 1.2T terms
- [svgwg] Issue: Drawing vector-effects mentions SVG 1.2T terms marked as Painting chapter
- [svgwg] Issue: How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties marked as Agenda+
- [svgwg] Issue: Wrong description of percentage units marked as Needs editing
- [svgwg] Pull Request: Use DOMMatrix2DInit as parameters for methods. #326
- [svgwg] Pull Request: Remove at-risk flag from vector-effect values
- [svgwg] Issue: <foreignObject> and <svg:use> marked as Agenda+
Tuesday, 6 November 2018
- [svgwg] new commits pushed by ewilligers
- [svgwg] Merged Pull Request: [interactivity] pointer-events auto
- Closed: [svgwg] pointer-events auto
- [svgwg] Pull Request: [interactivity] pointer-events auto
- Re: [svgwg] 'd' presentation attribute: use path() function
- [svgwg] Pull Request: [interactivity] pointer-events auto
- Closed: [svgwg] typo: Elmenent
- [svgwg] Issue: Proposal for addition of new commands in the Path Data language marked as Proposal
Monday, 5 November 2018
- Re: [svgwg] pointer-events auto
- Re: [svgwg] pointer-events auto
- Re: [svgwg] Add decode() and decoding attribute to SVGImageElement
- Re: [svgwg] 'd' presentation attribute: use path() function
- Re: [svgwg] Define how new sizing keywords are resolved for SVG width and height geometry properties
- Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?
- Re: [svgwg] SVGGeometry.prototype.isPointInStroke vs. vector-effects
- Re: [svgwg] 'd' presentation attribute: use path() function
Sunday, 4 November 2018
- Re: [svgwg] Z-axis
- [svgwg] Issue: pointer-events auto marked as Interactivity chapter
- [svgwg] pointer-events auto
- [svgwg] Issue: pointer-events bounding-box marked as Interactivity chapter
- [svgwg] pointer-events bounding-box
Friday, 2 November 2018
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
Thursday, 1 November 2018
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes.
- Re: [svgwg] Proposal for addition of new commands in the Path Data language