Brennan Young
My feedback
52 results found
-
5 votesUnder Review · 8 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment An error occurred while saving the comment Brennan Young
commented
Illustrator seems to wreck a lot of things when importing SVG, regardless of where it originated. Its habit of changing css, classnames etc. is infuriating.
I fully understand there are legacy reasons why this has happened, since Illustrator predates SVG, but it begins to look like poor strategy in the post Flash, responsive-design century.
Illustrator is currently a liability for the integrity of any SVG roundtrip work. It's fine for originating markup, but falls very short if that markup is going to be tweaked or manipulated by other tools.
Brennan Young
supported this idea
·
-
4 votes
An error occurred while saving the comment Brennan Young
commented
Thank you!
Brennan Young
shared this idea
·
-
2 votesBrennan Young
shared this idea
·
-
2 votes
An error occurred while saving the comment Brennan Young
commented
It's ugly behavior on the part of AI, especially without warning, but isn't reuse of IDs in the same namespace disallowed in XML/SVG?
The right thing for you to do is to ensure compliant markup, and the right thing for AI would be to warn about screwy input. -
17 votes
An error occurred while saving the comment Brennan Young
commented
This would be a compellingly useful improvement to the UI.
Add to / Remove from selection would get much of the way, but being able to combine 'Same...' criteria with checkboxes or some such would be extremely useful. Basically a Selection Filter editor.
Other useful selection criteria:
Locked
In Layers below
In Layers above
Wider than... / Narrower than (some value)
Taller than / Shorter than (some value)
Font size greater than... / less than...
Same Font
Bounding box / x,y outside artboard
x/y greater / less than (some value)
Overlaps objects/paths in current selectionBrennan Young
supported this idea
·
-
1 voteBrennan Young
shared this idea
·
-
1 vote
An error occurred while saving the comment Brennan Young
commented
I'm pretty sure spaces are not permitted in id names. If I understand your screenshots correctly, you are breaking this rule, no?
Also, it's worth pointing out that the current version of Illustrator chokes when importing id and class identifiers containing underscores.
-
3 votes
An error occurred while saving the comment Brennan Young
commented
More control over SVG export would be very, very welcome.
Brennan Young
supported this idea
·
-
3 votes
An error occurred while saving the comment Brennan Young
commented
Very good catch!
I encountered this problem too with class names. I just added a comment to my bug report mentioning yours. I am fairly sure this is a duplicate, although the symptoms are slightly different. Still, the title of your bug report is closer to the 'truth' of the matter.
What I caught (and missing from the report above) is that this issue pertains specifically to path elements. Not (e.g.) rect, circle, polygon... There might be other points of failure but certainly path import is borked here.
In one line, the issue appears to be: SVG import fails to import css rules for path elements with class/id identifiers containing underscores.
The good thing is, there's a workaround for today: Simply don't use underscores in class/id identifiers. But it's still Adobe's bug to fix.
FYI the title of my bug report is "Imported SVG path elements - always black fill".
Brennan Young
supported this idea
·
-
4 votes
An error occurred while saving the comment Brennan Young
commented
More info on this issue.
It seems to be because the class name I added manually has an underscore in it. I can confirm that Illustrator imports the fill correctly if I remove the underscore from the class name.
A possibly duplicate issue was reported by Gust van de Wal in November 2018 under the title "Underscores in SVG id attributes won't get their CSS styles applied". That issue refers only to Ids, but apparently this is a more general problem with CSS identifiers not being handled properly.
Brennan Young
shared this idea
·
-
36 votesBrennan Young
supported this idea
·
-
1 voteBrennan Young
shared this idea
·
This is encouraging, Dirk!
I understand the predicament here. As a low-hanging fruit, I suppose a warning alert ("Are you sure you want to trample onwards" with a "don't show this again" checkbox) might appear if you do something in AI which destroys some incompatible third-party structures.
"most-minimal-destructive" sounds great in the long term!