This is the Disposition of Comments for the 7 December 2005 third Last Call of SVG 1.2. This document lists the comments recieved on the third 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 | 297 |
| Number of agreed comments | 257 |
| Number of comments where no change was requested or made | 76 |
| Number of comments for which a compromise was found | 19 |
| Number of comments disagreed | 22 |
|
SVGT12-8 SVG12: gzip transfer encoding Responses: Ola Andersson Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: The SVG WG believes the commenter misunderstands transfer-encoding. Resolution: This comment appears to be the same as SVGT12-159 and was dealt with there. |
|
SVGT12-10 SVG12: syncTolerance* schema Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The schema was corrected to use the defined datatype. |
|
SVGT12-11 SVG12: charmod note Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: Conformance to charmod part 1: Fundamentals is now explicitly required for content and implementations. |
|
SVGT12-12 SVG12: "animations execute" Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Resolution: We agree, and have altered the language to be clearer. |
|
SVGT12-14 SVG12: formal vs prose Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: Removing the text would reduce compliance to QA specification guidelines, so we decline to do so. |
|
SVGT12-18 SVG12: stylesheets not applied Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We have removed the erroneous claim. |
|
SVGT12-19 SVG12: "prop."? Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: We have clarified the draft to implement the commenter's suggestions. (The commenter being extremely unclear as to why he's still unhappy, we couldn't do more the second time around) |
|
SVGT12-20 SVG12: standard language bindings Responses: Chris Lilley Bjoern Hoehrmann Bjoern Hoehrmann 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Chris Lilley Resolution: The WG has explained the rules for id and xml:id, and clarified them based on close coordination with XML Core. |
|
SVGT12-22 SVG12: microsyntaces Responses: Dean Jackson Dean Jackson Bjoern Hoehrmann Andrew Emmons Resolution: The WG have added the missing definitions Resolution: The WG have added links from the prose as requested but not links to the types. |
|
SVGT12-24 SVG12: trait access on illegal names Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Resolution: The WG has changed the spec. |
|
SVGT12-25 SVG12: normative DOM definitions Responses: Vincent Mahe Bjoern Hoehrmann Robin Berjon Resolution: We updated the IDL as suggested |
|
SVGT12-32 SVG12: DOM references Responses: Ola Andersson Bjoern Hoehrmann Bjoern Hoehrmann Robin Berjon 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We decline to group attributes in the format commenter requests. Resolution: The draft has been modified to add the links from the tables to the definitions. |
|
SVGT12-36 SVG12: IDL namespaces Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Nandini Ramani Resolution: The spec has been updated. |
|
SVGT12-37 SVG12: Escaping fragment identifiers Responses: Chris Lilley Bjoern Hoehrmann Resolution: We agree that fragments are not used in resolution so never need to be escaped. |
|
SVGT12-40 SVG12: <absoluteIRI> etc
Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The language has been corrected so that it does not use undefined terms and so that same-document references are distinguished from local IRI references. |
|
SVGT12-41 SVG12: eRR for invisible content Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear 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 Bjoern Hoehrmann Chris Lilley 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 Bjoern Hoehrmann Resolution: We have updated the spec to address the issues raised by the commenter. |
|
SVGT12-44 SVG12: <iri> Responses: Chris Lilley Bjoern Hoehrmann Felix Sasaki Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: The data type <iri> has been replaced with <XMLRI> and <FuncXMLRI> Resolution: We find that RFC 3986 and RFC 3987 were designed to be compatible. |
|
SVGT12-48 SVG12: DOM-based animation Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andy Sledd Resolution: We have updated the specification of Timer interface and the createTimer method of the SVGGlobal interface. Resolution: We agree that the example was confusing and have rewritten it to use the timer facility in the uDOM |
|
SVGT12-51 SVG12: Modularization Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: Removed modules and put the information previously in modules in the feature string appendix instead. 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: Agree that xml:id should be present. |
|
SVGT12-55 SVG12: SMIL references Responses: Chris Lilley Chris Lilley Bjoern Hoehrmann Andrew Shellshear Resolution: We agree and have made all SMIL references consistent |
|
SVGT12-61 SVG12: references mess Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We agree, and substantially revised the references section. |
|
SVGT12-62 SVG12: namespace'd events vs animation
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Erik Dahlstrom Bjoern Hoehrmann Andrew Emmons Resolution: Commenter wishes us to change functionality that has been in the spec since SVG Tiny 1.0. Resolution: We have put all events in the interactivity chapter in the null namespace. |
|
SVGT12-66 SVG12: overlay stacking Responses: Dean Jackson Bjoern Hoehrmann Resolution: Spec has been clarified. |
|
SVGT12-68 SVG12: editable design Responses: Chris Lilley Bjoern Hoermann Chris Lilley Resolution: We have clarified the spec regarding DOM changes, explainedhow editing expectations are platform-dependent, and described flattening |
|
SVGT12-69 SVG12: 10.4 grammar Responses: Craig Northway Dean Jackson Bjoern Hoehrmann Bjoern Hoehrmann Andrew Shellshear Resolution: We have changed all instances of "XML character data" to "XML content". Resolution: We have corrected the incomplete sentence. |
|
SVGT12-71 SVG12: editable vs scripting Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: We will consider adding richer examples during CR 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 Doug Schepers Bjoern Hoehrmann Chris Lilley Ola Andersson Resolution: The mentions of an editable attribute now all point to the same definition. |
|
SVGT12-75 SVG12: system colors Responses: Chris Lilley Bjoern Hoehrmann 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 Bjoern Hoehrmann Scott Hayman Resolution: We agree, the wording has been changed to "If these are not specified, the default values of 100% must be used." Resolution: We agree, the wording has been changed to cover all cases" |
|
SVGT12-82 SVG12: 6.4 example Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We agree, example has been changed |
|
SVGT12-85 SVG12: animating xml vs css Responses: Robin Berjon Bjoern Hoehrmann Cyril Concolato Bjoern Hoehrmann Chris Lilley Resolution: Changed and moved the statement about animation of properties into the definition of attributeType. Resolution: The commenter misunderstood the intent of attributeType |
|
SVGT12-87 SVG12: Progressive rendering not mandatory?
Responses: Bjoern Hoehrmann Andrew Emmons Resolution: The requirements document has been updated to state that there are optional parts ( progressive rendering is an optional part ). |
|
SVGT12-90 SVG12: eRR vs timelineBegin Responses: Chris Lilley Bjoern Hoehrmann Andrew Emmons Resolution: Agreed, in the case where the timelineBegin="onLoad", this will also mean that the animation timeline does not begin. Resolution: Agreed. The timeout case has been listed as an example. |
|
SVGT12-94 SVG12: discard begin Responses: Craig Northway Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon 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 Bjoern Hoehrmann Bjoern Hoehrmann Resolution: We agree that the term 'nested timeline' was unclear and have explained the timelineBegin attribute without using that term. |
|
SVGT12-102 SVG12: snapshotTime optional Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Ola Andersson 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 Bjoern Hoehrmann 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 Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Resolution: We agree that standalone="no" has no value, and it has been removed from all examples. |
|
SVGT12-107 WD-SVGMobile12-20050413: Comments on
examples Responses: Chris Lilley Chris Lilley Dave Hodder Dean Jackson Resolution: We agree, and have changed most examples to use xml:id as recommended for new content. Resolution: We have changed remaining examples to use xml:id as recommended for new content, and fixed other examples as suggested. |
|
SVGT12-116 SVG12: namespace-illformed fragments Responses: Ian Hickson Robin Berjon Bjoern Hoehrmann Bjoern Hoehrmann Robin Berjon Resolution: The spec has been updated to add some clarification, all references are now dual as requested. |
|
SVGT12-117 SVG12: data: default type Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The definition referenced from the spec is not ambiguous. |
|
SVGT12-118 SVG12: target, observer, event, ... Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Mark Birbeck Robin Berjon Resolution: We have reverted to using the existing XML Events unmodified. |
|
SVGT12-120 SVG12: "Animation event names" Responses: Dean Jackson Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Doug Schepers Resolution: Commenter wishes to change the animation event value syntax, but we must defer until DOM3 is done and the SMIL Spec addresses namespaced events. Resolution: Changed typo 'repeat' back to 'repeatEvent'. Resolution: The WG has pointed out his misinterpretation, but he disagrees. |
|
SVGT12-121 SVG12: <handler>, etc. vs
<handler>, etc. Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Scott Hayman Resolution: We've changed the spec to simply refer to XML Events. Resolution: We have noted the concern and will ensure that coordination is maintained. |
|
SVGT12-123 SVG12: ev:event vs namespaces Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Dean Jackson Resolution: We clarified the spec with respect to unqualified event names. |
|
SVGT12-130 SVG12: overflow initial value Responses: Dean Jackson Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We updated the specification to remove 'overflow' |
|
SVGT12-131 SVG12: missing properties Responses: Scott Hayman Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Resolution: Omitted due to an error in the program that processed the RNG; now fixed |
|
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 Bjoern Hoehrmann Robin Berjon Resolution: We agree with the comment and the spec is changed. |
|
SVGT12-134 SVG12: Vendor-specific presentation
attributes Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: Vendor-specific presentational attributes are already not allowed. |
|
SVGT12-137 SVG12: 5.7 example Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: The example is updated in line with Bjoern's comment. |
|
SVGT12-143 SVG12: prefetch02.svg Responses: Charles McCathie-Neville Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: We agree and corrected the example. |
|
SVGT12-148 SVG12: 5.1.2 "referenced document" Responses: Chris Lilley Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Jon Ferraiolo Ola Andersson Resolution: We agree, have removed the wording about "referenced document" and clarified the spec regarding viewBox. |
|
SVGT12-150 SVG12: prefetch relationship to SMIL 2.0
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: Changed incorrect ref to local-IRI into non-local-IRI. 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 Jon Ferraiolo Dean Jackson Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Maciej Stachowiak Jeff Rafter Doug Schepers Bjoern Hoehrmann Resolution: The spec has changed to address this comment. Resolution: Commenter believes navigation model and future liason commitments to be unsatisfactory. |
|
SVGT12-153 SVG12: inconsistent/undefined data types
Responses: Robin Berjon Bjoern Hoehrmann 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-156 SVG12: "WQ Framework" Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The typo has been corrected. |
|
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 Bjoern Hoehrmann Doug Schepers Resolution: Settled after much discussion.Content-Encoding carefully distinguished from gzipped Transfer-Encoding. |
|
SVGT12-161 SVG12: svg:transform attributes Responses: Antoine Quint Bjoern Hoehrmann Chris Lilley Resolution: We have defined the attribute in the same style that others are defined. |
|
SVGT12-163 [SVGMobile12] Conformance criteria Responses: Chris Lilley Ian Hickson Craig Northway Ian Hickson Chris Lilley Ian Hickson Chris Lilley Resolution: The WG has updated the entire specification to ensure properly worded conformance criterias. Resolution: The issue of further improving normativity was retracted after comparison with CSS2.1 spec. |
|
SVGT12-183 [SVGMobile12] Comment: Please give specific
error-handling behaviour Responses: Doug Schepers Jon Ferraiolo David Woolley Ian Hickson Bjoern Hoehrmann Boris Zbarsky Jon Ferraiolo Boris Zbarsky Ian Hickson Jon Ferraiolo L. David Baron Robin Berjon David Woolley David Woolley Jim Ley Ian Hickson Boris Zbarsky Charles McCathieNevile Ian Hickson Nandini Ramani Ian Hickson Scott Hayman Ian Hickson Scott Hayman Scott Hayman Ian Hickson Scott Hayman Ian Hickson Scott Hayman Resolution: The WG has explained the concept of svg error handling. Resolution: Invalid IRIs must be treated as if 'none' were specified. |
|
SVGT12-188 [SVGMobile12] Comments: Multimedia
Responses: Chris Lilley T Rowley T Rowley Scott Hayman Resolution: We explained the need for constrained video, and that a point is still geometric Resolution: The rationale for the SMIL-compatible animation element was explained Resolution: The error in the example was corrected Resolution: The spec now states that the values of the width and height attributes do not affect the rendering of the video element. |
|
SVGT12-197 [SVGMobile12] Comments: Coordinate
Systems, Transformations and Units Responses: Chris Lilley T Rowley Chris Lilley T Rowley T Rowley Resolution: The possibility of a supplemental user rotation was explained Resolution: We added an explanation of the use case for this feature Resolution: The geographical metadata does not affect rendering, adds semantics and increases interoperabilty for higher-level systems. We clarified that it does not affect rendering |
|
SVGT12-203 [SVGMobile12] 2.1.5: SVG not appropriate for
multi-namespace use Responses: Dean Jackson Boris Zbarsky Bjoern Hoehrmann Chris Lilley Jonathan Watt Ian Hickson Jonathan Watt Ian Hickson Resolution: The comment does not seem to apply to SVG Tiny 1.2; the comment about font-shorthand ambiguity has been carried forward to Full. |
|
SVGT12-205 [SVGMobile12] Comments: The SVG Micro DOM
(uDOM) Responses: Dean Jackson Tim Rowley Robin Berjon T Rowley Resolution: Network API's are in our charter and will still be part of the specification. |
|
SVGT12-243 SVG12: units for font-size descriptor
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The draft has been changed to remove font-size, and the commenter has been notified. |
|
SVGT12-244 SVG12: 'WheelEvent' "registration"
Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: The draft has been modified to implement the commenter's request and a reply has been sent. |
|
SVGT12-246 SVG12: currentTime definition Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: We removed some unnecessary text from the spec that might confuse readers and added a definition of document time. |
|
SVGT12-247 SVG12: A.7.18 ownerDocument attribute Responses: Antoine Quint Bjoern Hoehrmann Nandini Ramani Resolution: Examples changed and request to Sun made Resolution: Spec has been changed per Bjoern's suggestion and Antoine sent Bjoern a response. |
|
SVGT12-249 SVG12: gotoLocation behavior Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: We clarified the definition of gotoLocation as requested. |
|
SVGT12-250 SVG12: A.7.18 example Responses: Antoine Quint Bjoern Hoehrmann Ola Andersson Resolution: The example has been fixed to be well-formed Resolution: A request to Sun has been put in to register application/java-archive |
|
SVGT12-252 SVG12: SVGGlobal vs ELI2 Responses: Robin Berjon Bjoern Hoehrmann Nandini Ramani Maciej Stachowiak Robin Berjon Maciej Stachowiak Dean Jackson Resolution: We have changed the draft so that no object implements the EventListenerInitializer2 interface. |
|
SVGT12-255 SVG12: xlink:href default value Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: The typo has been fixed. Resolution: The traits table has been changed so that getTraitNS is used instead of getTrait, as can be expected. The default value is maintained to be the empty string but the excepted return values has been modified to take into account the empty string as a valid value. |
|
SVGT12-261 SVG12: A.4.11 vs lengthComputable
requirements Responses: Robin Berjon Bjoern Hoehrmann Doug Schepers Resolution: The draft has been changed to clarify that switch processing only affects the rendering tree. Resolution: The draft has been updated so as to remove any assumption that lengthComputable would be set to true during the processing of ProgressEvents. |
|
SVGT12-262 SVG12: 'switch' processing Responses: Robin Berjon Bjoern Hoehrmann Bjoern Hoehrmann Ola Andersson Resolution: The draft has been changed so that the '/' is now an "and", thereby clarifying the intended meaning. We have also removed the word "bypassed" as it was causing confusion. |
|
SVGT12-263 SVG12: which elements do requiredFeatures,
etc. apply to? Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The draft has been changed to remove the first bullet containing the non-exhaustive list, as well as to clarify the other bullets, clearly specifying where the test attributes apply, as well as adding to the attributes table. |
|
SVGT12-264 SVG12: binding-specific discussion in A.2.10
Responses: Robin Berjon Bjoern Hoehrmann Ola Andersson Resolution: The draft has been changed to indicate that this section is specific to the Java(tm) platform and has no applicability whatsoever elsewhere. |
|
SVGT12-265 SVG12: SVGGlobal::document vs AbstractView
Responses: Robin Berjon Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Boris Zbarsky Jon Ferraiolo Boris Zbarsky Jon Ferraiolo Jim Ley Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Bjoern Hoehrmann Doug Schepers Doug Schepers Resolution: We will reference a new WebAPI spec for this if one comes available and meets our requirements Resolution: The SVGGlobal::document field is of type Document so as to be compatible with the expected Global::document field since in some languages it is not necessarily possible to subclass a class and change the type of one of its fields. It is expected that casting will be used where necessary. The current specification assumes that forthcoming definitions of the Global interface will not inherit or otherwise implement the AbstractView interface (though they may provide other means of accessing it) so as not to create unnecessary conflicts. |
|
SVGT12-266 SVG12: attribute/trait "normalization"
Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: The draft states that "A user agent is allowed to store normalized attribute values internally as described in DOM 3[0]". This entails that implementations are indeed allowed to store values in the way most optimal to them and setting an attribute and getting its value back immediately may not produce the same value that was used when setting. This will apply not only to SVG Full 1.2 but in fact to any implementation of DOM Level 3 Core. Consequently, we have not changed the draft. |
|
SVGT12-267 SVG12: getTrait vs 'display'
property Responses: Chris Lilley Bjoern Hoehrmann Jon Ferraiolo Resolution: We have changed the draft such that the computed value of the display property, on the one hand, and the value returned by getTrait on the display property are clearly distinguished. Resolution: We have modified the draft to add extensive clarification in order to make sure that implementers will not be able to miss a single detail, as you required. The specification now details the differences between the trait accessors which for backward compatibility reasons can only access normalised values, and the attribute accessors which may provide access to the original value. |
|
SVGT12-269 SVG12: SVGPath::close lacks prose Responses: Antoine Quint Bjoern Hoehrmann Resolution: The draft has been changed to reflect the intended "Appends a 'z' (close path) segment to the path." |
|
SVGT12-271 SVG12: non-visual foreign markup Responses: Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Resolution: The WG has explained that requiring foreignObject to have a geometric size to operate even when used for non-visual content is not an issue. This is further supported by the fact that non-visual content can be used outside of foreignObject, either with foreign namespaces or with facilities such as the 'audio' element. |
|
SVGT12-272 SVG12: http://www.w3.org/TR/SVG12/feature
strings Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear Resolution: The draft has been changed so that the feature strings correspond to those listed in the appendix. Resolution: Additional examples were fixed to refer to the correct feature strings. |
|
SVGT12-273 SVG12: uDOM vs DOMImplementation Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: All mention of hasFeature has been removed. |
|
SVGT12-274 SVG12: svg:discard feature string Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Resolution: Discard feature string was missing. Added as suggested. |
|
SVGT12-275 SVG12: base IRI for element instances
Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Chris Lilley Resolution: We agree, and have defined base IRI processing in a manner consistent with shadow trees. |
|
SVGT12-276 SVG12: animateMotion vs transform="" Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Bjoern Hoehrmann Resolution: We added text specifying that animateMotion and animateTransform may be applied to any element that can have a transform attribute. Resolution: The absence of the 'transform' attribute on 'animation' was an oversight in the schema which has been corrected, and 'textPath' has been added to the list of supported elements. Note however that supporting the 'transform' attribute and being a target for 'animateMotion' are orthogonal features. |
|
SVGT12-277 SVG12: animation of path data Responses: Nandini Ramani Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: We explained behaviour of discrete animation to commenter. Resolution: We explained to commenter that paths are normalised before comparison, but not necessarily on getAttributeNS. Resolution: He is correct and the spec has been changed to reflect this. |
|
SVGT12-278 SVG12: cumulative animation targets
Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Maciej Stachowiak Resolution: Commenter wishes to register a formal objection. Resolution: We explained to commenter that additive is precondition of cumulative. Resolution: We have checked that additive and accumulate link to the correct definitions in SMIL 2.0 |
|
SVGT12-279 SVG12: animating transform ref() Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: The spec now explicitly says that ref() cannot be animated. Resolution: The group believes the new wording is sufficient to resolve ambiguity. |
|
SVGT12-280 SVG12: IDL "int" Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: The draft has been changed so as to refer to "long" instead of "int". |
|
SVGT12-281 SVG12: !important in property animation
Responses: Chris Lilley Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: The way SMIL and SVG define this issue has been explained multiple times to the commenter. |
|
SVGT12-282 SVG12: animation with indirect values
Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: We agree and have clarified the specification |
|
SVGT12-283 SVG12: animation of <color>
and <paint> Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We agree and have clarified the specification regarding keywords which give animatable values, such as colors. |
|
SVGT12-284 SVG12: feature strings vs "supports" Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: color-rendering was indeed missing from the Paint Attributes module; we added it Resolution: We do not see the more general point regarding ambiguity, and quoted the spec to demonstrate this. |
|
SVGT12-289 SVG12: transform on <defs>
Responses: Nandini Ramani Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Resolution: transform attribute on 'defs' is now removed. |
|
SVGT12-290 SVG12: wheelDelta should be UIEvent.detail
Responses: Chris Lilley Bjoern Hoehrmann Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Scott Hayman Scott Hayman Resolution: It was not possible to use UIEvent.detail as it is already used by the event inherited from (MouseEvent). Resolution: There is no issue with readonly attributes as uDOM doesn't support createEvent. |
|
SVGT12-291 SVG12: conversion to float vs NaN Responses: Nandini Ramani Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Nandini Ramani Resolution: The WG has explained the rationale here. |
|
SVGT12-293 SVG12: illegal non-xlink:href animation
targets Responses: Scott Hayman Bjoern Hoehrmann Scott Hayman Resolution: The spec has been changed to address this comment. |
|
SVGT12-295 SVG12: 'target' "trait" default value
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Resolution: The WG has resolved to change the default value to "_self". |
|
SVGT12-296 SVG12: getRGBColorTrait vs non-SVGRGBColor
Responses: Ola Andersson Bjoern Hoehrmann Andrew Shellshear Cameron McCormack Chris Lilley Cameron McCormack Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Resolution: The spec has been further updated to clarify that paint server is returned. Resolution: The spec has been changed to address this comment. |
|
SVGT12-301 SVG12: getCurrentFocusedObject return type
Responses: Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Resolution: getCurrentFocusedObject now returns EventTarget. |
|
SVGT12-302 SVG12: DOMObject portability Responses: Andrew Shellshear Boris Zbarsky Ola Andersson Anne van Kesteren Robin Berjon Anne van Kesteren Robin Berjon Mark Birbeck Boris Zbarsky Bjoern Hoehrmann Andrew Shellshear Resolution: getCurrentFocusedObject now returns EventTarget. |
|
SVGT12-303 SVG12: currentTime vs SVG 1.1 Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The requested change was made. |
|
SVGT12-304 SVG12: Document.documentElement definition
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The draft has been modified to fix the grammar and provide a more orthodox definition, by reference. |
|
SVGT12-307 SVG12: setAttributeNS exceptions Responses: Antoine Quint Ian Hickson Dean Jackson Ian Hickson Dean Jackson Bjoern Hoehrmann Resolution: The suggested fixes have been applied, namely to add the NOT_SUPPORTED_ERR, NO_MODIFICATION_ALLOWED_ERR, INVALID_CHARACTER_ERR and NAMESPACE_ERR exceptions to the definition of Element::setAttributeNS() to the uDOM. Resolution: Removed exception throwing behaviour for setAttributeNS() on version and base profile. |
|
SVGT12-308 SVG12: createElementNS exceptions Responses: Antoine Quint Bjoern Hoehrmann Antoine Quint Bjoern Hoehrmann Antoine Quint Resolution: The suggested fixes have been applied, namely to add the INVALID_CHARACTER_ERR and NAMESPACE_ERR exceptions to the definition of Document::createElementNS() to the uDOM. |
|
SVGT12-311 [SVGMobile12] SVGT12-207: <title>
does not define what the title is Responses: Chris Lilley Ian Hickson Chris Lilley Ian Hickson Chris Lilley Ian Hickson Maciej Stachowiak Jim Ley Jon Ferraiolo Anne van Kesteren Doug Schepers Jon Ferraiolo Chris Lilley Resolution: The varied uses of title and description elements, also the differences from the single HTML title element inthe head, were explained. Resolution: The UA may display the flattened text string for a title, and may choose to do more. |
|
SVGT12-312 [SVGMobile12] SVGT12-207: Behaviour of
<a> pointing into same document outside SVG document fragment is not defined
Responses: Chris Lilley Ian Hickson Chris Lilley Ian Hickson Chris Lilley Ian Hickson Scott Hayman Ian Hickson Scott Hayman Ian Hickson Scott Hayman Ian Hickson Scott Hayman Resolution: We will not add a restriction that something can refer to somewhere in the current document but outside the current document fragment. Resolution: We will clarify that SVG Tiny does not support this. |
|
SVGT12-313 [SVGMobile12] No witches please Responses: Dean Jackson Resolution: Fixed the typo. |
|
SVGT12-314 [SVGMobile12] typos? Responses: Dean Jackson Resolution: Fixed the typos. |
|
SVGT12-315 SVG 1.2 Tiny: Please add changes from last
version Responses: Chris Lilley Resolution: We plan to add colour-coding to Elements and Attributes Appendix to show diffs with SVG 1.1 Full and SVG 1.1 Tiny Resolution: We plan to produce an overview of changes from SVG 1.1 Full and SVG 1.1 Tiny to SVG 1.2 Tiny Resolution: We will try to add this during CR. |
|
SVGT12-316 SVG 1.2 Tiny: Networking API issues Responses: Chris Lilley Maciej Stachowiak Resolution: No change to connection APIs, but make mention of security concerns |
|
SVGT12-317 SVGT12-207: Conflicting requirements in 5.9.3 The
'prefetch' element Responses: Chris Lilley Ian Hickson Chris Lilley Resolution: Clarified that MediaSize has precedence over MediaTime. |
|
SVGT12-318 SVGT12-207: Unclear rules regarding
mediaCharacterEncoding and mediaContentEncodings Responses: Chris Lilley Chris Lilley Ian Hickson Chris Lilley Ian Hickson Resolution: The wording was clarified regarding mediaContentEncoding |
|
SVGT12-319 SVGT12-207: id/xml:id statement that does not
match conformance criteria Responses: Robin Berjon Resolution: The change in wording has been made. |
|
SVGT12-320 [SVGMobile12] typo in Schema title Responses: Robin Berjon Resolution: We agree, and have fixed the typo. |
|
SVGT12-321 [SVGMobile12] SVGT12-207: No conformance criteria
for how to parse attribute values Responses: Chris Lilley Ian Hickson Robin Berjon Ian Hickson Chris Lilley Ian Hickson Resolution: We pointed out the xisting EBNFs and what the specification already says regarding unsupported values. |
|
SVGT12-322 [SVGMobile12] STZLC3-4 animation of
xlink:href of a media Responses: Doug Schepers Bjoern Hoehrmann Jean-Claude Dufourd Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: Timeline progresses regardless of readiness of media. |
|
SVGT12-323 [SVGMobile12] STZLC3-1 on viewport-fill
Responses: Chris Lilley Resolution: Value 'none' added to list. |
|
SVGT12-324 [SVGMobile12] STZLC3-2 on display=none
and audio Responses: Doug Schepers Chris Lilley Jon Ferraiolo Resolution: Clarified spec to make it clear that audio is part of the rendering tree |
|
SVGT12-325 [SVGMobile12] STZLC3-3 definition of the
intrinsic duration of a media Responses: Dean Jackson Resolution: Defined by the SMIL specification. |
|
SVGT12-326 [SVGMobile12] STZLC3-5 media element in a
defs Responses: Chris Lilley Resolution: A defs element does not influence the 'timing' part of SMIL animation elements. |
|
SVGT12-327 [SVGMobile12] STZLC3-6 overlapping
display=none and media element Responses: Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Resolution: The timing engine is orthogonal to the rendering tree. Resolution: We added text to the animation introduction clarifying that the timing engine is orthogonal to the rendering tree. |
|
SVGT12-328 Last Call SVG 1.2 Tiny Comments: Circular
Definition Responses: Robin Berjon Jeff Schiller Resolution: Commenter agrees that the existing wording is sufficient. |
|
SVGT12-329 SVG 1.2 Tiny Working Draft 3 Comments: More
Typos Responses: Andrew Shellshear Resolution: We fixed the typos. |
|
SVGT12-330 SVG 1.2 Tiny Working Draft 3 Comments:
Transform Stack Typo Responses: Andrew Shellshear Resolution: We fixed the typo. |
|
SVGT12-331 SVG 1.2 Tiny Working Draft 3 Comments:
Misplaced Audio Paragraph Responses: Andrew Shellshear Resolution: We have elimination the duplication, and created a new section to describe the mixing of audio. |
|
SVGT12-332 [SVGMobile12] 13.12.4 changeNavigationOrder.svg
typo Responses: Andrew Shellshear Resolution: We fixed the typo. |
|
SVGT12-333 [SVGMobile12] content of the handler
attribute of listener Responses: Mark Birbeck Jean-Claude Dufourd Dean Jackson Resolution: Clarification provided |
|
SVGT12-334 [SVGMobile12] 15.3 Java example incorrect
Responses: Andrew Shellshear Resolution: We fixed the typo. |
|
SVGT12-335 [SVGMobile12] processing attribute values
and basic data types Responses: Andrew Shellshear |
|
SVGT12-336 [SVGMobile12], Focus navigation and circular
dependencies Responses: Andrew Shellshear Andrew Shellshear Resolution: We agree that we need a mechanism for escaping from the focus loop, and have added one. |
|
SVGT12-337 [SVGMobile12] STZLC3-8 missing bubble
phase information in events table Responses: Andrew Shellshear Bjoern Hoehrmann Jean-Claude Dufourd Andrew Shellshear Resolution: We added the bubbling phase information to the events table. |
|
SVGT12-338 [SVGMobile12] STZLC3-9 listening to
document events Responses: Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Anne van Kesteren Mark Birbeck Robin Berjon Mark Birbeck Robin Berjon Bjoern Hoehrmann Robin Berjon Mark Birbeck Mark Birbeck Resolution: We declined to add this feature, as it is possible to do via scripting, and does not have strong enough use cases to add for this version. |
|
SVGT12-339 [SVGMobile12] SVGT12-207: Section 7.13 doesn't
say how to get aspect ratio from viewBox Responses: Andrew Shellshear Ian Hickson Andrew Shellshear Ian Hickson Andrew Shellshear Resolution: Clarified that aspect ratio is width divided by height. |
|
SVGT12-340 SVGT 1.2: uDOM appendChild and insertChild
conflict with DOM, Implementation Requirements Responses: Robin Berjon Maciej Stachowiak Resolution: All DOM now by reference. |
|
SVGT12-341 SVGT 1.2: no way to tell through uDOM if an
attribute is present Responses: Cyril Concolato Maciej Stachowiak Andrew Shellshear Resolution: We prefer not to add hasAttributeNS for this version. |
|
SVGT12-342 SVGT 1.2: no way to remove an attribute
Responses: Andrew Shellshear Resolution: We prefer not to add removeAttributeNS for this version. |
|
SVGT12-343 SVGT 1.2: no way to traverse children of
non-SVG elements Responses: Andrew Shellshear Resolution: We agree, and have specificed that ElementTraversal can be applied to the Element interface. |
|
SVGT12-344 SVGT 1.2: uDOM DOMImplementation.hasFeature
Responses: Robin Berjon Maciej Stachowiak Resolution: We have removed hasFeature. |
|
SVGT12-345 SVGT 1.2: uDOM Node methods/attributes with
minor textual differences from DOM Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-346 SVGT 1.2: uDOM Node.removeChild more
restrictive than DOM Level 3 Core Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-347 SVGT 1.2: uDOM.{get,set}AttributeNS
inconsistent with DOM3 Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-348 SVGT 1.2: uDOM vs DOM Responses: Robin Berjon Maciej Stachowiak Resolution: We agree with option 3, to provide the union of DOM and uDOM interfaces. |
|
SVGT12-349 SVGT 1.2: textContent is not compliant with
DOM3 Core version Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-350 SVGT 1.2: lack of capture phase for event
handling Responses: Robin Berjon Resolution: The change was effected. |
|
SVGT12-351 SVGT 1.2: uDOM EventListener interface
identical to DOM, claims to be subset Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-352 SVGT 1.2: Document behavior for Node
interfaces Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-353 SVGT 1.2: uDOM Event methods and attributes
have only minor wording differences Responses: Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-354 SVGT 1.2: uDOM Document interfaces with
minor wording differences from DOM Responses: Robin Berjon Robin Berjon Maciej Stachowiak Resolution: DOM is now all by reference. |
|
SVGT12-355 SVGT 1.2: OriginalEvent underspecified;
behavior could be a security risk Responses: Bjoern Hoehrmann Maciej Stachowiak Ola Andersson Maciej Stachowiak Resolution: OriginalEvent removed. |
|
SVGT12-356 SVGT 1.2 3rd last call: XML 1.1 references
Responses: Ola Andersson Resolution: The spec has been updated to address the issues found by the commenter. |
|
SVGT12-357 [SVGMobile12] Rendering tree Responses: Ola Andersson Anne van Kesteren Ola Andersson Anne van Kesteren Ola Andersson Anne van Kesteren Ola Andersson Bjoern Hoehrmann Anne van Kesteren Bjoern Hoehrmann Resolution: The spec has been updated. font, linearGradient and radialGradient are not part of the rendering tree. |
|
SVGT12-358 [SVGMobile12] Referenced SVG liveness Responses: Ola Andersson Bjoern Hoehrmann T Rowley Resolution: The intent of the questioned section has been explained. |
|
SVGT12-359 SVGT 1.2: "shadow content" Responses: Ola Andersson Resolution: 'animation' does not create a shadow tree. This is now clarified in the spec. |
|
SVGT12-360 SVGT 1.2: Claim that uDOM is compatible
subset of the DOM Responses: Robin Berjon Maciej Stachowiak Resolution: All DOM is now by reference. |
|
SVGT12-361 SVGT 1.2: Need for uDOM as a DOM subset is
poorly justified Responses: Andy Sledd Resolution: Some non-normative text was changed to address the concerns. |
|
SVGT12-362 SVGT 1.2: "evt" vs "event" as the implicit
event argument to event handlers Responses: Doug Schepers Maciej Stachowiak Sigurd Lerstad Boris Zbarsky Chris Lilley Anne van Kesteren Robin Berjon Doug Schepers Chris Lilley Maciej Stachowiak Maciej Stachowiak Maciej Stachowiak Chris Lilley Jonathan Watt Ian Hickson Chris Lilley Jonathan Watt Chris Lilley Jonathan Watt Ian Hickson Robin Berjon Ola Andersson Maciej Stachowiak Resolution: We added "event" as an alias to "evt". |
|
SVGT12-363 SVGT 1.2: event handler function equivalent
code is invalid ECMAScript syntax Responses: Ola Andersson Maciej Stachowiak Resolution: The spec has been changed per the suggestion of this comment, Function is replaced by function. |
|
SVGT12-364 SVGT 1.2: !important is an error Responses: Ola Andersson Anne van Kesteren Doug Schepers Robin Berjon Anne van Kesteren Anne van Kesteren Chris Lilley Anne van Kesteren Robin Berjon Anne van Kesteren Chris Lilley Robin Berjon Ian Hickson Doug Schepers Ian Hickson Doug Schepers Maciej Stachowiak Jon Ferraiolo Ian Hickson Bjoern Hoehrmann Ian Hickson Resolution: The lexical space and the value space are distinct. The WG has explained the rationale behind this restriction. No spec change is needed. |
|
SVGT12-365 SVGT 1.2: <image> does not support
SVG Responses: Ola Andersson Anne van Kesteren Chris Lilley Jon Ferraiolo Anne van Kesteren Anne van Kesteren Robin Berjon Maciej Stachowiak Maciej Stachowiak Chris Lilley Ola Andersson Bjoern Hoehrmann Maciej Stachowiak Chris Lilley Anne van Kesteren Resolution: The reason for animation being timed and image being not timed were explained Resolution: Use of image element in fullfor non-animated uses was agreed Resolution: The conformance requirements on SVG impolementations that are part of XHTMl, SMIL, or CSS implementations were removed. |
|
SVGT12-366 SVGT 1.2: Copy/Paste/Change Responses: Chris Lilley Resolution: We ave noted and fixed the specific incompatibilities brought to our attention Resolution: The CSS lexicalspace for external stylesheets is not the same as for formatting attributes Resolution: SMIL makes some requirements of host languages, which SVG provides |
|
SVGT12-367 SVGT 1.2: XML events handlers attached to
elements from other documents Responses: Robin Berjon Maciej Stachowiak Resolution: The adoption of XML Events as is solves this. |
|
SVGT12-368 SVGT 1.2: XML events vs. handler attributes
Responses: Chris Lilley Andrew Emmons Resolution: We feel XML events are more extensible and are the way to go forward. |
|
SVGT12-369 SVGT 1.2: CDATA blocks for scripts Responses: Robin Berjon Maciej Stachowiak Chris Lilley Maciej Stachowiak Chris Lilley Resolution: We clarified to the sender that both examples are correct. |
|
SVGT12-370 SVGT 1.2: dynamic changes to
<handler> elements Responses: Jim Ley Boris Zbarsky Jim Ley Boris Zbarsky Jim Ley Boris Zbarsky Maciej Stachowiak Jim Ley Maciej Stachowiak Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Resolution: We agreed that changes to handler should be reflected dynamically. |
|
SVGT12-371 SVGT 1.2: order of script execution and
load event Responses: Jon Ferraiolo Jon Ferraiolo Jon Ferraiolo Maciej Stachowiak Resolution: We have changed the specification to say that the script executes before the element's load event occurs. |
|
SVGT12-372 SVGT 1.2: <handler> script
scope and `this' object Responses: Andrew Emmons Andrew Emmons Resolution: Changed spec to acknowledge that it does not have global scope, and that we meant global context and local scope. Resolution: Changed spec to clarify that the observer is placed into the scope chain and is bound to the this keyword in ECMAScript. |
|
SVGT12-373 [SVGMobile12] SVGT12-207: Incorrect assertion in
section 7.1 regarding information provided to the UA Responses: Jon Ferraiolo Resolution: Removed redundant and unnecessary words from 7.1. |
|
SVGT12-374 [SVGMobile12] SVGT12-207: "positioning
properties" and other incorrect prose regarding CSS Responses: Jon Ferraiolo Resolution: Fixed the spec so that if the parent document is CSS styled then the SVG follows the rules of replaced elements, otherwise here is how it is defined for other contexts such as XSL. |
|
SVGT12-375 [SVGMobile12] SVGT12-207: Why are UAs allowed to
have varying definitions of "px"? Responses: Chris Lilley Ian Hickson Chris Lilley Ian Hickson Jim Ley Chris Lilley Resolution: Added wording to spec giving example that that operating systems vary in their ability to say what the display density is. |
|
SVGT12-376 [SVGMobile12] SVGT12-207: 7.3 The initial
coordinate system lacks conformance criteria Responses: Jon Ferraiolo Resolution: Editorial fixes made to add "must" at appropriate places. |
|
SVGT12-377 [SVGMobile12] SVGT12-207: Support for
transformations is optional? Responses: Jon Ferraiolo Resolution: We discussed the feedback but felt it is self-evident that implementations need to support transformations. |
|
SVGT12-378 [SVGMobile12] SVGT12-207: viewBox conformance
requirements Responses: Jon Ferraiolo Resolution: Editorial fixes made to replace "should" with "must" at appropriate places. |
|
SVGT12-379 [SVGMobile12] SVGT12-207: Conformance
requirements for preserveAspectRatio Responses: Jon Ferraiolo Resolution: Editorial fixes made to replace "should" with "must" at appropriate places. |
|
SVGT12-380 [SVGMobile12] Implementation specific authoring
advice Responses: Doug Schepers T Rowley Resolution: The authoringadvice is general, and not implementation specific. Resolution: The commenter believes the specification is not a place for authoring style recommendations. |
|
SVGT12-381 [SVGMobile12] SVGT12-207: 7.12 Object bounding
box units Responses: Doug Schepers Resolution: Added normative definition of bounding-box. |
|
SVGT12-382 [SVGMobile12] discard element definition location
Responses: Robin Berjon Resolution: The WG thinks that element is at the right location. |
|
SVGT12-383 [SVGMobile12] discard with nonexistent target
Responses: Chris Lilley Resolution: Fixed the spec so that we only have option 2 of the contradiction. |
|
SVGT12-384 [SVGMobile12] visibility and 'use' Responses: Chris Lilley Resolution: Fixed the spec so that the use/visibility paragraph gets reordered. |
|
SVGT12-385 [SVGMobile12] image element DOM model Responses: Chris Lilley T Rowley Chris Lilley Resolution: Redundant text removed. |
|
SVGT12-386 [SVGM[obile12] requiredFormats psuedo MIME types
Responses: Chris Lilley T Rowley Chris Lilley Anne van Kesteren Resolution: W3C is registering its own types, and encourages other organisations to do likewise. |
|
SVGT12-387 [SVGMobile12] required requiredFormats Responses: Chris Lilley Resolution: We agree and have corrected the list. |
|
SVGT12-388 [SVGMobile12] requiredFormats attribute description
Responses: Chris Lilley Resolution: We agree and have changed the spec as requested |
|
SVGT12-389 [SVGMobile12] Progressive rendering event
description Responses: Chris Lilley Anne van Kesteren Resolution: We have referenced the XML specifications for the definitions |
|
SVGT12-390 [SVGMobile12] progressive rendering examples Responses: Dean Jackson Resolution: We agree, and have changed the text. |
|
SVGT12-391 [SVGMobile12] requiring progressive rendering Responses: Charles McCathieNevile Chris Lilley Resolution: We have explained the value of the feature and that it is testable. |
|
SVGT12-392 [SVGMobile12] SVGT12-207: 'line-increment'
redundant Responses: Chris Lilley Ian Hickson Chris Lilley Maciej Stachowiak Resolution: We want to keep it, and we don't have the same box or area model as CSS or XSL, so we need to define it. Its based off existing SVG-Tiny mechanisms for a fixed line increment. |
|
SVGT12-393 [SVGMobile12] prefetch element too complicated
Responses: Chris Lilley Resolution: Explained to commenter that for network bandwidth, we have inherited it from SMIL. |
|
SVGT12-394 [SVGMobile12] SVGT12-207: 'line-increment' not
compatible with CSS Responses: Chris Lilley Resolution: We have explained that the XSL and CSS line-height properties are not the same and do not provide the required functionality. |
|
SVGT12-395 [SVGMobile12] SVGT12-207:
<textArea> redundant with HTML Responses: Doug Schepers Jeff Schiller Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Ian Hickson Ian Hickson Resolution: Implementors and content developers have requested this features and are satisfied with the functionality, so we are going to keep it. |
|
SVGT12-396 [SVGMobile12] SVGT12-207: SVG Tiny 1.2 does not
comply to AWWW Responses: Chris Lilley Ian Hickson Chris Lilley Maciej Stachowiak Chris Lilley Ian Hickson Resolution: The WG believes that the spec is indeed in accordance with AWWW. Resolution: Other people have given us specific feedback about incompatibilites with other specs, and we have resolved them. |
|
SVGT12-397 [SVGMobile12] SVGT12-207: Incompatibility with
XML Events Responses: Charles McCathieNevile Ian Hickson Resolution: In order to simplify compatibility with the existing XML events specification, we will use the existing XML events specification as it is. |
|
SVGT12-398 [SVGMobile12] SVGT12-207: Requirement to
implement XML Events Responses: Charles McCathieNevile Ian Hickson Resolution: In order to simplify compatibility with the existing XML events specification, we will use the existing XML events specification as it is. |
|
SVGT12-399 [SVGMobile12] SVGT12-207: Conformance to uDOM
Responses: Ian Hickson Jon Ferraiolo Jeff Schiller Antoine Quint Ian Hickson Ian Hickson Jeff Schiller Bjoern Hoehrmann Ian Hickson Bjoern Hoehrmann Bjoern Hoehrmann Ian Hickson Antoine Quint Maciej Stachowiak Maciej Stachowiak Jon Ferraiolo Robin Berjon Ian Hickson Resolution: We changed the text to refer more to DOM instead of copying the text from the DOM specification. |
|
SVGT12-400 [SVGMobile12] SVGT12-207: Requirements on
copy/paste UI Responses: Chris Lilley Ian Hickson Resolution: The commentor seems to wish the Working group to conflict with CharMod part 1: Fundamentals. We decline to do so. Resolution: Commentor misunderstood the requirement; nothing to do with UI. Resolution: We have added tests on bidi selection to the test suite, contrary to the commentor's claims on untestability. |
|
SVGT12-401 [SVGMobile12] SVGT12-207: Requirements on system
interaction Responses: Ola Andersson Resolution: We agreed to change the requirement from must to should. |
|
SVGT12-402 [SVGMobile12] transform attribute and error handling
Responses: Eric Seidel Robin Berjon Resolution: We replied that it is not an error and doesn't conform to the syntax, so you ignore. |
|
SVGT12-403 [SVGMobile12] SVGT12-207: Meaning of "backwards
compatible" in section 1.3 Responses: Ola Andersson Ian Hickson Resolution: We explained what backwards compatible means. Resolution: We made it more explicit in the specification what happens. |
|
SVGT12-404 SVGT 1.2: <use> and
<foreignObject> Responses: Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Maciej Stachowiak Cameron McCormack Jon Ferraiolo Cameron McCormack Eric Seidel Jon Ferraiolo Resolution: We made the test case for interaction with one instance of something used in multiple places. Resolution: We clarified that the foreignObject will be replicated as multiple copies of a single instance, so they all update at the same time. |
|
SVGT12-405 SVGT 1.2: Section 1.4, svgz Responses: Jim Ley Boris Zbarsky Jon Ferraiolo Jon Ferraiolo Jon Ferraiolo Eric Seidel Bjoern Hoehrmann Resolution: Added further explanatory text regarding Content-Encoding and Transfer-Encoding |
|
SVGT12-406 SVGT 1.2: Appendix E, Requirement 12, Identify
Deprecated Features Responses: Ola Andersson Resolution: We have located and listed the deprecated features. |
|
SVGT12-407 SVGT 1.2: Addendum: <svg:image>
support of external SVG content Responses: Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Resolution: Repeat of LC-14. Various technical complexities led to decision that SVG content can only be referenced by svg:animation elements. |
|
SVGT12-408 SVGT 1.2: General Comment uDOM Responses: Robin Berjon Resolution: The specification has largely been changed to address his concerns already, and is moving towards greater satisfaction still. |
|
SVGT12-409 [SVGMobile12] system paint and gradients Responses: Jon Ferraiolo T Rowley Chris Lilley Resolution: We reworded the specification to better clarify the section on System Paint for clarity. |
|
SVGT12-410 [SVGMobile12] color Responses: Jon Ferraiolo T Rowley Chris Lilley Anne van Kesteren Chris Lilley Anne van Kesteren Resolution: Tim complains that we are duplicating the CSS definition of 'color', but our definition is not the same, and we removed the reference to CSS2 in response to other feedback. |
|
SVGT12-411 [SVGMobile12] SVGT12-207: Incorrect computed
value for 'audio-level' Responses: Chris Lilley Resolution: Computed value corrected; volume can now be increased as well as decreased. |
|
SVGT12-412 [SVGMobile12] missing rotate event Responses: Andrew Emmons Resolution: A rotate event has been added. |
|
SVGT12-413 SVGT 1.2: Appendix C3: SVG Error Processing
Responses: Jim Ley Jon Ferraiolo Maciej Stachowiak Ian Hickson Jim Ley Jim Ley Maciej Stachowiak Jim Ley David Woolley Jon Ferraiolo David Woolley Anne van Kesteren David Woolley Boris Zbarsky Jon Ferraiolo Ian Hickson Jon Ferraiolo Ian Hickson Maciej Stachowiak David Woolley Maciej Stachowiak Jon Ferraiolo David Woolley Maciej Stachowiak Resolution: We already have attributes that allow unsupported values. We consider our level of error handling to be appropriate. |
|
SVGT12-414 SVGT 1.2: SVGMatrix gratuitously
incompatible with SVG 1.1 version Responses: Robin Berjon Resolution: We will keep it as is. We admit that we did not catch JSR-226's "change". Full 1.1 implementers should support both - there is no conflict, and we'll try to clarify the spec in this regard. |
|
SVGT12-415 Re: [SVGMobile12] SVGT12-207: Incorrect computed
value for 'fill', 'stroke' Responses: Andreas Neumann Ian Hickson Andreas Neumann Ian Hickson Andreas Neumann Ian Hickson Chris Lilley Resolution: Changed the spec so that for all properties which are shared with CSS 1.2 we have the same line for computed value. |
|
SVGT12-416 [SVGMobile12] SVGT12-207: Incorrect computed
value for 'stop-color', 'solid-color' Responses: Andreas Neumann Resolution: Fixed the computed values for color properties. |
|
SVGT12-417 [SVGMobile12] SVGT12-207: Interaction with XLink
Responses: Charles McCathieNevile Ian Hickson Erik Dahlstrom Ian Hickson Resolution: Clarified that the behaviour is well-defined. |
|
SVGT12-418 [SVGMobile12] Connection::send error handling
Responses: Robin Berjon Robin Berjon Resolution: The WG agrees, and have added a code for security errors, alongside text indicating when UAs may decide to report such problems. |
|
SVGT12-419 [SVGMobile12] SVGT12-207: Conformance criteria
for 14.3.2 SVG fragment identifiers Responses: Chris Lilley Doug Schepers Chris Lilley Resolution: We have clarified the language in 14.3.2. |
|
SVGT12-420 [SVGMobile12] SVGT12-207: event "alias"es
Responses: Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Ian Hickson Erik Dahlstrom Resolution: We have removed event aliasing in favour of double-dispatching, and we have defined the order events fire in. |
|
SVGT12-421 [SVGMobile12] SVGT12-207: capture is
"unsupported"? Responses: Scott Hayman Anne van Kesteren Resolution: We updated the spec to allow implementations, but not content, to use event capture. |
|
SVGT12-422 SVGT 1.2: mention of removeEventListener
for <listener> element Responses: Scott Hayman Maciej Stachowiak Scott Hayman Resolution: Mention of removeEventListener was removed. |
|
SVGT12-423 [SVGMobile12] SVGT12-207: Grammatical errors
Responses: Andrew Shellshear Ian Hickson Andrew Shellshear Resolution: We agreed to fix up grammatical errors reported to us. Resolution: We went through the spec and fixed spelling errors that we found. Resolution: We asked STC to review SVG Mobile 1.2 for grammar and typos. |
|
SVGT12-424 [SVGMobile12] SVGT12-207: Too many issues (again)
Responses: L. David Baron Doug Schepers Ian Hickson Marc Verstaen Antoine Quint Jonathan Watt Bjoern Hoehrmann Marc Verstaen Cyril Concolato Maciej Stachowiak Marc Verstaen Resolution: We have substantially extended the review period. We will make a full draft available to allow reviewers to see the disposition of comments in the context of a full draft before proceeding to another stage. |
|
SVGT12-425 SVGT 1.2: Please extend the Last Call
period Responses: Chris Lilley Andreas Neumann Anne van Kesteren Andreas Neumann Maciej Stachowiak Anne van Kesteren Robin Berjon Ian Hickson Maciej Stachowiak Resolution: We extended the deadline to Jan 27. |
|
SVGT12-426 SVGT 1.2: requirements for pointer
selection Responses: Doug Schepers Maciej Stachowiak Chris Lilley David Woolley Resolution: We changed the text selection wording. Resolution: We clarified to commenter about how selecting links in html works. |
|
SVGT12-427 SVGT 1.2: SVG fragment identifiers
Responses: Doug Schepers Maciej Stachowiak Doug Schepers Chris Lilley Doug Schepers Doug Schepers Doug Schepers Maciej Stachowiak Maciej Stachowiak Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: A secondary commenter dislikes the working group's decision to correct the fragment identifier behaviour. Resolution: We clarified the linking architecture with reference to webarch Resolution: We added text for specifying behavior of non existing fragment identifiers, and explanation of link architecture, and added new behavior for fragment identifiers. |
|
SVGT12-428 [SVGMobile12] SVGT12-207: "editable"
attribute for text Responses: Doug Schepers Maciej Stachowiak David Woolley Doug Schepers Maciej Stachowiak Chris Lilley Cameron McCormack Bjoern Hoehrmann Maciej Stachowiak Chris Lilley Doug Schepers Resolution: The discrepancy between the schema and the text was corrected Resolution: Editing of structured text (by flattening) is already described Resolution: Text was moved to the relevant section as suggested Resolution: Text now includes tBreak elements, instead of strict flattening |
|
SVGT12-429 [SVGMobile12] SVGT12-207: use of xml:space
for whitespace Responses: Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Andrew Emmons Resolution: Although harmonization of whitespace behavior is a valid goal, the working group will look into this in a future spec. |
|
SVGT12-430 [SVGMobile12] Yet more typos Responses: Scott Hayman Resolution: Typos will be fixed. |
|
SVGT12-431 [SVGMobile12] Don't fully ignore font-face-src
elements Responses: Chris Lilley Resolution: We deleted font-face-name from the spec, and verified example 20_01 |
|
SVGT12-432 [SVGMobile12] A.3.3 Element Responses: Robin Berjon Resolution: Everything is now a reference to DOM 3. |
|
SVGT12-433 SVG 1.2 Tiny: Networking API issues Responses: Chris Lilley Maciej Stachowiak Chris Lilley Maciej Stachowiak Chris Lilley Resolution: We declined to state a single security model. Resolution: Added text to state that UAs are allowed to restrict the networking api due to security reasons. |
|
SVGT12-434 [SVGMobile12] IDL Typos Responses: Jeff Schiller Andrew Shellshear Resolution: We have reviewed the chapter and fixed all typos we could find. |
|
SVGT12-435 [SVGMobile12] SVGElementInstance, EventTarget,
currentTarget, use and defs Responses: Jon Ferraiolo Resolution: Fixed confusing wording. Resolution: Explained behaviour with defs and events. |
|
SVGT12-436 [SVGMobile12] textContent defined via
incomplete copy/paste and incompatibly Responses: Robin Berjon Resolution: DOM is by reference now. |
|
SVGT12-437 [SVGMobile12] A.7.5 SVGRGBColor attributes
should not be readonly Responses: Robin Berjon Resolution: We have changed them to be read/write. |
|
SVGT12-438 [SVGMobile12] Comments Responses: Andrew Shellshear Resolution: The comments listed will be addressed. |
|
SVGT12-439 Effect of 'animateMotion' on
transform.animVal Responses: Jon Ferraiolo Bjoern Hoehrmann Bjoern Hoehrmann Chris Lilley Cameron McCormack Scott Hayman Cameron McCormack Resolution: Deferable - does not require change to functionality. Resolution: AnimateMotion is a supplemental transform, so the animated value of the transform attribute itself does not change. |
|
SVGT12-441 [SVGMobile12] more on data types Responses: Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Maciej Stachowiak Jon Ferraiolo Eric Seidel Jon Ferraiolo Bjoern Hoehrmann Maciej Stachowiak Cameron McCormack Ian Hickson Boris Zbarsky Ola Andersson Thomas Deweese Anne van Kesteren Jim Ley Thomas Deweese Robin Berjon Jim Ley Jim Ley Robin Berjon Jim Ley Robin Berjon Jim Ley Robin Berjon Christophe Jolif mental Jim Ley Rick Graham Ian Hickson Ian Hickson Bjoern Hoehrmann David Woolley Maciej Stachowiak Jim Ley Thomas Deweese Thomas Deweese Robin Berjon Robin Berjon Thomas Deweese Anne van Kesteren Jon Ferraiolo Ian Hickson Jim Ley Thomas Deweese Ian Hickson Doug Schepers Anne van Kesteren Robin Berjon Bjoern Hoehrmann Anne van Kesteren Doug Schepers Chris Lilley Doug Schepers Anne van Kesteren Resolution: Commentor still wants looser datatypes: case insensitive, optional whitespace, etc. The WG declines to do so, preferring to retain compatibility with XSL as requested by the XSL WG. Resolution: Further restricted color keywords to be lowercase only. Resolution: We explained the SVG Working Group position on case-sensitivity and leading- and trailing-spaces. Resolution: We believe the spec is sufficiently clear regarding parsing these attribute values. Resolution: Some of the issues raised are issues with SVG Full. |
|
SVGT12-442 [SVGMobile12] No ECMAScript bindings defined
for uDOM Responses: Chris Lilley Chris Lilley Resolution: We agree and have updated the manifest to sure they get published. |
|
SVGT12-443 [SVGMobile12] STZLC3-10 missing
definition of computed value Responses: Ola Andersson Resolution: We revised section 6.7 to point to CSS2 computed-value |
|
SVGT12-444 [SVGMobile12] script element processing
Responses: Chris Lilley Anne van Kesteren Bjoern Hoehrmann Chris Lilley Anne van Kesteren Chris Lilley Anne van Kesteren Ian Hickson Doug Schepers Ian Hickson Robin Berjon Resolution: We have addressed Anne's request by defining how various types are processed |
|
SVGT12-445 [SVGMobile12] listener element Responses: Jim Ley Anne van Kesteren Mark Birbeck Anne van Kesteren Maciej Stachowiak Maciej Stachowiak Robin Berjon Mark Birbeck Ian Hickson Jim Ley Robin Berjon Mark Birbeck Maciej Stachowiak Resolution: The spec has been changed to reference rather than copy xml events. |
|
SVGT12-446 [SVGMobile12] followed versus immediately
followed Responses: Scott Hayman Anne van Kesteren Resolution: We agree that there is no difference between "followed" and "immediately followed". We've removed the word "immediately" as appropriate. |
|
SVGT12-447 [SVGMobile12] version and baseProfile
Responses: Scott Hayman Resolution: The case where both "version" and "baseProfile" is needed was explained. |
|
SVGT12-448 [SVGMobile12] XML Events Responses: Charles McCathieNevile Anne van Kesteren Resolution: In order to simplify compatibility with the existing XML events specification, we will use the existing XML events specification as it is. |
|
SVGT12-449 [SVGMobile12] uDOM attribute normalization
and getAttribute Responses: Robin Berjon Anne van Kesteren Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Resolution: The conflict suggested between normalization behaviour and DOM Level 3 core was a misunderstanding. |
|
SVGT12-450 [SVGMobile12] requirements in SVG uDOM
Responses: Ola Andersson Resolution: Changed spec to create a normative and informative introductory overview. |
|
SVGT12-451 [SVGMobile12] uDOM attribute normalization
on color values Responses: Chris Lilley Resolution: We have explained that trait access is preferable to forcing users to microparse |
|
SVGT12-452 [SVGMobile12] SVGElement description
Responses: Robin Berjon Resolution: Spec clairified. |
|
SVGT12-453 [SVGMobile12] Connection interface Responses: Chris Lilley Resolution: We referred to our charter |
|
SVGT12-454 [SVGMobile12] Concern about "Relative to
absolute IRI conversion" attribute normalization Responses: Scott Hayman Boris Zbarsky Resolution: The IRI normalization list item was removed. |
|
SVGT12-455 [SVGMobile12] Gradient color interpolation
Responses: Chris Lilley Resolution: Fixed the spec to point to relevant sections for compositing of gradients. |
|
SVGT12-456 [SVGMobile12] viewBox attribute Responses: Scott Hayman Anne van Kesteren Scott Hayman Resolution: Added EBNF for viewBox attribute. |
|
SVGT12-457 [SVG12] Issues regarding stroke-dasharray Responses: Jon Ferraiolo Jon Ferraiolo Jon Ferraiolo Resolution: We updated the language in the description of the various basic shapes to make it clear how dash patterns are stroked for each shape type. |
|
SVGT12-458 attributeType=auto Responses: Chris Lilley Eric Seidel Resolution: We agree, and clarified that all CSS properties known to the implementation are searched. |
|
SVGT12-459 [SVG12Mobile] Issue with Transform
Normalization example Responses: Andrew Emmons Boris Zbarsky Resolution: Agree. The example has been modified to add precision typical of 16.16 fixed point. |
|
SVGT12-460 [SVGMobile12] Definition of the <number>
type makes nonsensical claims about range Responses: Chris Lilley Resolution: We agree and adopted the suggested text |
|
SVGT12-461 [SVGMobile12] A.2.7 Transform Normalization
Responses: Andrew Emmons Resolution: Agree. The typos have been fixed. |
|
SVGT12-462 [SVGMobile12] A.2.7 IRI Normalization Responses: Ola Andersson Resolution: The spec has been changed to correct the typo. |
|
SVGT12-463 [SVGMobile12] A.2.8 Text Node Access Responses: Ola Andersson Resolution: The spec has been changed as he suggests. |
|
SVGT12-464 [SVGMobile12] A.2.7 Color normalization Responses: Jon Ferraiolo Chris Lilley Resolution: Explained that trait accessors remove the need for script authors to do this microparsing. |
|
SVGT12-465 [SVGMobile12] A.2.4 Element Addition Responses: Robin Berjon Jonathan Watt Robin Berjon Robin Berjon Resolution: Small editorial change, made. |
|
SVGT12-466 [SVGMobile12] A.2.7 Display normalization
Responses: Chris Lilley Resolution: CDF has been asked to specify this for mixed, CDI SVG and XHTML scenarios.. |
|
SVGT12-467 [SVGMobile12] A.2.5 Element Removal Responses: Robin Berjon Jonathan Watt Resolution: Small editorial change, made. |
|
SVGT12-468 Typo in parseXML description Responses: Robin Berjon Resolution: We have corrected the typo. |
|
SVGT12-469 [SVGMobile12] parseXML requires XML 1.1 support
Responses: Robin Berjon Resolution: This has been modified to be in line with the rest of SVG where XMLNS 1.0 applies to XML 1.0 and 1.1 to 1.1. |
|
SVGT12-470 [SVGMobile12]
SVGSVGElement::createSVGMatrixComponents Responses: Robin Berjon T Rowley Robin Berjon Resolution: Can't effect change due to JSR-226. |
|
SVGT12-471 [SVGMobile12] SVGMatrix Responses: Maciej Stachowiak Robin Berjon T Rowley Resolution: Can't effect change due to JSR-226. |
|
SVGT12-472 [SVGMobile12] SVGPath Responses: Robin Berjon Resolution: Convenience change that we decline to make at this late stage. |
|
SVGT12-473 [SVGMobile12] uDOM Responses: Maciej Stachowiak Robin Berjon Resolution: All DOM now by reference. |
|
SVGT12-474 [SVGMobile12] Properties on elements Responses: Chris Lilley Resolution: Clarified operation of properties and atttributes to commenter. |
|
SVGT12-475 [SVGMobile12] Attribute and property tables
claim some properties cannot be inherited Responses: Chris Lilley Resolution: We clarified the description of property as requested. |
|
SVGT12-476 [SVGMobile12] <svg:svg> width and
height should provide intrinsic size in a CSS context Responses: Chris Lilley Boris Zbarsky Chris Lilley Boris Zbarsky Resolution: We clarified the wording as requested. |
|
SVGT12-477 [SVGMobile12] Sentence describing the effect of
"height" on the initial viewport is unclear Responses: Chris Lilley Boris Zbarsky Chris Lilley Resolution: We agree that the wording is unclear, and have fixed it as suggested. |
|
SVGT12-478 [SVGMobile12] Section 3.3 grammar nit Responses: Chris Lilley Chris Lilley Resolution: Fixed the wording as requested. |
|
SVGT12-479 [SVGMobile12] Issue SVGT12-175 not resolved
Responses: Andrew Shellshear Boris Zbarsky Andrew Shellshear Boris Zbarsky Andrew Shellshear Boris Zbarsky Andrew Shellshear Resolution: Updated definition of SVG Document Fragment to state that nested svg elements are unsupported elements. |
|
SVGT12-480 [SVGMobile12] A.7.19 SVGGlobal Responses: Andrew Emmons Anne van Kesteren Andrew Emmons Anne van Kesteren Andrew Emmons Resolution: Explained that CDF covers SVGGlobal interface. |
|
SVGT12-481 [SVGMobile12] A.7.19 gotoLocation Responses: Boris Zbarsky Jonathan Watt Boris Zbarsky Maciej Stachowiak Boris Zbarsky Maciej Stachowiak Jim Ley Boris Zbarsky Andrew Emmons Boris Zbarsky Bjoern Hoehrmann Chris Lilley Jonathan Watt Resolution: The name gotoLocation is already in use. Resolution: We changed the spec so that empty string in gotoLocation reloads the current document. |
|
SVGT12-482 [SVGMobile12] A.7.19 getURL and postURL Responses: Boris Zbarsky Jonathan Watt Maciej Stachowiak Robin Berjon Resolution: We decline to define security models in greater detail, as different implementations will wish for different security models. Resolution: We have separated the paragraph on security concerns and enhanced the wording. |
|
SVGT12-484 [SVGMobile12] A.7.19 parseXML Responses: Anne van Kesteren Jim Ley Boris Zbarsky Robin Berjon Anne van Kesteren Resolution: Clarified wording that parseXML produces a node not a document. |
|
SVGT12-485 [SVGMobile12] A.6.3 Connection Responses: Robin Berjon Anne van Kesteren Resolution: We decline to define security models in greater detail, as different implementations will wish for different security models. We will reuse work from WebAPI. |
|
SVGT12-486 [SVGMobile12] Question on SVG implementation in
an XLink-aware processor Responses: Chris Lilley Anne van Kesteren Robin Berjon Anne van Kesteren Boris Zbarsky Boris Zbarsky Anne van Kesteren Chris Lilley Chris Lilley Anne van Kesteren Boris Zbarsky Bjoern Hoehrmann Boris Zbarsky Chris Lilley Chris Lilley Boris Zbarsky Chris Lilley Chris Lilley Boris Zbarsky Resolution: The proposed markup is not licensed by the SVG specification and is thus out of scope, as confirmed on the XLink public list; see also SVG spec re unsupported values |
|
SVGT12-487 [SVGMobile12] Section 14.2 -- What is the difference between "_replace" and "_self"
Responses: Chris Lilley Boris Zbarsky Chris Lilley Resolution: The difference was explained. The WG will liaise with CDF WG to put examples into the CDR test suite. |
|
SVGT12-488 [SVGMobile12] parseXML method description has
some wording that could be improved Responses: Scott Hayman Boris Zbarsky Resolution: Typos and text clarifications have been incorporated into the document. |
|
SVGT12-489 [SVGMobile12] parseXML method needs
clarification Responses: Erik Dahlstrom Boris Zbarsky Erik Dahlstrom Boris Zbarsky Erik Dahlstrom Boris Zbarsky Andrew Emmons Resolution: The parseXML wording has been clarified in the spec. |
|
SVGT12-490 [SVGMobile12] Not sure what section 15.2
paragraph 2 is saying Responses: Andrew Shellshear Resolution: The sentence was fixed. |
|
SVGT12-491 [SVGMobile12] Please exorcise witches from
section A.2.6 ;) Responses: Scott Hayman Resolution: The typo was fixed. |
|
SVGT12-492 [SVGMobile12] Node interface method and
property descriptions should just reference the Core DOM Responses: Robin Berjon Resolution: Core DOM by reference. |
|
SVGT12-493 [SVGMobile12] Question on load events
Responses: Andy Sledd Boris Zbarsky Andy Sledd Resolution: We clarified that load events are sent when nodes are added to the tree. |
|
SVGT12-494 [SVGMobile12] Question on handling of
<script> with xlink:href and child nodes Responses: Doug Schepers Boris Zbarsky Robin Berjon Boris Zbarsky Jim Ley Jim Ley Boris Zbarsky Doug Schepers Anne van Kesteren Doug Schepers Ian Hickson Doug Schepers Robin Berjon Bjoern Hoehrmann Anne van Kesteren Doug Schepers Boris Zbarsky Resolution: Added text to specify behavior. |
|
SVGT12-495 [SVGMobile12] Question on details of when <script> elements execute
Responses: Andy Sledd Boris Zbarsky Andrew Emmons Resolution: We clarified that we do not plan to standardize this since it would constrain implementations; some are synchronous and some are asynchronous. |
|
SVGT12-496 [SVGMobile12] SVG Mobile 1.2 redefines
semantics of XML Events attributes Responses: Robin Berjon Ian Hickson Dean Jackson Resolution: We will support XML Events on everything. Resolution: XML Events is now by reference. |
|
SVGT12-497 [SVGMobile12] issues with the uDOM's Element
Responses: Robin Berjon Resolution: DOM Core now by reference. |
|
SVGT12-498 [SVGMobile12] DOMException interface should
just reference the Core DOM Responses: Robin Berjon Resolution: DOM Core now by reference. |