public-svg-issues@w3.org from August 2016 by author

Amelia Bellamy-Royds via GitHub

• [svgwg] Pull Request: Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• Re: [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs (Friday, 26 August)
• [svgwg] Triage all issues from Tracker (Friday, 26 August)
• [svgwg] Issue: Triage all issues from Tracker marked as Tools (Friday, 26 August)
• [svgwg] Issue: Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts marked as SVG Core (Friday, 26 August)
• Re: [svgwg] x/y/width/height attributes on HTML elements (Thursday, 25 August)
• Re: [svgwg] Support SVG 1.1 baseline value for baseline-shift (Thursday, 25 August)
• Closed: [svgwg] Use "HTML" instead of "HTML5" (Thursday, 25 August)
• Closed: [svgwg] x/y/width/height attributes on HTML elements (Thursday, 25 August)
• Re: [svgwg] Use "HTML" instead of "HTML5" (Thursday, 25 August)
• [svgwg] Issue: Use "HTML" instead of "HTML5" marked as Entire spec (Thursday, 25 August)
• Re: [svgwg] x/y/width/height attributes on HTML elements (Thursday, 25 August)
• Re: [svgwg] Consider rewriting 'references to external resources' processing mode feature (Thursday, 25 August)
• Re: [svgwg] Correct syntax for viewBox to allow comma-separated numbers (Thursday, 25 August)
• [svgwg] Correct syntax for viewBox to allow comma-separated numbers (Wednesday, 24 August)
• [svgwg] Issue: Correct syntax for viewBox to allow comma-separated numbers marked as SVG Core (Wednesday, 24 August)
• Re: [svgwg] Marked-up text from other namespaces in <title> and <desc> (Wednesday, 24 August)
• Closed: [svgwg] Marked-up text from other namespaces in <title> and <desc> (Wednesday, 24 August)
• Closed: [svgwg] Define how object-fit and object-position interact with preserveAspectRatio (Wednesday, 24 August)
• Closed: [svgwg] SVG Image size conflicts with size property and CSS style (Wednesday, 24 August)
• Closed: [svgwg] Do min/max-width/height properties constrain SVG geometry? (Wednesday, 24 August)
• Re: [svgwg] Do min/max-width/height properties constrain SVG geometry? (Wednesday, 24 August)
• Re: [svgwg] Should bounding box of svg, image, foreignObject, etc include overflow content? (Wednesday, 24 August)
• Re: [svgwg] Define how object-fit and object-position interact with preserveAspectRatio (Tuesday, 23 August)
• Re: [svgwg] Should bounding box of svg, image, foreignObject, etc include overflow content? (Tuesday, 23 August)
• [svgwg] Should bounding box of svg, image, foreignObject, etc include overflow content? (Tuesday, 23 August)
• [svgwg] Issue: Should bounding box of svg, image, foreignObject, etc include overflow content? marked as Needs WG input (Tuesday, 23 August)
• Re: [svgwg] Define how object-fit and object-position interact with preserveAspectRatio (Tuesday, 23 August)
• Re: [svgwg] Cut down number of categories (Monday, 22 August)
• Re: [svgwg] Marked-up text from other namespaces in <title> and <desc> (Saturday, 20 August)
• [svgwg] Issue: Marked-up text from other namespaces in <title> and <desc> marked as SVG Core (Saturday, 20 August)
• Re: [svgwg] Require HTML 5 parser to correctly parse embedded HTML elements (Saturday, 20 August)
• Re: [svgwg] Require HTML 5 parser to correctly parse embedded HTML elements (Saturday, 20 August)
• Re: [svgwg] Require HTML 5 parser to correctly parse embedded HTML elements (Saturday, 20 August)
• [svgwg] Issue: Require HTML 5 parser to correctly parse embedded HTML elements marked as SVG Core (Friday, 19 August)
• [svgwg] Require HTML 5 parser to correctly parse embedded HTML elements (Friday, 19 August)
• [svgwg] Issue: Define how object-fit and object-position interact with preserveAspectRatio marked as Needs WG input (Friday, 19 August)
• [svgwg] Define how object-fit and object-position interact with preserveAspectRatio (Friday, 19 August)
• [svgwg] Do min/max-width/height properties constrain SVG geometry? (Friday, 19 August)
• [svgwg] Issue: Do min/max-width/height properties constrain SVG geometry? marked as Geometry Properties chapter (Friday, 19 August)
• Re: [svgwg] SVG Image size conflicts with size property and CSS style (Friday, 19 August)
• Re: [svgwg] SVG Image size conflicts with size property and CSS style (Friday, 19 August)
• [svgwg] Issue: SVG Image size conflicts with size property and CSS style marked as Geometry Properties chapter (Friday, 19 August)
• [svgwg] Issue: Define a style switch to allow one-dimensional shapes to render strokes, markers, etc. marked as Future wish list (Thursday, 18 August)
• [svgwg] Define a style switch to allow one-dimensional shapes to render strokes, markers, etc. (Thursday, 18 August)
• Re: [svgwg] Remove support for "rev" attribute on <a> element (Thursday, 18 August)
• Closed: [svgwg] Should some SVG 2 list type syntax definitions include a trailing comma? (Thursday, 18 August)
• Re: [svgwg] Should some SVG 2 list type syntax definitions include a trailing comma? (Thursday, 18 August)
• Closed: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Friday, 12 August)
• [svgwg] Define equivalent paths for degenerate shapes (Friday, 12 August)
• [svgwg] Issue: Define equivalent paths for degenerate shapes marked as SVG Paths (Friday, 12 August)
• Re: [svgwg] Should some SVG 2 list type syntax definitions include a trailing comma? (Wednesday, 10 August)
• Re: [svgwg] Adjust stroke/fill to be compatible with proposed Fill & Stroke spec (Sunday, 7 August)
• [svgwg] Issue: Adjust stroke/fill to be compatible with proposed Fill & Stroke spec marked as Needs editing (Sunday, 7 August)
• Re: [svgwg] Attributes and properties that allow <length> value should also allow <number> and <percentage> (Sunday, 7 August)
• [svgwg] Issue: Attributes and properties that allow <length> value should also allow <number> and <percentage> marked as Paint Servers chapter (Sunday, 7 August)
• [svgwg] Issue: image-rendering property should apply to <image>, not shapes marked as SVG Core (Sunday, 7 August)
• Re: [svgwg] Tidy up attributes appendix (Sunday, 7 August)
• [svgwg] Issue: Mark "width" and "height" attributes on <image> as animatable marked as SVG Core (Sunday, 7 August)
• Re: [svgwg] "paint-order" property should apply to the same elements as "fill" and "stroke" properties (Sunday, 7 August)
• Re: [svgwg] Consider removal SVGViewElement and its interface (Sunday, 7 August)
• [svgwg] Issue: "paint-order" property should apply to the same elements as "fill" and "stroke" properties marked as SVG Core (Sunday, 7 August)
• [svgwg] Issue: Consider removal SVGViewElement and its interface marked as SVG Core (Sunday, 7 August)
• Re: [svgwg] Remove support for "rev" attribute on <a> element (Sunday, 7 August)
• [svgwg] Issue: Remove support for "rev" attribute on <a> element marked as Needs WG input (Sunday, 7 August)
• Re: [svgwg] stroke/fill should be shorthand properties (Thursday, 4 August)
• Re: [svgwg] stroke/fill should be shorthand properties (Wednesday, 3 August)
• Re: [svgwg] Add <use> to the graphics elements category (Wednesday, 3 August)
• Re: [svgwg] Add <use> to the graphics elements category (Tuesday, 2 August)
• Re: [svgwg] Add <use> to the graphics elements category (Tuesday, 2 August)
• [svgwg] Issue: Add <use> to the graphics elements category marked as SVG Core (Tuesday, 2 August)
• Re: [svgwg] We should define the behavior of ‘use’ in terms of Web Components (Tuesday, 2 August)
• Re: [svgwg] Consider if XSL references can be removed (Tuesday, 2 August)
• Re: [svgwg] Update getNumberOfChars() definition (Monday, 1 August)
• [svgwg] Provide text-to-path-data conversion method (Monday, 1 August)
• [svgwg] Issue: Provide text-to-path-data conversion method marked as Future wish list (Monday, 1 August)

Cameron McCormack via GitHub

• [svgwg] Issue: rootElement IDL attribute type should allow null marked as Document structure chapter (Friday, 12 August)
• [svgwg] rootElement IDL attribute type should allow null (Friday, 12 August)

Doug Schepers via GitHub

• Re: [svgwg] We should define the behavior of ‘use’ in terms of Web Components (Tuesday, 2 August)
• Re: [svgwg] We should define the behavior of ‘use’ in terms of Web Components (Tuesday, 2 August)
• Re: [svgwg] Consider if XSL references can be removed (Tuesday, 2 August)
• [svgwg] Consider if XSL references can be removed (Tuesday, 2 August)

fantasai via GitHub

• [svgwg] stroke/fill should be shorthand properties (Wednesday, 3 August)

Fredrik Söderqvist via GitHub

• Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• Re: [svgwg] Require HTML 5 parser to correctly parse embedded HTML elements (Friday, 19 August)

Jarek Foksa via GitHub

• [svgwg] Mark "paint-order" property as inheritable in the property index (Monday, 8 August)
• Re: [svgwg] Tidy up attributes appendix (Monday, 8 August)
• Re: [svgwg] Consider removal SVGViewElement and its interface (Monday, 8 August)
• Re: [svgwg] Tidy up attributes appendix (Sunday, 7 August)
• Re: [svgwg] Attributes and properties that allow <length> value should also allow <number> and <percentage> (Sunday, 7 August)
• Re: [svgwg] Add <use> to the graphics elements category (Wednesday, 3 August)
• Re: [svgwg] Add <use> to the graphics elements category (Tuesday, 2 August)
• [svgwg] Add <use> to the graphics elements category (Tuesday, 2 August)
• [svgwg] "paint-order" property should apply to the same elements as "fill" and "stroke" properties (Tuesday, 2 August)
• [svgwg] image-rendering property should apply to <image>, not shapes (Monday, 1 August)
• [svgwg] Mark "width" and "height" attributes on <image> as animatable (Monday, 1 August)
• [svgwg] Remove support for "rev" attribute on <a> element (Monday, 1 August)
• Closed: [svgwg] Geometry properties should allow <number> value (Monday, 1 August)
• [svgwg] Geometry properties should allow <number> value (Monday, 1 August)
• [svgwg] Attributes that allow <length> value should also allow <number> and <percentage> (Monday, 1 August)

Nikos Andronikos via GitHub

• Re: [svgwg] Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts (Friday, 26 August)
• [svgwg] Support SVG 1.1 baseline value for baseline-shift (Thursday, 25 August)
• [svgwg] Issue: Support SVG 1.1 baseline value for baseline-shift marked as Needs WG input (Thursday, 25 August)
• [svgwg] Consider rewriting 'references to external resources' processing mode feature (Thursday, 25 August)
• [svgwg] Issue: Consider rewriting 'references to external resources' processing mode feature marked as Needs editing (Thursday, 25 August)
• Closed: [svgwg] Correct syntax for viewBox to allow comma-separated numbers (Thursday, 25 August)
• [svgwg] Issue: Multilingual titles and ARIA fallbacks don't work well together marked as DoC_deferred (Wednesday, 24 August)
• [svgwg] Issue: What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? marked as DoC_deferred (Wednesday, 24 August)
• [svgwg] Issue: Check whether behaviour of new CSS3 units needs clarification in SVG context marked as DoC_deferred (Wednesday, 24 August)
• Re: [svgwg] Do min/max-width/height properties constrain SVG geometry? (Wednesday, 24 August)
• Re: [svgwg] Should bounding box of svg, image, foreignObject, etc include overflow content? (Tuesday, 23 August)
• Re: [svgwg] SVG Image size conflicts with size property and CSS style (Tuesday, 23 August)
• Re: [svgwg] Add <use> to the graphics elements category (Monday, 22 August)
• Closed: [svgwg] image-rendering property should apply to <image>, not shapes (Monday, 22 August)
• [svgwg] Issue: Cut down number of categories marked as Entire spec (Monday, 22 August)
• [svgwg] Cut down number of categories (Monday, 22 August)
• Closed: [svgwg] Remove support for "rev" attribute on <a> element (Friday, 19 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Wednesday, 17 August)
• Closed: [svgwg] rootElement IDL attribute type should allow null (Friday, 12 August)
• Closed: [svgwg] Adjust stroke/fill to be compatible with proposed Fill & Stroke spec (Thursday, 11 August)
• Closed: [svgwg] Mark "paint-order" property as inheritable in the property index (Wednesday, 10 August)
• [svgwg] Issue: Mark "paint-order" property as inheritable in the property index marked as DoC_accepted (Wednesday, 10 August)
• [svgwg] Issue: Should some SVG 2 list type syntax definitions include a trailing comma? marked as SVG Core (Wednesday, 10 August)
• [svgwg] Should some SVG 2 list type syntax definitions include a trailing comma? (Wednesday, 10 August)
• [svgwg] Issue: SVG2 Implementation note: figure 6.3.1 not Formatting/rendering marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: SVGSVGElement referenceElement arguments should be nullable marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: SVGDiscardeElement in IDL index links to SVGDescElement marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: css-transforms-2 may clash with SVG's rotate, scale, and translate attributes marked as DoC_rejected (Monday, 8 August)
• [svgwg] Issue: SVGElement.style is defined by CSSOM marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Remove SVGZoomEvent? marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Specify if `getComputedTextLength()` should return a float or an integer marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: How should degenerate closed paths render in SVG ? marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: should UA style sheet have a rule for visited link color? marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Move path interrogation functions to SVGGeometryElement marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Remove any mention of "outline of canvas" marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Value for SVGURIReference.href.animVal when 'xlink:href' is specified (but not 'href') marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Fix the “the the” typos marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: lengthAdjust="spacingAndGlyphs" is a BAD idea marked as DoC_rejected (Monday, 8 August)
• [svgwg] Issue: Shorter equivalent path for the <circle> element marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: SVG element names should not mix camelCase and lowercase notations marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: window.SVGDocument alias is probably not needed for web compat marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Two questions about the `<a>` element marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Does conditional processing mute sound playback? marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: Request for clarification on complex text shaping marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Initial value for the 'rx' and 'ry' properties marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: Result for a value of zero for pathLength is undefined marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Define purpose of other namespaced markup in <title> and <desc> marked as DoC_rejected (Monday, 8 August)
• [svgwg] Issue: Clean up language re <title>/<desc> and tooltips marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: Clarify whether 'filter' attribute is valid for <tspan> elements marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: How should text following <textPath> be positioned? marked as DoC_positiveResponse (Monday, 8 August)
• [svgwg] Issue: Shouldn't gradientTransform precede object bounding box to user space conversion? marked as DoC_noResponse (Monday, 8 August)
• [svgwg] Issue: Limit pattern & gradient attributes that are inheritable using href marked as DoC_accepted (Monday, 8 August)
• [svgwg] Issue: Define how meshes are rendered when children of shapes marked as DoC_noResponse (Monday, 8 August)
• Re: [svgwg] Consider removal SVGViewElement and its interface (Monday, 8 August)
• Re: [svgwg] "paint-order" property should apply to the same elements as "fill" and "stroke" properties (Monday, 8 August)
• Closed: [svgwg] "paint-order" property should apply to the same elements as "fill" and "stroke" properties (Monday, 8 August)
• [svgwg] Issue: Unit of numbers in path data marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Clarify what is the size of a use element if width and height are not specified marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Simplify <image> element content model marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Shorter equivalent path for the <rect> element marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: Marker section seems to be missing some changes marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: <style> should be allowed everywhere where <script> is allowed marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: <script> and <style> content model should allow only character data. marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Remove paint server elements from the content model of <solidcolor>, <linearGradient>, <radialGradient> and <mesh> marked as DoC_noResponse (Sunday, 7 August)
• [svgwg] Issue: Remove <image>, <use>, <iframe>, <video>, <audio>, <foreignObject> from the content model of <use> element marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: Deprecate <cursor> element marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Restore SVGSVGElement.prototype.getElementById marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: Use a single-case name for meshGradient marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: Define what element is returned by SVGSVGElement.getElementById when id duplicated marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Incorrect syntax for <tspan>´s attributes marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Define interaction of markerUnits="strokeWidth" and non-scaling-stroke marked as DoC_accepted (Sunday, 7 August)
• [svgwg] Issue: Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes marked as DoC_positiveResponse (Sunday, 7 August)
• [svgwg] Issue: Update getNumberOfChars() definition marked as DoC_noResponse (Sunday, 7 August)
• [svgwg] Issue: Allow transforms on textPath marked as DoC_positiveResponse (Sunday, 7 August)
• Re: [svgwg] Update getNumberOfChars() definition (Monday, 1 August)
• Closed: [svgwg] Update getNumberOfChars() definition (Monday, 1 August)
• Re: [svgwg] Update getNumberOfChars() definition (Monday, 1 August)

Paul LeBeau via GitHub

• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• [svgwg] Pull Request: Add text-transform property to the list of required CSS properties (Saturday, 27 August)
• Re: [svgwg] Marked-up text from other namespaces in <title> and <desc> (Wednesday, 24 August)
• Re: [svgwg] Marked-up text from other namespaces in <title> and <desc> (Saturday, 20 August)
• [svgwg] Marked-up text from other namespaces in <title> and <desc> (Saturday, 20 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Thursday, 18 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Wednesday, 17 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Consider removal SVGViewElement and its interface (Monday, 8 August)

shanmuga-m via GitHub

• [svgwg] SVG Image size conflicts with size property and CSS style (Friday, 19 August)
• Re: [svgwg] Consider removal SVGViewElement and its interface (Monday, 8 August)
• [svgwg] Consider removal SVGViewElement and its interface (Thursday, 4 August)

Simon Pieters via GitHub

• Re: [svgwg] x/y/width/height attributes on HTML elements (Thursday, 25 August)
• [svgwg] Use "HTML" instead of "HTML5" (Thursday, 25 August)
• [svgwg] x/y/width/height attributes on HTML elements (Thursday, 25 August)
• [svgwg] Issue: x/y/width/height attributes on HTML elements marked as Embedded Content chapter (Thursday, 25 August)

Tab Atkins Jr. via GitHub

• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Define equivalent paths for degenerate shapes (Monday, 15 August)
• Re: [svgwg] Should some SVG 2 list type syntax definitions include a trailing comma? (Wednesday, 10 August)
• Re: [svgwg] Remove support for "rev" attribute on <a> element (Monday, 8 August)

Tavmjong via GitHub

• Re: [svgwg] Add text-transform property to the list of required CSS properties (Sunday, 28 August)

Last message date: Sunday, 28 August 2016 10:25:52 UTC