W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2009

[Bug 3031] The Built-in Datatype Hierarchy diagram

From: <bugzilla@wiggum.w3.org>
Date: Sat, 24 Jan 2009 22:11:37 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1LQqj3-0000Ee-Lw@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3031


C. M. Sperberg-McQueen <cmsmcq@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
           Keywords|                            |resolved
         Resolution|                            |FIXED




--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@w3.org>  2009-01-24 22:11:37 ---
Further investigation shows that there was indeed a related bug in Firefox 
(https://bugzilla.mozilla.org/show_bug.cgi?id=300868), which has now 
been fixed.  What remains may be an irritating or confusing difference
among browsers in the handling of SVG, but not a bug.

When external SVG images are embedded using the 'object' element, Firefox 
treats the display of the SVG as constituting a separate frame.  Traversal
of hyperlinks within such a frame follows the usual rules for frames:  the
target of the link is displayed within that frame, without affecting the
display or content of other frames, unless the hyperlink has a 'target'
attribute.  Adding 'target="_parent"' to the links within the SVG image
causes the target of the hyperlink to be displayed not within the frame
containing the SVG image, but within its parent (the one containing the
display of the XSD spec), which yields the expected behavior.

The addition of target="_parent" appears to have no effect on other browsers 
tested (Opera, Safari, IE) when they are displaying the XSD spec in their
main window.  I assume that if they are displaying the XSD spec in a frame
(e.g. with commentary in another frame), then this addition will wreak 
havoc on the frameset.  But I have not verified this assumption; even if it's
true, the tradeoff between making normal display work in Firefox on the one
hand, and causing minor problems for eventual future framed displays on
the other, is a clear one.

The change has been made both in the new SVG diagram drawn to resolve
bug 2687 and in the old one (now deleted), in the copies of the spec
at 

  http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.html
  (member-only link)

etc.

Andrew, if you would verify that the bug has been fixed, and report the
fact to the XML Query and XSL WGs, we would be grateful.  Close the issue
to signal that you and they are satisfied by the resolution of the issue,
and reopen it otherwise.  If we don't hear from you in the next two weeks,
we'll assume you and they are satisfied.  Thank you.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 24 January 2009 22:11:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:09 UTC