Jeremy > bringing up a tiddler instead of a different viewbox of the svg. > > No, TW will still detect the change to the document fragment and respond > accordingly. >
Understandable-- necessary for TW's tiddler navigation (using the #anchor) > Or the svg <a> tag not appling target attribute (which I assume is a > shadow DOM issue) > > I’m not familiar with that problem, can you elaborate? > When targetting an iframe from a svg <a> with target attribute, it opens a second instance of the entire wiki inside the iframe instead of just the tiddler that is the href. Attached is a json with a test tiddler & 2 support tiddlers, the circles of the svg are the links, the last 2 targetting iframes (1 in the same tiddler as the svg, the other is another tiddler, whhich has to be open in the story river along with the test tiddler) > I don't know if my breaking svg's into different element tiddler to be > transcluded into a svg shell is what you previously meant by primitives but > I can now assemble custom layered svg maps picking and choosing from a > "master library" of over 100 layer/element tiddlers by just setting fields > of the shell svg tiddler and not needing js. > > Cool stuff, looks good. > The only problem with transcluding elements into a svg shell- Chrome doesin't seem to like it-- with the animation demo, http://pyewackit.net/ash/empty1.html , I had someone tell me Chrome (Mac & PC) wouldn't show the svg animations triggered by button clicks. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/845f439d-5e1a-42f2-9002-5d39e26c3982%40googlegroups.com.
svgatargettesting.json
Description: application/json
