RESOLVED FIXED 53242
Web Inspector: [STYLES] Cancelled suggestion of a property name results in a visual artifact
https://bugs.webkit.org/show_bug.cgi?id=53242
Summary Web Inspector: [STYLES] Cancelled suggestion of a property name results in a ...
Alexander Pavlov (apavlov)
Reported 2011-01-27 08:45:57 PST
1. Double-click a property name (e.g. "color") and type in some other name prefix, e.g. "bo". "border" is suggested 2. Press Esc to cancel the property rename. As a result, "bocolor" remains in place of the property name ("bo" in black color). Another double-click + Esc fixes the display (the actual property name is not affected by the issue).
Attachments
[PATCH] Suggested fix (1.76 KB, patch)
2011-01-27 08:54 PST, Alexander Pavlov (apavlov)
no flags
[PATCH] Comment addressed (2.49 KB, patch)
2011-01-27 09:32 PST, Alexander Pavlov (apavlov)
no flags
Alexander Pavlov (apavlov)
Comment 1 2011-01-27 08:54:36 PST
Created attachment 80335 [details] [PATCH] Suggested fix
Yury Semikhatsky
Comment 2 2011-01-27 09:17:25 PST
Comment on attachment 80335 [details] [PATCH] Suggested fix View in context: https://bugs.webkit.org/attachment.cgi?id=80335&action=review > Source/WebCore/inspector/front-end/StylesSidebarPane.js:1727 > + this._prompt.removeFromElement(); I don't quite understand why we detach the prompt from its parent here and don't do this on commit, can you explain this?
Alexander Pavlov (apavlov)
Comment 3 2011-01-27 09:32:11 PST
Created attachment 80341 [details] [PATCH] Comment addressed You are correct, this removal should be invoked in all cases. Fixed.
WebKit Commit Bot
Comment 4 2011-01-27 20:14:50 PST
Comment on attachment 80341 [details] [PATCH] Comment addressed Clearing flags on attachment: 80341 Committed r76913: <http://trac.webkit.org/changeset/76913>
WebKit Commit Bot
Comment 5 2011-01-27 20:14:54 PST
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 6 2011-01-27 22:01:36 PST
http://trac.webkit.org/changeset/76913 might have broken Leopard Intel Release (Tests)
Note You need to log in before you can comment on or make changes to this bug.