Bug/render nodes

[simontegg]

Not ready to merge. This renders svg 's by monkey patching React.DOM and SVGDOMPropertyConfig.Properties.

[simontegg]

Ok fixed. I'll tidy this up, rebase and add some tests, but a look over is appreciated

[ahdinosaur]

such hacks :fireworks:, but if it works then that's great and looks good to me. also if you're based on master there's no reason to rebase, my mad science refactor-api branch is in the stars right now. moving forward, i recommend we link up by each writing tests for our modules' desired interface.

[simontegg]

@ahdinosaur Ok should be ready. Tests are token though.

[ahdinosaur]

hmm, i'm only seeing a blank screen on firefox and a mostly blank screen with arrows floating around on chrome.

[simontegg]

check console. Are they <img>'s or <image>'s ?

[simontegg]

I'm getting arrowheads + square images on firefox (no lines, no css clip: circle()

[ahdinosaur]

<img>s. have you changed anything in your local react install that might separate yours from mine?

[simontegg]

Yeah its in getMarkupWrap.js. Need a little more jigging

[simontegg]

patching done. Now fixing tests.

[simontegg]

@ahdinosaur ok looking better now

[ahdinosaur]

looks good to me, sans some minor nitpicks. :palm_tree:

[ahdinosaur]

here's how it looks to me in firefox 35.0.1:

[ahdinosaur]

also the amount of hacks you've had to go through to get this to work is astounding, kudos to you @simontegg. :smile_cat:

[simontegg]

My firefox is showing the arrowheads and `marker-end?

Seems firefox doesn't support css clip-path: circle(). I feel like that's a separate bug :)

[simontegg]

I reckon this can be merged. I can do the firefox issues as a separate bug.

[ahdinosaur]

k cool, i'll merge it up, @simontegg can you file the issues?

[ahdinosaur]

deployed :tada: