[svgwg] Clarify hit testing behavior of <foreignObject>
[svgwg] Issue: Browsers do not implement transform attribute syntax as described by w3c marked as Needs CSS WG
[svgwg] Browsers do not implement transform attribute syntax as described by w3c
- Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c
- Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c
- Closed: [svgwg] Browsers do not implement transform attribute syntax as described by w3c
- Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c
[svgwg] Issue: What should happen if you try to set an out of range value on an enum in the DOM marked as Agenda+
[svgwg] Issue: dur attribute should permit leading . marked as Agenda+
Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties
- Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties
- Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties
[svgwg] Pull Request: Add or update dfns for definitions
[svgwg] Issue: Do we really need not to reflect additional enum values in SVG 2 marked as SVG Markers
[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] 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] Do we really need not to reflect additional enum values in SVG 2
[svgwg] What should happen if you try to set an out of range value on an enum in the DOM
[svgwg] Issue: Bounding box algorithm is not precise marked as Co-ordinates chapter
[svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
- Re: [svgwg] Bounding box algorithm is not precise
[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
[svgwg] Issue: Start using URL (instead of URI reference) marked as Needs editing
[svgwg] Start using URL (instead of URI reference)
- Re: [svgwg] Start using URL (instead of URI reference)
- Re: [svgwg] Start using URL (instead of URI reference)
Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers.
- Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers.
- Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers.
[svgwg] new commits pushed by dstorey
[svgwg] Issue: Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit marked as Basic Data Types and Interfaces chapter
[svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit
- Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit
- Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit
- Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit
[svgwg] Pull Request: Keep the linting minions happy
Closed: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement
[svgwg] new commits pushed by dstorey
[svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
- Re: [svgwg] Use <dfn> for definitions
[svgwg] Issue: Clarify relation of isPointInFill and pointer-events marked as Agenda+
[svgwg] Clarify relation of isPointInFill and pointer-events
- Re: [svgwg] Clarify relation of isPointInFill and pointer-events
- Re: [svgwg] Clarify relation of isPointInFill and pointer-events
- Re: [svgwg] Clarify relation of isPointInFill and pointer-events
- Re: [svgwg] Clarify relation of isPointInFill and pointer-events
[svgwg] Pull Request: Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- Re: [svgwg] Add HTMLOrSVGElement mixn
- [svgwg] Merged Pull Request: Add HTMLOrSVGElement mixn
[svgwg] Pull Request: Use DOMPointInit argument for getCharNumAtPosition. #389
[svgwg] Pull Request: Add DocumentAndElementEventHandlers
- Re: [svgwg] Add DocumentAndElementEventHandlers
- Re: [svgwg] Add DocumentAndElementEventHandlers
- Re: [svgwg] Add DocumentAndElementEventHandlers
- Re: [svgwg] Add DocumentAndElementEventHandlers
[svgwg] Issue: Remove "style attributes" from all element definitions marked as SVG Core
[svgwg] Do we need to replace DOMStringMap?
- Re: [svgwg] Do we need to replace DOMStringMap?
- Re: [svgwg] Do we need to replace DOMStringMap?
- Re: [svgwg] Do we need to replace DOMStringMap?
- Closed: [svgwg] Do we need to replace DOMStringMap?
- Re: [svgwg] Do we need to replace DOMStringMap?
Closed: [svgwg] Update WebIDL definition(s) to use new mixin syntax
[svgwg] new commits pushed by dirkschulze
[svgwg] Merged Pull Request: Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353
[svgwg] Deprecate type attribute on SVGStyleElement?
- Re: [svgwg] Deprecate type attribute on SVGStyleElement?
- Re: [svgwg] Deprecate type attribute on SVGStyleElement?
- Re: [svgwg] Deprecate type attribute on SVGStyleElement?
[svgwg] Issue: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint marked as Agenda+
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
- 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
- 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
- Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint
[svgwg] Update SVGScriptElement and SVGImageElement to use src?
- Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src?
- Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src?
- Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src?
[svgwg] new commits pushed by dirkschulze
[svgwg] Merged Pull Request: Clarify patternTransform/linearTransform presentation attriute behavi…
Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers
[svgwg] Pull Request: Update SVGAElement to match attributes on HTMLAnchorElement
[svgwg] new commits pushed by dstorey
[svgwg] Pull Request: Fixes #407 copy-pasto in viewBox definition
Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353
- Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353
- Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353
- Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353
Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
- Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible
Re: [svgwg] SVGAElement implements two conflicting interfaces
Re: [svgwg] Convert SVG linking reftests to .svg files
Closed: [svgwg] "mode" of a shadow root which <use> element uses is unclear
Re: [svgwg] "mode" of a shadow root which <use> element uses is unclear
Re: [svgwg] Revisions to sentence on focusable elements
[svgwg] Merged Pull Request: Revisions to sentence on focusable elements
Re: [svgwg] Change SVGMeshElement to derive from SVGGraphicsElement
[svgwg] Closed Pull Request: Change SVGMeshElement to derive from SVGGraphicsElement
Re: [svgwg] Remove support for segment-completing close path
- Re: [svgwg] Remove support for segment-completing close path
- Re: [svgwg] Remove support for segment-completing close path
- Re: [svgwg] Remove support for segment-completing close path
Re: [svgwg] Fixed path grammar
[svgwg] Closed Pull Request: Add text-transform property to the list of required CSS properties
Re: [svgwg] Add text-transform property to the list of required CSS properties
Re: [svgwg] 'd' presentation attribute: use path() function
Re: [svgwg] Cut down number of categories
[svgwg] Typo in viewBox attribute type definition
[svgwg] Wrong description of percentage units
[svgwg] Issue: Wrong description of "visibility" property marked as Document structure chapter
[svgwg] Wrong description of "visibility" property
Closed: [svgwg] Remove "text content child element" category
Re: [svgwg] Remove "text content child element" category
[svgwg] Issue: Replace <opacity-value> with <alpha-value> marked as SVG Core
[svgwg] Issue: The computed value of fill-opacity and stroke-opacity should never be a percentage marked as SVG Core
[svgwg] Remove "style attributes" from all element definitions
[svgwg] Replace <opacity-value> with <alpha-value>
[svgwg] The computed value of fill-opacity stroke-opacity should never be a percentage
- Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage
- Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage