View Single Post
Old 03-07-2016, 10:46 AM   #26
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi Psymon,
That is not consistent with what Bertrand reported. I assumed you were both talking about the same warning. If you remember, I did ask you earlier if you had anchors in your file to try and rule that out.

So these are caused by normal html anchors pointing to an svg external image file? Or is it an anchor pointing toward an html location just before or after the svg embedded in html? Or is it an img tag pointing to an external svg image file?

The problem is in none of these cases would an xlink:title attribute be appropriate. It is really only appropriate in standalone svg file, and svg embedded inside xhtml or svg image tag.

I will look again at your code when I get back from work to see if I can figure out what is really going on. The warning you are getting just makes no sense if adding xlink:title to the svg image tag does not prevent the warning.

KevinH
KevinH is online now   Reply With Quote