#100 ✓resolved
Nick Takayama

CPTextField setStringValue: behaves strangely when CPTextField is firstResponder

Reported by Nick Takayama | October 9th, 2008 @ 04:36 PM

A CPTextField that is editable will render both old and new values over the top of eachother when a user is editing it and some code calls to [_textField setStringValue:].

This is because the setStringValue: method does not take the DOM input element into account when re-rendering.

I've attached a git email formatted patch for this, which is just 7 lines of code.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

The Cappuccino Web Framework, including AppKit, Foundation, and Objective-J.

Shared Ticket Bins

People watching this ticket


Referenced by