I have the same question. Can you explain why text-overflow is insufficient? I think in this case it would be acceptable behavior to just make text-overflow behave the way you want, i.e., no longer showing the ellipsis while the user is actively typing in the focused control seems like fine behavior even for text-overflow.
dave ([email protected]) On Jan 13, 2012, at 2:45 PM, Ojan Vafai wrote: > Is this specced anywhere? Do we need a new CSS property? Could we just make > text-overflow work on text inputs? > > On Wed, Jan 11, 2012 at 11:30 PM, Jon Lee <[email protected]> wrote: > Hi WebKit! > > I wanted to let you know that we would like to add a new CSS property > -webkit-control-text-overflow. It is a non-inheritable property that can only > be applied to single-line text inputs. Acceptable values are the same as > text-overflow, i.e. "clip" and "ellipsis". > > When the input is set with the "ellipsis" value, both the placeholder and > inner text value of the input render with an ellipsis if the text overflows > and the input is not focused. When the input becomes focused, the placeholder > or text value renders clipped, as before. > > Although this is a small enhancement to text controls, we think this is > especially useful for authors developing on the mac platform, since the > analog native widgets behave similarly. > > The bug that tracks this is: https://bugs.webkit.org/show_bug.cgi?id=76118 > > Jon > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
