Planet SVG
  • Home
  • Blog
  • News
  • Forums
Home • Forums • Best Practices
 

User login

What is OpenID?
  • Log in using OpenID
  • Cancel OpenID login
  • Request new password

Recent blog posts

  • Sketsa SVG Editor 6.4 Released
  • Animated map of the Gulf of Mexico Oil Spill, made with SVG
  • Mappetizer 8.2 for ArcGIS Released
  • SVG Open in Paris; put the Eiffel-towered banners on your site !!
  • IE9 will support SVG !! (preview available)
  • Microsoft and W3C co-present about SVG at MIX conference
  • Microsoft joins SVG working group
  • How to make impact with your design
  • Jumping in to SVG
  • Sketsa SVG Editor 6.2.2 Released
more

<title> and <desc>

July 31, 2008 - 12:16pm by Shepazu

I'm interested in feedback on what the content model for title and description elements should be... any thoughts? I'm thinking it should be text or structured markup, like RDF. What should browsers do with the information?

  • Best Practices

#1 I dimly remember discussions

Submitted by Jeff on July 31, 2008 - 3:52pm.

I dimly remember discussions in the SVG WG mailing list regarding this - I believe at the time that Chris Lilley felt the spec should not specify the content, markup language, etc. In other words, leave it up to UAs, I guess.

Are you talking about changing the spec or guidelines on what browsers should support?

As to what browsers should do, well - tooltip for title (as is currently implemented) works fine. For visual browsers, I guess desc elements can be just 'ignored' (i.e. not shown) since the contents of the desc element are intended to be a textual replacement for the parent element.

 
Powered by Drupal, an open source content management system