You can easily do inline editing in pure HTML, but how about enabling the same feature in SVG, and making it available on all major browsers?
Although pure SVG implementations like SVG Textbox exist, they can't be used on a iOS device because the textfield isn't recognized as an input text, so the keyboard doesn't show up.
Another alternative is to use the SVG foreignObject tag, which aims to add HTML element in a SVG, like an
<input> tag. But it's not compatible with Internet Explorer under the version 9.
The feature is already planned for implementation directly in SVG, see the SVG text editing draft specification: Text editing SVG 1.2.
When looking for a library that allows to manipulate SVG elements in the browser, the first one that pop directly is Raphael.js. It's also the most easy to use.
Raphaël.js implements W3C's current recommendation of SVG, which is currently in version 1.1. So there is no way to get the native SVG text editing feature directly in Raphaël.js.
So it must be emulated...
The solution is simple: Add an
<input> text field on top of the SVG. This allows to edit the text on mobile device and is compatible with Internet Explorer.
The tricky part is to report the SVG transformations on the input element.
The Raphael.fn method object provides a way to add custom methods that can be called on the
It allows to make a new
inlineTextEditing() method to turn any SVG
<text> element into an editable text, as follows:
Let's get started. First, we initialize the new method, taking an SVG text element as parameter:
Next, we have to retrieve the transformations (rotation / translation & scale) of the text element. This is done thanks to the '_' property of the Raphael element (an undocumented property which has nothing to do with the underscorejs library).
This property returns the rotation and the scale of the element. To retrieve the translation we have to parse each transformation to point out the one that begin by a 't'.
The Element.Transform method can take a matrix parameter, as follows:
r to represents the scale, translation or rotation. Just a
m that is the combination of all of theses.
In this case there is no informations in the '_' attribute, we have to parse the transformations in search of a
For more informations about transform matrix, check out Matthew Bystedt's blog post.
The textfield is positioned by the CSS
transform property and the CSS
Raphael uses the center by default to rotate or scale an element so we set the
The translation is directly added to the original position of the element (
Then we build the
transform property. It should take the same transform order than the SVG element. That's because a scale followed by a rotation on an element don't give the same result as a rotation followed by a scale.
We can now append the textfield to the container of Raphael's paper and hide the text element.
stopEditing method in the plugin allows the user to :
After 2 days working on this plugin we have set up a todo list :
You're welcome if you want to give us a hand!