jessyInk* attributes should be in a custom namespace

Bug #353818 reported by Erik Dahlström
4
Affects Status Importance Assigned to Milestone
JessyInk
Fix Released
Medium
Hannes Hochreiner

Bug Description

It would be better if JessyInk could put all its custom attributes in a custom namespace, as described here:

http://www.w3.org/TR/SVGTiny12/extend.html#ForeignNamespacesPrivateData

In particular "Unprefixed attributes on elements in the SVG namespace must not be used for extensions."

Related branches

Changed in jessyink:
assignee: nobody → hannes-hochreiner
status: New → Confirmed
Revision history for this message
Hannes Hochreiner (hannes-hochreiner) wrote :

Thanks for the reminder. Actually, I tried to do that when I started out writing JessyInk. However, at the moment, it would make the JessyInk installation in Inkscape harder. Please see also the linked blueprint. I agree that this is an important point and I will continue to look into it.

Changed in jessyink:
importance: Undecided → Medium
Revision history for this message
Hannes Hochreiner (hannes-hochreiner) wrote :

Ok, I checked the issue again with the new scripts using the "inkex.py" script and apparently it work. If an attribute with a namespace is introduced, the namespace is correctly transfered into the SVG file that's used by Inkscape. Just have to check to JavaScript side of things still.

Changed in jessyink:
milestone: none → 1.1.0
Changed in jessyink:
status: Confirmed → In Progress
Changed in jessyink:
status: In Progress → Fix Committed
Changed in jessyink:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.