Wednesday, 30 May 2018
Monday, 28 May 2018
- [svgwg] Make URL-resolution compatible with web componants shadow DOM
- [svgwg] Issue: Make URL-resolution compatible with web componants shadow DOM marked as Document structure chapter
Friday, 25 May 2018
Thursday, 24 May 2018
- [svgwg] Merged Pull Request: Export text content element definition
- [svgwg] new commits pushed by dirkschulze
Wednesday, 23 May 2018
Monday, 21 May 2018
- Re: [svgwg] Define "context" for SVG-in-OpenType glyphs
- Closed: [svgwg] Update SVG 2.0 (master) to remove "at-risk" features, preserve in svg-next (Wave 1: Hatch, Mesh, Cursor, Solid color)
- Re: [svgwg] Update SVG 2.0 (master) to remove "at-risk" features, preserve in svg-next (Wave 1: Hatch, Mesh, Cursor, Solid color)
Saturday, 19 May 2018
Friday, 18 May 2018
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Update SVG 2.0 (master) to remove "at-risk" features and make sure they're preserved in svg-next
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Remove solidcolour
- Re: [svgwg] Remove solidcolour
- Re: [svgwg] Remove solidcolour
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Remove defintion of white-space
- Closed: [svgwg] Computed value for white-space incorrect?
- Re: [svgwg] Remove defintion of white-space
- [svgwg] Pull Request: Remove defintion of white-space
- Re: [svgwg] stacking context / rendering order requirements are mostly not Web compatible
- Re: [svgwg] stacking context / rendering order requirements are mostly not Web compatible
- [svgwg] stacking context / rendering order requirements are mostly not Web compatible
Thursday, 17 May 2018
- Re: [svgwg] Define "context" for SVG-in-OpenType glyphs
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Re: [svgwg] Allow setting the SVG context properties when in an HTML <img> tag
- Re: [svgwg] Define "context" for SVG-in-OpenType glyphs
- [svgwg] Issue: context-value UA rules for OpenType are giving unexpected rendering / compat problems marked as SVG in OpenType
- [svgwg] Issue: Define "context" for SVG-in-OpenType glyphs marked as SVG2
- [svgwg] Define "context" for SVG-in-OpenType glyphs
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems
- Closed: [svgwg] Definitions not marked as export
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Update data-export
- [svgwg] SVG...List.removeItem not specified to reserialize to attribute
- [svgwg] Pull Request: Update data-export
- Re: [svgwg] Definitions not marked as export
- Re: [svgwg] Definitions not marked as export
- [svgwg] Definitions not marked as export
Wednesday, 16 May 2018
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Remove unused defs and fix some linking issues
- [svgwg] Pull Request: Remove unused defs and fix some linking issues
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Fix issue with MathML namespace and duplicate ID in changelog
- [svgwg] Pull Request: Fix issue with MathML namespace and duplicate ID in changelog
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Remove SVGCursorElement...
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- [svgwg] isPointInFill/isPointInStroke and display: none and other specifics
- Re: [svgwg] Remove SVGCursorElement...
Tuesday, 15 May 2018
- Re: [svgwg] Remove SVGCursorElement...
- [svgwg] Pull Request: Remove SVGCursorElement...
- Re: [svgwg] Remove solidcolour
- [svgwg] Merged Pull Request: Remove hatch gradients
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Remove mesh gradients
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Remove mesh gradients
- Re: [svgwg] Remove solidcolour
- Re: [svgwg] Remove mesh gradients
- [svgwg] Issue: Clean up assets once all removals/referments from SVG2 are merged marked as SVG2
- [svgwg] Clean up assets once all removals/referments from SVG2 are merged
- Re: [svgwg] Remove mesh gradients
Monday, 14 May 2018
- Re: [svgwg] Marker element percentages are missing reference values
- Re: [svgwg] Remove mesh gradients
- Re: [svgwg] Remove solidcolour
- Re: [svgwg] Remove solidcolour
- Re: [svgwg] Remove SVGCursorElement
- [svgwg] Closed Pull Request: Remove SVGCursorElement
- [svgwg] Pull Request: Remove SVGCursorElement
- Re: [svgwg] Remove mesh gradients
- [svgwg] Pull Request: Remove mesh gradients
- [svgwg] Pull Request: Remove hatch gradients
- [svgwg] Pull Request: Remove solidcolour
- [svgwg] Update SVG 2.0 (master) to remove "at-risk" features and make sure they're preserved in svg-next
- [svgwg] Identify SVG1 elements that are obsolete in SVG2
Friday, 11 May 2018
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Computed value for white-space incorrect?
- [svgwg] Merged Pull Request: Allow paint-order to be a presentational attribute
- Closed: [svgwg] Add a presentation attribute for `paint-order`
- [svgwg] new commits pushed by dstorey
- [svgwg] Computed value for white-space incorrect?
- [svgwg] Pull Request: Update property index
- Closed: [svgwg] Clarify relation of isPointInFill and pointer-events
- [svgwg] Merged Pull Request: Specify algorithm used for isPointInFill() and isPointInStroke(). #416
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Issue: SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString marked as HTML Consistency
- Re: [svgwg] Allow paint-order to be a presentational attribute
- [svgwg] Pull Request: Allow paint-order to be a presentational attribute
- [svgwg] Issue: Synchronize SVGImageElement with HTMLImageElement marked as HTML Consistency
- [svgwg] Issue: Parameters and Switch command to allow parametric SVGs marked as Proposal
- Re: [svgwg] Spec behavior of ::before and ::after within SVG text
- [svgwg] Issue: Spec behavior of ::before and ::after within SVG text marked as Future wish list
- Re: [svgwg] Add more modern event handling examples
- Re: [svgwg] Marker element percentages are missing reference values
- Re: [svgwg] Clarify how user agents should implement vendor-specific extensions
- Closed: [svgwg] Clarify how user agents should implement vendor-specific extensions
- Closed: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- Re: [svgwg] Consider adding decoding and decode to SVGImageElement
- [svgwg] Consider adding decoding and decode to SVGImageElement
Thursday, 10 May 2018
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Closed: [svgwg] SVG Integration: mixed content
- [svgwg] Merged Pull Request: Update http to https to avoid mixed content. Update http anchors while at it
- [svgwg] new commits pushed by dstorey
- Closed: [svgwg] SVG Integration: update "This version" link
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Fixes #356 this version link on Integration spec
- [svgwg] Issue: Do we really need not to reflect additional enum values in SVG 2 marked as Needs tests
- [svgwg] Pull Request: Specify algorithm used for isPointInFill() and isPointInStroke(). #416
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Number syntax: digit-sequence "."
- Re: [svgwg] Number syntax: digit-sequence "."
- [svgwg] Issue: Floating point number format discordance (SVG vs CSS vs browsers) marked as Agenda+
- Re: [svgwg] Number syntax: digit-sequence "."
- Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)
- Re: [svgwg] Number syntax: digit-sequence "."
- Closed: [svgwg] Number syntax: digit-sequence "."
- Re: [svgwg] Number syntax: digit-sequence "."
- Re: [svgwg] Number syntax: digit-sequence "."
- [svgwg] Issue: Number syntax: digit-sequence "." marked as Paths chapter
- [svgwg] Number syntax: digit-sequence "."
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Add myself to editors
Wednesday, 9 May 2018
Tuesday, 8 May 2018
- Re: [svgwg] Add myself to editors
- [svgwg] Pull Request: Add myself to editors
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
- [svgwg] new commits pushed by heycam
Monday, 7 May 2018
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
- Re: [svgwg] Clarify hit testing behavior of <foreignObject>
- Re: [svgwg] Clarify relation of isPointInFill and pointer-events
- Re: [svgwg] Move corresponding[Use]Element members to main SVGElement definition?
- Re: [svgwg] Move corresponding[Use]Element members to main SVGElement definition?
- Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers
- [svgwg] Move corresponding[Use]Element members to main SVGElement definition?
- [svgwg] new commits pushed by heycam
Sunday, 6 May 2018
- Re: [svgwg] Fix broken and missing references
- [svgwg] Merged Pull Request: Fix broken and missing references
- [svgwg] new commits pushed by dstorey
- [svgwg] Pull Request: Fix broken and missing references
- [svgwg] Pull Request: Update http to https to avoid mixed content. Update http anchors while at it
- [svgwg] Pull Request: Fix #356 this version link on Integration spec
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
Saturday, 5 May 2018
- Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec
- Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers
- Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers
- Closed: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers
- [svgwg] Issue: SVGAElement implements two conflicting interfaces marked as HTML Consistency
- [svgwg] Issue: Should support nomodule attribute on script elements marked as HTML Consistency
- [svgwg] Issue: Resolved value for the 'width' and 'height' geometry properties marked as CSS Consistency
- [svgwg] Issue: 'image' element not defined to fire 'load' event when load happens marked as HTML Consistency
- [svgwg] Issue: Update SVGScriptElement and SVGImageElement to use src? marked as HTML Consistency
- [svgwg] Issue: Deprecate type attribute on SVGStyleElement? marked as HTML Consistency
- [svgwg] Issue: Harmonise inline-size with CSS Logical properties marked as CSS Consistency
- [svgwg] Issue: Add decode() and decoding attribute to SVGImageElement marked as HTML Consistency
- [svgwg] Harmonise inline-size with CSS Logical properties
- [svgwg] Merged Pull Request: Update <length> | <percentage> to <length-percentage>
- Closed: [svgwg] Update percentage types to the new convenience notations
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Fixes #405 update description of when visibility applies
- Re: [svgwg] Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- [svgwg] Merged Pull Request: Add GitHub link to Integration and Template
- Closed: [svgwg] Please link to GitHub from the drafts
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Make DOMPointInit argument optional according to WebIDL spec.
- [svgwg] Pull Request: Add GitHub link to Integration and Template
- [svgwg] Issue: Compatibility mid-line rendering attribute to textPath marked as Proposal
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript
- Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec
Friday, 4 May 2018
- Re: [svgwg] Fixes #405 update description of when visibility applies
- Re: [svgwg] Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Allow more properties to be applied on <a> inside <text>
- [svgwg] Pull Request: Update <length> | <percentage> to <length-percentage>
- Re: [svgwg] Update SVG WG Feedback page on w3.org to point to GitHub issues
- [svgwg] Issue: SVG Paths spec vs Paths chapter of SVG2 marked as SVG Paths
- [svgwg] Issue: On the urgent need to add a native 9-slice scaling mode to the SVG standard marked as Proposal
Thursday, 3 May 2018
- [svgwg] Pull Request: Make DOMPointInit argument optional according to WebIDL spec.
- Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
- Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
- Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
- Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
Wednesday, 2 May 2018
- Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit
- Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit
- Closed: [svgwg] Should SVG 2 switch to Bikeshed?
- Re: [svgwg] Should SVG 2 switch to Bikeshed?
- Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit
- Closed: [svgwg] Can we remove presentation attribute / element table from Attribute Index appendix?
- Re: [svgwg] Can we remove presentation attribute / element table from Attribute Index appendix?
- Re: [svgwg] SVG 2 has un-used references
- Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document
- Closed: [svgwg] Implicit and allowed roles for SVG element in a HTML document
- Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit
- Re: [svgwg] SVG and CSS transform
- Closed: [svgwg] SVG and CSS transform
- [svgwg] new commits pushed by dstorey
- Closed: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage
- [svgwg] Merged Pull Request: Fix #402 Use CCS Colour L4 definition for computed value of *-opacity
- Re: [svgwg] Fix #402 Use CCS Colour L4 definition for computed value of *-opacity
- Re: [svgwg] Allow more properties to be applied on <a> inside <text>
- Re: [svgwg] Fix #402 Use CCS Colour L4 definition for computed value of *-opacity
- [svgwg] Pull Request: Fix #402 Use CCS Colour L4 definition for computed value of *-opacity
- Closed: [svgwg] Replace <opacity-value> with <alpha-value>
- [svgwg] Merged Pull Request: Fix #403 update opacity-value to alpha-value
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Fix #403 update opacity-value to alpha-value
- [svgwg] Pull Request: Fix #403 update opacity-value to alpha-value
- [svgwg] Pull Request: Fixes #405 update description of when visibility applies
- Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2
Tuesday, 1 May 2018
- Re: [svgwg] Fix lint/build issues
- [svgwg] new commits pushed by AmeliaBR
- [svgwg] Merged Pull Request: Fix lint/build issues
- Re: [svgwg] Fix lint/build issues
- [svgwg] Pull Request: Fix lint/build issues
- Closed: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Use DOMPointInit argument for getCharNumAtPosition. #389
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Update spec references for HTML, DOM and CSSOM
- [svgwg] Pull Request: Update spec references for HTML, DOM and CSSOM
- [svgwg] new commits pushed by dstorey
- [svgwg] Merged Pull Request: Add DocumentAndElementEventHandlers
- Closed: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin?
- Closed: [svgwg] Use <dfn> for definitions
- [svgwg] Merged Pull Request: Add or update dfns for definitions
- [svgwg] new commits pushed by dstorey
- Re: [svgwg] Use DOMPointInit argument for getCharNumAtPosition. #389
- [svgwg] Issue: Clarify hit testing behavior of <foreignObject> marked as Agenda+