This is the Disposition of Comments for the 13 April 2005 second Last Call of SVG 1.2. This document lists the comments recieved on the second Last Call specification and the extent to which we believe they have been addressed in the Candidate Recommendation specification.
| Code | Meaning |
|---|---|
| Agree | The commentor and the WG agree on the comment, and if necessary the specification has been altered or clarified to bring it into line with what the commentor requested. |
| Discuss | The comment resulted in some discussion, but no change seemed to be asked for and none was made. |
| Compromise | The commentor and the WG compromise on the comment; the WG has explained why they feel the sugested changes woud not be an improvement, or have drawbacks outweighing the gain, or are too hard to implement. |
| Disagree | The commentor and the WG compromise on the comment, the WG have explained their reasoning, and the commentor has stated they are unsatisfied. |
| Total number of comments | 310 (375) |
| Number of agreed comments | 283 |
| Number of comments where no change was requested or made | 42 |
| Number of comments for which a compromise was found | 46 |
| Number of comments disagreed | 4 |
SVGT12-1 Fwd: Two questions on flowed text in 1.2
Responses: Jon Ferraiolo bulia byak Chris Lilley Chris Lilley Jon Ferraiolo bulia byak David Woolley bulia byak Chris Lilley David Woolley Thomas DeWeese bulia byak Thomas DeWeese bulia byak Chris Lilley Resolution: The existing line-increment property affects the line spacing for text in an area. dx, dy and rotate are not available on 'text' or 'tspan' either, in SVG Tiny 1.2, so the spec is consistent. For richer control, see text in an area in SVG 1.2 Full. |
SVGT12-2 ISSUE: getDocumentElement() --> documentElement
Responses: Christophe Jolif Jonathan Watt Resolution: The IDL is correct, and the example cited was Java not ECMAScript so its syntax is correct also. |
SVGT12-3 [SVGMobile12] Editable text with child elements
Responses: Chris Lilley Resolution: We agreed that the term flattening was insufficiently defined, and added a definition drawn from DOM Level 3. |
SVGT12-4 [SVGMobile12] viewport-fill example
Responses: Chris Lilley Resolution: We agree, the rendering was wrong and has now been corrected. |
SVGT12-5 [SVGMobile12] Chapter 7
Responses: Chris Lilley Cameron McCormack Resolution: The text has been clarified, this is indeed the transform-list part of transform, not the whole attribute. Resolution: The indenting has been fixed to improve readability. Resolution: SVG Tiny 1.2 only has one svg element, so the closest svg element is also the root-most one. The square brackets notation was defined, and the definition has been clarified slightly. |
SVGT12-6 [SVGMobile12] prefetch element
Responses: Chris Lilley Resolution: We agree, the reference to percentages was not correct and has been removed. For numbers, the units of bandwidth are bytes/second as with SMIL, and this has been clarified in the spec. |
SVGT12-7 SVG12: sync* trait access
Responses: Ola Anderson Resolution: Trait access is not required for all svg attributes, it is only required for those attributes listed in the trait access table |
SVGT12-8 SVG12: gzip transfer encoding
Responses: Ola Andersson Resolution: This comment appears to be the same as SVGT12-159 and was dealt with there. |
SVGT12-9 SVG12: 'display' trait
Responses: Ola Andersson Boris Zbarsky Bjoern Hoehrmann Ola Andersson Boris Zbarsky Ola Andersson Bjoern Hoehrmann Boris Zbarsky Chris Lilley Bjoern Hoehrmann Jon Ferraiolo Boris Zbarsky Chris Lilley Bjoern Hoehrmann Ian Hickson Jon Ferraiolo Jon Ferraiolo Ian Hickson David Woolley Ola Andersson Jon Ferraiolo Jon Ferraiolo Chris Lilley Jon Ferraiolo Bjoern Hoehrmann Ola Andersson Resolution: We agreed and changed the spec. This comment appears to be the same as SVGT12-267 getTrait vs 'display' property, and was discussed there. |
SVGT12-10 SVG12: syncTolerance* schema
Responses: Robin Berjon Resolution: The schema was corrected to use the defined datatype. |
SVGT12-11 SVG12: charmod note
Responses: Chris Lilley Resolution: Commentor did not supply any reason to remove the note. |
SVGT12-12 SVG12: "animations execute"
Responses: Chris Lilley Resolution: We agree, and have altered the language to be clearer. |
SVGT12-13 SVG12: 'font-face-URI'
Responses: Chris Lilley Resolution: The mis-spelling was corrected. |
SVGT12-14 SVG12: formal vs prose
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: Removing the text would reduce compliance to QA specification guidelines, so we decline to do so. |
SVGT12-15 SVG12: 19.4 example
Responses: Chris Lilley Resolution: The example is now valid to the RNG and NVDL, and does not make wierd use of XHTML |
SVGT12-16 SVG12: contentScriptType default
Responses: Chris Lilley Resolution: The default has been corrected to application/ecmascript. |
SVGT12-17 SVG12: textArea vs xml:space
Responses: bulia byak Robin Berjon Bjoern Hoehrmann Scott Haymann Resolution: The spec has been updated to remove the reference to xml:space |
SVGT12-18 SVG12: stylesheets not applied
Responses: Chris Lilley Resolution: We have removed the erroneous claim. |
SVGT12-19 SVG12: "prop."?
Responses: Robin Berjon Resolution: We have clarified the draft to implement the commenter's suggestions. |
SVGT12-20 SVG12: standard language bindings
Responses: Chris Lilley Resolution: The standard bindings which had been omitted by mistake have been added. |
SVGT12-21 SVG12: A.7.15 id attribute
Responses: Robin Berjon Anne Van Kesteren Robin Berjon Resolution: The WG has explained the rules for id and xml:id. |
SVGT12-22 SVG12: microsyntaces
Responses: Dean Jackson Resolution: The WG have added links from the prose as requested but not links to the types. |
SVGT12-23 SVG12: getPresentation* naming
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Ian Hickson Dean Jackson Ian Hickson Bjoern Hoehrmann Bjoern Hoehrmann Resolution: No better alternative name was suggested. |
SVGT12-24 SVG12: trait access on illegal names
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The WG has changed the spec. |
SVGT12-25 SVG12: normative DOM definitions
Responses: Vincent Mahe Resolution: We updated the IDL as suggested |
SVGT12-26 SVG12: onpreload, etc attributes
Responses: Ola Andersson Resolution: The WG agrees with this comment and the spec has been changed in a corresponding way. |
SVGT12-27 SVG12: event name casing
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Names were changed to use the correct case |
SVGT12-28 SVG12: svgudom style
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: Styling has improved but not completely to the level Bjoern ask for. |
SVGT12-29 SVG12: traits in the svg namespace
Responses: Ola Andersson Bjoern Hoerhmann Resolution: We agree and have corrected the use of getTraitNS. |
SVGT12-30 SVG12: language of examples
Responses: Chris Lilley Resolution: We agree and have modified the spec so that examples state what programming language is used. |
SVGT12-31 SVG12: #text traits
Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Robin Berjon Jon Ferraiolo Bjoern Hoehrmann Robin Berjon Resolution: The WG declines introducing a change that would break compatibility with JSR-226 |
SVGT12-32 SVG12: DOM references
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree and have updated references to DOM Level 3 throughout. |
SVGT12-33 SVG12: links to attribute, etc. tables
Responses: Chris Lilley Robin Berjon Cyril Concolato Resolution: The draft has been modified to add the links from the tables to the definitions. |
SVGT12-34 SVG12: typos in A.2.6
Responses: Chris Lilley Resolution: We agree and have fixed the typos. |
SVGT12-35 SVG12: when document begins
Responses: Chris Lilley Resolution: We have clarified the document start to take into account the timelineBegin attribute. |
SVGT12-36 SVG12: IDL namespaces
Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: The spec has been updated. |
SVGT12-37 SVG12: Escaping fragment identifiers
Responses: Chris Lilley Resolution: We agree that fragments are not used in resolution so never need to be escaped. |
SVGT12-38 SVG12: IRIs in RFC 2396
Responses: Chris Lilley Resolution: We have corrected the reference, to RFC 3987 |
SVGT12-39 SVG12: 14.1.1 should be table
Responses: Chris Lilley Resolution: We agree, and have reformatted the list as a table. |
SVGT12-40 SVG12: <absoluteIRI> etc
Responses: Chris Lilley Resolution: The language has been corrected so that it does not use undefined terms and so that same-document dreferences are distinguished from local IRI references. |
SVGT12-41 SVG12: eRR for invisible content
Responses: Robin Berjon Resolution: Resolution: Since eRR is a processing requirement whereas not loading invisible media is a permitted optimization, the former naturally takes over. The draft has been clarified to make this more obvious. |
SVGT12-42 SVG12: rendering accuracy
Responses: Jim Ley Chris Lilley Resolution: We agree and have changed the spec from "device pixel" to "px unit" as previously discussed. |
SVGT12-43 SVG12: XML 1.0 vs XML 1.1
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The WG believes the spec is clear. |
SVGT12-44 SVG12: <iri>
Responses: Chris Lilley Resolution: We find that RFC 3986 and RFC 3987 were designed to be compatible. |
SVGT12-45 SVG12: SMIL M12N
Responses: Chris Lilley Chris Lilley Resolution: We agree and have removed this wording from the specification. |
SVGT12-46 SVG12: Charmod norm reference
Responses: Chris Lilley Resolution: We agree and now point to the correct charmod specification; we have clarified that this is a guideline,not a conformance requirement. |
SVGT12-47 SVG12: UAAG reference
Responses: Chris Lilley Chris Lilley Resolution: We now require UAAG priority 1 conformance. |
SVGT12-48 SVG12: DOM-based animation
Responses: Chris Lilley Resolution: We agree that the example was confusing and have rewritten it to use the timer facility in the uDOM |
SVGT12-49 SVG12: "object tag"
Responses: Chris Lilley Resolution: The colloquial 'tag' was changed to 'element'. |
SVGT12-50 SVG12: symbolic links
Responses: Ola Andersson Resolution: We have corrected the erroneous links. |
SVGT12-51 SVG12: Modularization
Responses: Ola Andersson Resolution: Updated modules to include missing attributes and elements. Added links from each module to corresponding RNG file and corresponding feature string. Resolution: Left module definitions at end of each chapter, as this is how it has been done in earlier versions of svg. |
SVGT12-52 SVG12: xml:id in core module
Responses: Chris Lilley Chris Lilley Chris Lilley Resolution: Agree that xml:id should be present. |
SVGT12-53 SVG12: xml:lang definition
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The spec has been updated so that xml:lang takes either a token from "3066 or its successor", or the empty string, |
SVGT12-54 SVG12: RFC 3066 reference
Responses: Chris Lilley Bjoern Hoehrmann Addison Phillips Chris Lilley Martin Duerst Chris Lilley Addison Phillips Felix Sasaki Chris Lilley Resolution: We agree and have changed the reference list as recommended by Addison. |
SVGT12-55 SVG12: SMIL references
Responses: Chris Lilley Chris Lilley Resolution: We agree and have made all SMIL references consistent |
SVGT12-56 SVG12: 11.7 sample rendering
Responses: Chris Lilley Resolution: The sample rendering was fixed to be correct.. |
SVGT12-57 SVG12: xml:space description
Responses: Dean Jackson Bjoern Hoehrmann Resolution: We agree, an nbsp had been converted to a space, so it collapsed in the HTML. Now fixed. |
SVGT12-58 SVG12: textArea text-rendering
Responses: Robin Berjon Resolution: We agree, this is fixed in the spec. The schema was already correct. |
SVGT12-59 SVG12: end-of-line handling
Responses: Chris Lilley Resolution: We agree that character references are not normalized, and have corrected the specification by deleting the erroneous sentence |
SVGT12-60 SVG12: app/ecmascript content
Responses: Chris Lilley Robin Berjon Resolution: No further response from Bjoern |
SVGT12-61 SVG12: references mess
Responses: Chris Lilley Resolution: We agree, and substantially revised the references section. |
SVGT12-62 SVG12: namespace'd events vs animation
Responses: Dean Jackson Resolution: The WG believes the spec is clear. |
SVGT12-63 SVG12: form feed
Responses: Chris Lilley Resolution: We agree, have used correct references to Unicode characters per manual of style, and have dropped the erroneous form feed. |
SVGT12-64 SVG12: event namspaceURI
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree, and have added the namespaceURI attribute on Event. |
SVGT12-65 SVG12: TransformedVideo feature string
Responses: Ola Andersson Resolution: We have changed the spec to use the correct feature strings |
SVGT12-66 SVG12: overlay stacking
Responses: Dean Jackson Resolution: Spec has been clarified. |
SVGT12-67 SVG12: listen to custom events
Responses: Antoine Quint Resolution: We have changed the draft so that there are no mentions of custom events. |
SVGT12-68 SVG12: editable design
Responses: Chris Lilley Resolution: We have clarified the spec regarding DOM changes, and explainedhow editing expectations are platform-dependent |
SVGT12-69 SVG12: 10.4 grammar
Responses: Craig Northway Dean Jackson Bjoern Hoehrmann Resolution: We have corrected the incomplete sentence. |
SVGT12-70 SVG12: color orange
Responses: Chris Lilley Bjoern Hoehrmann Craig Northway Chris Lilley Resolution: css2.0 does not contain orange. The incorrect references has been updated. |
SVGT12-71 SVG12: editable vs scripting
Responses: Robin Berjon Resolution: We have changed the draft so that events on editable text fields are dispatched as expected. |
SVGT12-72 SVG12: editable definition
Responses: Chris Lilley Resolution: The mentions of an editable attribute now all point to the same definition. |
SVGT12-73 SVG12: textArea schema
Responses: Robin Berjon Resolution: Changed the schema fragment to correctly type the attributes. |
SVGT12-74 SVG12: tBreak sequences
Responses: David Woolley Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: The effect of multiple consecutive tbreaks is now explicitly described. |
SVGT12-75 SVG12: system colors
Responses: Chris Lilley Resolution: No change - its very clear in the CSS3 draft that the system colors are deprecated. Its very clear in the SVG one that they are not deprecated. They are now described as System Paint, giving CSS 3 the freedom to deprecate them. |
SVGT12-76 SVG12: height/width defaults
Responses: Craig Northway Bjoern Hoehrmann Chris Lilley Ian Hickson Chris Lilley Ian Hickson Craig Northway Resolution: We agree, the wording has been changed to "If these are not specified, the default values of 100% must be used." |
SVGT12-77 SVG12: "outermost" svg element
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Andrew Shellshear Resolution: Changed all references to "outermost svg element" to "rootmost svg element", updated definitions. |
SVGT12-78 SVG12: A.2.8 addEventListener
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree, addEventListener and addEventListenerNS are both supported |
SVGT12-79 SVG12: A.7.18 style
Responses: Ola Andersson Resolution: We agree, URL is changed from sample.org to example.org |
SVGT12-80 SVG12: 7.2 example
Responses: Ola Andersson Resolution: We agree, URL is changed from sample.org to example.org |
SVGT12-81 SVG12: 7.8 example
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: We agree, example has been fixed to conform to svg tiny 1.2 |
SVGT12-82 SVG12: 6.4 example
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Resolution: We agree, example has been changed |
SVGT12-83 SVG12: 7.13 example
Responses: Chris Lilley Resolution: We agree, and well-formedness errors in example files are fixed. |
SVGT12-84 SVG12: 6.3 example
Responses: Ola Andersson Resolution: Removed DOCTYPE from the example |
SVGT12-85 SVG12: animating xml vs css
Responses: Robin Berjon Bjoern Hoehrmann Cyril Concolato Resolution: Changed and moved the statement about animation of properties into the definition of attributeType. |
SVGT12-86 SVG12: non-sRGB colors
Responses: Dean Jackson Bjoern Hoehrmann Resolution: Agree, SVG Tiny 1.2 does not allow colours in arbitrary spaces. Spec is updated. |
SVGT12-87 SVG12: Progressive rendering not mandatory?
Responses: Nandini Ramani Craig Northway Resolution: Agreed, User Agent must follow the rules outlined for progressive rendering |
SVGT12-88 SVG12: What is "SAX"?
Responses: Craig Northway Resolution: Agreed, changed the document to define the necessary concepts independant of SAX |
SVGT12-89 SVG12: playbackOrder has no "true" value
Responses: Craig Northway Resolution: Agreed, this has now been fixed in the spec |
SVGT12-90 SVG12: eRR vs timelineBegin
Responses: Chris Lilley Resolution: Agreed, in the case where the timelineBegin="onLoad", this will also mean that the animation timeline does not begin. |
SVGT12-91 SVG12: desc/title "text-only"
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Chris Lilley Resolution: Agreed. This is a hold-over from SVG 1.1 where the DTD was unable to express anything more useful. In RNG, and with NVDL, we have done a much better job and the textof the spec now reflects this |
SVGT12-92 SVG12: seeking requirements
Responses: Craig Northway Bjoern Hoehrmann Craig Northway Bjoern Hoehrmann Craig Northway Bjoern Hoehrmann Craig Northway Resolution: Added text clarifying that seeking backwards in the timeline must not re-insert the discarded elements Resolution: The discard element definition will reference the SMIL specification regarding seeking backwards. |
SVGT12-93 SVG12: when vs why discard
Responses: Chris Lilley Craig Northway Ian Hickson Craig Northway Ian Hickson Bjoern Hoehrmann Resolution: Reworded definition of discard criteria to clarify and to have explicit conformance criteria |
SVGT12-94 SVG12: discard begin
Responses: Craig Northway Resolution: added the value "indefinite" to the list of allowed values for the begin attribute Resolution: leave the default value as '0' |
SVGT12-95 SVG12: applicability of timelineBegin
Responses: Chris Lilley Chris Lilley Resolution: We agree that the term 'nested timeline' was unclear and have explained the timelineBegin attribute without using that term. |
SVGT12-96 SVG12: discard not mandatory?
Responses: Chris Lilley Chris Lilley Resolution: The spec has been updated. |
SVGT12-97 SVG12: 'g' id
Responses: Chris Lilley Dean Jackson Dean Jackson Resolution: changed the draft to refer to the xml:id attribute |
SVGT12-98 SVG12: version attribute
Responses: Robin Berjon Resolution: leave the version attribute as-is. |
SVGT12-99 SVG12: <paint> elements
Responses: Dean Jackson Dean Jackson Resolution: Agreed, and changed. Note that viewport-fill does not allow all variations of paint. It can only reference solid colors. |
SVGT12-100 SVG12: width and height in 5.1.2 example
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Chris Lilley Resolution: Changed to say "does not have a fixed width and height" and removed width and height attributes |
SVGT12-101 SVG12: playbackOrder design
Responses: Craig Northway Resolution: The WG agrees with one of Bjoern's somments here and explains the reasoning about the others. |
SVGT12-102 SVG12: snapshotTime optional
Responses: Chris Lilley Resolution: It is thumbnail generation which is optional. SVG says nothing about how big a thumbnail should be, whether it is animated, etc. This language feature allows a content author to pick a moment in time which is useful and representative, in the event that the thumbnail of the animation is a single static image. |
SVGT12-103 SVG12: SVG namespace declaration
Responses: Chris Lilley Resolution: The SVG spec cannot say anything about elements with a local name of svg in other, non-SVG namespaces. No better wording was proposed. |
SVGT12-104 SVG12: standalone declarations
Responses: Chris Lilley Resolution: We agree that standalone="no" has no value, and it has been removed from all examples. |
SVGT12-105 SVG12: Ill-formed example in 1.3
Responses: Chris Lilley Chris Lilley Resolution: All examples were checked for well-formedness and fixed if necessary |
SVGT12-106 SVG12: <color> elements
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Scott Hayman Resolution: We agree, there is now a complete list. |
SVGT12-107 WD-SVGMobile12-20050413: Comments on examples
Responses: Chris Lilley Chris Lilley Resolution: We agree, and have changed most examples to use xml:id as recommended for new content. |
SVGT12-108 interpretation of rotate= attribute
Responses: Chris Lilley Chris Lilley Resolution: Clarification is added. |
SVGT12-109 [SVGMobile12] Well formedness errors in examples
Responses: Chris Lilley Resolution: All examples were checked for well-formedness and fixed if necessary |
SVGT12-110 Implementing DOM 3 event dispatching
Responses: Chris Lilley Resolution: Status of DOM3 events has been explained. |
SVGT12-111 [SVGMobile12] Editorial: Single HTML or PDF file
Responses: jfrost@mbsbooks.com Dean Jackson Jean-Claude Moissinac Paul Cotton Jean-Claude Moissinac Resolution: A single file specification was provided by a third party |
SVGT12-112 SVG Tiny 1.2 should be returned for further work
Responses: Chris Lilley Resolution: A second Last Call will be published |
SVGT12-113 SVG12: Appendix C 1-4
Responses: Robin Berjon Resolution: The identified errors are fixed. |
SVGT12-114 SVG12: "Latest SVG Mobile Recommendation"
Responses: Chris Lilley Resolution: Latest rec indeed points to latest rec. |
SVGT12-115 SVG12: Animation vs Appendix C
Responses: Chris Lilley Resolution: The spec has been edited to remove the questioned paragraph. |
SVGT12-116 SVG12: namespace-illformed fragments
Responses: Ian Hickson Robin Berjon Bjoern Hoehrmann Resolution: The spec has been updated to add some clarification, though the WG has not been thoroughly convinced by the commenter's arguments. |
SVGT12-117 SVG12: data: default type
Responses: Chris Lilley Resolution: The definition referenced from the spec is not ambiguous. |
SVGT12-118 SVG12: target, observer, event, ...
Responses: Chris Lilley Resolution: The spec has been changed to define the missing attributes. The modifications to XMLevents are noted. |
SVGT12-119 SVG12: Informative recommendations
Responses: Andrew Shellshear Resolution: The section in question has been removed. |
SVGT12-120 SVG12: "Animation event names"
Responses: Dean Jackson Resolution: The WG has pointed out his misinterpretation. |
SVGT12-121 SVG12: <handler>, etc. vs <handler>, etc.
Responses: Chris Lilley Resolution: We have noted the concern and will ensure that coordination is maintained. |
SVGT12-122 SVG12: "DTD" and "W3C XML Schema"
Responses: Chris Lilley Resolution: There is no conflict in the specification here. |
SVGT12-123 SVG12: ev:event vs namespaces
Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Resolution: We clarified the spec with respect to unqualified event names. |
SVGT12-124 SVG12: "timer facilities" in ECMAScript
Responses: Ola Andersson Resolution: The spec has been updated to reflect Bjoern's comment. |
SVGT12-125 SVG12: ProgressEvent::typeArg
Responses: Ola Andersson Bjoern Hoehrmann Resolution: Spec is updated |
SVGT12-126 SVG12: ProgressEvent::progress
Responses: Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Example is changed. |
SVGT12-127 SVG12: "event attributes"
Responses: Craig Northway Bjoern Hoehrmann Resolution: Spec is changed. |
SVGT12-128 SVG12: 11.14.1 example
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree with the comment and the example is changed. |
SVGT12-129 SVG12: solid-color:currentColor
Responses: Chris Lilley Resolution: We updated the 'applies to' part of the color property |
SVGT12-130 SVG12: overflow initial value
Responses: Dean Jackson Resolution: We updated the specification to remove 'overflow' |
SVGT12-131 SVG12: missing properties
Responses: Scott Hayman Resolution: Omitted due to an error in the program that processed the RNG; now fixed |
SVGT12-132 SVG12: overflow:inherit
Responses: Chris Lilley Resolution: We agree with the comment and the spec is changed. |
SVGT12-133 SVG12: svg in foreignObject
Responses: Chris Lilley David Baron Chris Lilley David Baron Jon Ferraiolo David Baron Chris Lilley Jon Ferraiolo Chris Lilley Jon Ferraiolo Jon Ferraiolo Resolution: We agree with the comment and the spec is changed. |
SVGT12-134 SVG12: Vendor-specific presentation attributes
Responses: Chris Lilley Resolution: Vendor-specific presentational attributes are already not allowed. |
SVGT12-135 SVG12: textArea a text content element?
Responses: Chris Lilley Resolution: We corrected the spec to add textArea |
SVGT12-136 SVG12: RDF Primer reference
Responses: Chris Lilley Resolution: The spec has been changed to refer to the correct RDF specs. |
SVGT12-137 SVG12: 5.7 example
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: The example is updated in line with Bjoern's comment. |
SVGT12-138 SVG12: version="1.2"
Responses: Chris Lilley Resolution: The contradiction was removed in the spec. |
SVGT12-139 SVG12: mediaCharacterEncoding and mediaContentEncodings
Responses: Chris Lilley Resolution: We agree and removed the requirement. |
SVGT12-140 SVG12: prefetch attribute defaults
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: Spec is now clearer in the description of prefetch. |
SVGT12-141 SVG12: what is "bandwidth"?
Responses: Chris Lilley Resolution: bandwidth has been defined. |
SVGT12-142 SVG12: mediaContentEncodings
Responses: Chris Lilley Resolution: We agree, and defer to HTTP/1.1 for the allowed values. |
SVGT12-143 SVG12: prefetch02.svg
Responses: Charles McCathie-Neville Resolution: We agree and corrected the example. |
SVGT12-144 SVG12: focus* defaults
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree and clarified use of focus defaults. |
SVGT12-145 SVG12: animatable prefetch attributes
Responses: Chris Lilley Resolution: The confusing sentence has been removed. |
SVGT12-146 SVG12: what may prefetch refer to?
Responses: Craig Northway Resolution: The spec has been clarified to state what prefetch can refer to. |
SVGT12-147 SVG12: 16.2.10 example
Responses: Robin Berjon Resolution: The example was wrong and has been changed. |
SVGT12-148 SVG12: 5.1.2 "referenced document"
Responses: Chris Lilley Resolution: We agree, have removed the wording about "referenced document" and clarified the spec regarding viewBox. |
SVGT12-149 SVG12: Navigation behavior
Responses: Craig Northway Chris Lilley Resolution: The spec has been changed to include clearly stated normative statements and some examples. |
SVGT12-150 SVG12: prefetch relationship to SMIL 2.0
Responses: Robin Berjon Resolution: The spec has been changed to describe the differences with SMIL, as requested. |
SVGT12-151 SVG12: nav-* properties
Responses: Ola Andersson Bjoern Hoehrmann Robin Berjon Dean Jackson Dean Jackson Resolution: The spec has changed to address this comment." |
SVGT12-152 SVG12: Cancel events?
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Vincent Mahe Bjoern Hoehrmann Ola Andersson Vincent Mahe Resolution: The WG agrees with this comment. Methods have been added to allow for event cancellation. |
SVGT12-153 SVG12: inconsistent/undefined data types
Responses: Robin Berjon Resolution: The WG agrees. Data type references are now consistent.Data type names capitalization are consistent and links to data types definitions has been added. |
SVGT12-154 SVG12: Undefined feature strings
Responses: Craig Northway Bjoern Hoehrmann Craig Northway Craig Northway Resolution: Feature strings are now correctly defined. |
SVGT12-155 SVG12: ev:listener
Responses: Craig Northway Cyril Concolato Craig Northway Robin Berjon Craig Northway Cyril Concolato Craig Northway Vincent Mahe Resolution: The WG agrees with Bjoern. The specification has been updated to address his comment. |
SVGT12-156 SVG12: "WQ Framework"
Responses: Chris Lilley Resolution: The typo has been corrected. |
SVGT12-157 SVG12: trait table
Responses: Ola Andersson Resolution: The typo has been corrected. We have decided to keep the table as is. |
SVGT12-158 SVG12: 'focusable' property
Responses: Ola Andersson Bjoern Hoehrmann Resolution: The spec has been updated. Bjoern is happy. |
SVGT12-159 SVG12: Transfer-Encoding
Responses: Chris Lilley Boris Zbarsky Chris Lilley Boris Zbarsky Chris Lilley Yves Lafon Chris Lilley Boris Zbarsky Boris Zbarsky Boris Zbarsky Chris Lilley Chris Lilley Boris Zbarsky Yves Lafon Resolution: Settled after much discussion.Content-Encoding carefully distinguished from gzipped Transfer-Encoding. |
SVGT12-160 SVG12: get/setAttribute
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Suresh Chitturi Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Ola Andersson Bjoern Hoehrmann Resolution: The example has been changed. Bjoern is happy. |
SVGT12-161 SVG12: svg:transform attributes
Responses: Antoine Quint Resolution: Typo that will be fixed in the spec |
SVGT12-162 newline handling with xml:space="default"
Responses: Jon Ferraiolo Resolution: An explanation to why the spec is written the way it is has been given. |
SVGT12-163 [SVGMobile12] Conformance criteria
Responses: Chris Lilley Ian Hickson Craig Northway Resolution: The WG has updated the entire specification to ensure properly worded conformance criterias. |
SVGT12-164 Comments on textArea vs flowText
Responses: Doug Schepers David Woolley Doug Schepers Chris Lilley Resolution: The majority of comments were on 1.2 Full, and will be dealt with there; explanations were given for the changes in 1.2 Tiny, which mainly allow re-use of existing line-breaking code. |
SVGT12-165 [SVGMobile12] 5.8.1: interaction of conditional processing and use is unclear
Responses: Jon Ferraiolo Chris Lilley L. David Baron Chris Lilley Resolution: We have made some clarifications to how the rendering tree is defined. Resolution: We quoted parts of the spec to show that other aspects were already well defined. |
SVGT12-166 [SVGMobile12] 5.8.3: disallowed feature strings
Responses: Jon Ferraiolo |