Skip to content

Daniel

← Adobe Illustrator

My feedback

1 result found

  1. Properties panel fields don’t accept numeric input until focus resets (MacBook Pro, Illustrator 2025, macOS Sequoia 15.5)

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Illustrator (Desktop) Bugs » Properties Panel  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Daniel commented  · 

    No, I cannot, and here’s why: When the bug appeared on my Mac OS15, it was ongoing through a couple of restarts. ChatGPT 5 suggested it was a known issue, and that nothing I could do would fix it. Though I should know better, I believed it. I copyandpasted Chat’s text and posted it here. Now, after dumping Illustrator prefs and another restart, the issue has disappeared.

    So, apologies to the group, along with relief that AGI is not here yet.

    An error occurred while saving the comment
    Daniel commented  · 

    Reporting a UI regression in Illustrator 30.1 affecting numeric input fields.

    Issue
    In fields such as Stroke Width (Properties panel) and others, cannot type numeric values directly like we used to.

    * Arrow keys and scrubby dragging work
    * Typed input is ignored (caret often never appears)
    * This makes precise values (e.g., 240 pt) extremely impractical

    Environment
    * Illustrator version: 30.1
    * OS: (macOS / Windows – occurs on both, per community reports)
    * Panel affected most often: Properties (Stroke, Transform, etc.)

    Notes
    * The former **“Scrubby Sliders” preference appears removed or always-on**
    * The issue behaves like a **focus/caret bug**, not user error
    * Using Cmd+A then typing, or pasting values, works as a workaround
    * Stroke panel is less affected than Properties panel
    * Disabling GPU Performance reduces frequency but does not resolve the issue

    Expected behavior
    Numeric fields should reliably accept typed input when clicked, as in previous versions.

    Impact
    This slows professional workflows and precision design tasks.

    Would love to have type-in fields back in 30.2. But I’m sure I’ll survive either way.

    Thanks.

    Daniel supported this idea  ·