Translate Ideas and Comments
Choose language:
There was an error during translation

Brennan Young

My feedback

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Illustrator (Desktop) Feature Requests » Other...  ·  Flag idea as inappropriate…  ·  Admin →
    Brennan Young shared this idea  · 
  2. 613 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    I find it astonishing that anyone can imagine File Versioning could be a viable replacement for Undo History. Versioning and Undo History serve similar goals, but at very different levels.

    Versioning is at a higher level of organisation. It's certainly a useful 'import' from the software development world.

    But even software developers (who have pioneered and used versioning for many years) don't commit every single keystroke, clipboard operation and micro edit to the version history. Versioning was not created to solve that problem. Software developers still rely on the undo buffer just as much as Illustrator users. Versioning didn't make it obsolete.

    Furthermore, a 'commit' should preferably be relatively stable, so that others can pull it and try it out immediately. Devs who make too many commits of micro edits quickly become unpopular! If I wanted to find an old version of a graphic in the history, I'd be utterly dismayed to find that history polluted with dozens of near-identical micro edits. Don't do that. Be a good citizen. Consider that it might be you that has to trawl through your own version history in six months.

    Let Undo History handle the low-level edits. Let File Versioning handle the high-level edits.

    So, if it's not already loud and clear, we still need the Undo History panel, Adobe.

    Brennan Young supported this idea  · 
  3. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    Layer does not have a selected property in the object model, but there is "has selected artwork" which might work for you.

    You can use a filter reference form (a "whose" clause) to get all the layers with selected artwork. Example:

    tell application "Adobe Illustrator"
    layers of document 1 whose has selected artwork is true
    end tell

    Brennan Young supported this idea  · 
  4. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    SVG export should convert symbols to <use> elements.

  5. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Brennan Young supported this idea  · 
  6. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    Completely agree with Tim Kelly - it's a significant shortcoming not to support <title> and <description>, but regarding accessibility, I would love to see a way to work with aria roles, tabindexes and accessible names (such as aria-label). A more generally useful approach would be for the Illustrator GUI to support the full range of SVG attributes (including aria).

    An error occurred while saving the comment
    Brennan Young commented  · 

    If I could click the vote button for Edu Couchez' well-considered proposals, I would.

    Brennan Young supported this idea  · 
  7. 122 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Started  ·  Dirk Schulze responded

    Just a general status update. We are currently and will continuously improve SVG import support in Adobe Illustrator. We are currently working on solving the issues mentioned in this report. Please feel free to open new bug reports here on uservoice if you are experiencing additional/untracked issues.

    An error occurred while saving the comment
    Brennan Young commented  · 

    Regarding the use of AI as a dedicated SVG editor, and the possible compromises for other AI features, I would draw attention to the way that Photoshop can operate in various color modes (e.g CMYK, grayscale, RGB...) and in each mode, various editing features are disabled, or modified.

    Crucially, if you open an image with a CLUT, Photoshop puts the GUI into indexed color mode automagically. When opening certain file types, Photoshop even asks the user to clarify how the image should be handled.

    I know SVG-in-AI is a little different, but my point is that the idea that the GUI can be in a format-specific editing mode is already a precedent which graphics professionals (and creative cloud users) will be familiar with, so it need not be a huge paradigm shift

    Perhaps a way to constrain the illustrator UI to SVG-native features would help? e.g. if you open a SVG, you're in SVG mode, or perhaps you check a 'SVG mode' checkbox somewhere, then if you try to apply a non-SVG feature AI warns that it may not turn out as expected unless you save as an AI file. Something like that.

    Brennan Young supported this idea  · 
  8. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    fillColor and strokeColor sorely missing. These are extremely important. Also graphic styles.

    Brennan Young supported this idea  · 
  9. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    Hi Dirk,

    I ran into this issue trying to make a (flattened) hexagon shape with rounded corners, which could be scaled without changing the stroke width. The 'points' of the hexagon were at the sides.

    Can't really see how border-image-slice would help with this, or any shape which is not basically a rectangle.

    Brennan Young shared this idea  · 
  10. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    Hi Dirk,

    As long as the renaming on export is consistent, and predictable, so that when you roundtrip, it doesn't re-encode its own output from the previous export, and so that we have a fighting chance of constructing an id or class identifier algorithmically, then the renaming on export is ok.

    I do wonder why 'special' characters are converted to numerical entities. If the exported SVG is tagged as having a utf-8 charset (which it is, if you use Save As... SVG), the only truly forbidden characters are <, >, &, ' and ". All other characters might well be represented in their literal form. No? Some fine-grained control over this behavior would be welcome.

    An error occurred while saving the comment
    Brennan Young commented  · 

    Hi Dirk,

    Yes, I've tried using Graphic Styles and yes, they get exported, and yes this is a good start. But the renaming is infuriating.
    But we will certainly want to use the same class name on things with *different* graphic styles - or different kinds of drawing object (e.g. text).

    An error occurred while saving the comment
    Brennan Young commented  · 

    So compellingly useful, it's astounding that this is not implemented yet.

    Also: when importing SVG, Illustrator should not rename the class and id attributes because there might be scripts that depend on those specific names. Current behavior makes roundtrip editing of SVG very impractical.

    Brennan Young supported this idea  · 
  11. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    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!

    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  · 
  12. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Started  ·  4 comments  ·  Illustrator (Desktop) Feature Requests » Other...  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Brennan Young commented  · 

    Thank you!

    Brennan Young shared this idea  · 
  13. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Brennan Young shared this idea  · 
  14. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

  15. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Brennan Young shared this idea  · 
  16. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Brennan Young commented  · 

    Using AI (CC early 2019)

    I notice that graphic style names make it to the CSS in the exported SVG (great!) whereas paragraph and character style names do not. (Boo!) Infuriating! Everything is changed to st1, st2... etc.

    Use cases: Scripting SVG or using external css files depend on a minimal level of predictability about what identifiers appear in the markup which is just not there right now.

    If I want several related/similar SVG files to use the same script or css, I can't be sure that the class name that AI generates will match the same class of element in each case.

    "st4" might point to the main heading in one SVG, but might point to a minor tspan in some other SVG, depending (I suppose) on how many distinct styles appear in each individual document, the exact layer order, and various other arbitrary influences. This isn't how 'styles' are supposed to work.

    Just use the identifier given in the UI for paragraph and character styles, if it's been specified, please!

    Related: Shouldn't paragraph styles be applied to <text> elements, whereas character styles should be applied to <tspan> elements?

    Brennan Young supported this idea  · 
  17. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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 selection

    Brennan Young supported this idea  · 
  18. 52 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi Everyone,

    Thanks for the feedback. The color yellow has been removed altogether as a layer color, and has been replaced by Magenta color for Layer 5. This functionality is available in our latest release build – 24.1.1 for Win and 24.1 for Mac which is available worldwide now.

    What’s new in 24.1: https://helpx.adobe.com/illustrator/using/whats-new.html

    You can update to the latest release using Creative Cloud desktop App: https://helpx.adobe.com/in/creative-cloud/help/creative-cloud-updates.html

    Thank you for all the feedback.

    Brennan Young supported this idea  · 
  19. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Illustrator (Desktop) Bugs » User Interface  ·  Flag idea as inappropriate…  ·  Admin →
    Brennan Young shared this idea  · 
  20. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

← Previous 1

Feedback and Knowledge Base