Bug Report: Leading

  • 2
  • Problem
  • Updated 11 months ago
Merged

This conversation has been merged. Please reference the main conversation: Photoshop CC 2018: Character leading broken

Good afternoon,

After upgrading to Adobe Photoshop CC 2018, I have discovered a bug when adjusting "leading" through the Character panel. When I enter a value into the "leading" field, it changes to a value I did not enter. When I try to scrub or use the up/down arrow keys, the value only changes in one direction and with a large jump in value. I have discovered that this occurs after transforming the text layer.

Any advice on how to fix this?
Photo of Jose Garza

Jose Garza

  • 1 Post
  • 0 Reply Likes

Posted 11 months ago

  • 2
Photo of David

David, Official Rep

  • 2800 Posts
  • 387 Reply Likes
Howdy Jose,

The problem is related to transforming your text.  If you work with untransformed text, the problem should go away.  Not ideal, but a workaround until we can get a fix out to customers.

Sorry for the inconvenience.  You can read all the details here: https://feedback.photoshop.com/photoshop_family/topics/character-leading-in-photoshop-cc-2018-broken

Thanks,
David
Photo of Jaroslav Bereza

Jaroslav Bereza

  • 781 Posts
  • 166 Reply Likes
I don't understand why this is not fixed? This has several duplicites in bug tracker and this was reported before public release. Is it hard to fix it? I thought that somebody only confused "leading" property with "intended leading" property which differs for transformed text layers. Or is it more complicated?
Bug ID - PS-11154 ; Bug ID - PS-11749 ; Bug ID - PS-11748
Photo of David

David, Official Rep

  • 2800 Posts
  • 387 Reply Likes
Hey Jaroslav,

If you check those bugs, you'll see that the second two were logged AFTER we shipped.  The first one came in right about when the code got locked down, but as I noted in that bug, we didn't get the final steps to repro until the day we went RC and it is part of a larger issue that needs to be fixed with enough time to ensure there are no "accidental side effects" (i.e., it was a little complicated).  We didn't realize the full severity of the bug until Wednesday, about 11am PST, when those second two you mentioned were found...

David
Photo of Jaroslav Bereza

Jaroslav Bereza

  • 781 Posts
  • 166 Reply Likes
Ok thanks a lot for explanation :-)
Photo of David Chapman

David Chapman

  • 4 Posts
  • 2 Reply Likes
I logged the bug on Oct 7 and no one looked at it until the day of launch. I even provided a screen recording and exact details about what was going on.

This conversation is no longer open for comments or replies.