RESOLVED FIXED51114
Web Inspector: Up/Down/PageUp/PageDown on a CSS property numeric value commit the value editor
https://bugs.webkit.org/show_bug.cgi?id=51114
Summary Web Inspector: Up/Down/PageUp/PageDown on a CSS property numeric value commit...
Alexander Pavlov (apavlov)
Reported 2010-12-15 09:46:07 PST
[Page]Up/Down should not commit a CSS property value altogether but instead apply it to the style and continue editing. Patch to follow
Attachments
[PATCH] Suggested fix (2.92 KB, patch)
2010-12-15 10:06 PST, Alexander Pavlov (apavlov)
no flags
[PATCH] Fix reimplemented correctly (1.99 KB, patch)
2010-12-15 10:32 PST, Alexander Pavlov (apavlov)
eric: review-
[PATCH] Test added (5.71 KB, patch)
2010-12-16 05:00 PST, Alexander Pavlov (apavlov)
pfeldman: review+
Alexander Pavlov (apavlov)
Comment 1 2010-12-15 10:06:35 PST
Created attachment 76660 [details] [PATCH] Suggested fix
Yury Semikhatsky
Comment 2 2010-12-15 10:11:55 PST
Comment on attachment 76660 [details] [PATCH] Suggested fix View in context: https://bugs.webkit.org/attachment.cgi?id=76660&action=review > WebCore/inspector/front-end/ElementsPanel.js:-89 > - this.sidebarPanes.styles.addEventListener("style property toggled", this._stylesPaneEdited, this); _stylesPaneEdited is now only called from _styleSheetChanged, please get rid of _stylesPaneEdited
Alexander Pavlov (apavlov)
Comment 3 2010-12-15 10:32:41 PST
Created attachment 76665 [details] [PATCH] Fix reimplemented correctly pfeldman@ has explained the idea behind the event handling. This patch reverts the erroneous fix from r74038 and augments the stylesheet onRevert handling
Eric Seidel (no email)
Comment 4 2010-12-15 15:25:54 PST
Comment on attachment 76665 [details] [PATCH] Fix reimplemented correctly How do we test this?
Alexander Pavlov (apavlov)
Comment 5 2010-12-16 05:00:19 PST
Created attachment 76751 [details] [PATCH] Test added
Pavel Feldman
Comment 6 2010-12-16 05:12:32 PST
(In reply to comment #4) > (From update of attachment 76665 [details]) > How do we test this? Eric, could you please not blindly r- inspector changes that are missing tests without meaningful review comments? They go away from my to review report and this slows down the development. If you are willing to help us with the testing, as you know, inspector tests became flaky at some point and something in the harness needs to be fixed. I already had similar discussion with Adam the other day.
Alexander Pavlov (apavlov)
Comment 7 2010-12-16 06:10:25 PST
Committing to http://svn.webkit.org/repository/webkit/trunk ... M LayoutTests/ChangeLog M LayoutTests/inspector/styles-add-blank-property-expected.txt M LayoutTests/inspector/styles-add-blank-property.html M WebCore/ChangeLog M WebCore/inspector/front-end/ElementsPanel.js Committed r74185
WebKit Review Bot
Comment 8 2010-12-16 15:38:27 PST
http://trac.webkit.org/changeset/74185 might have broken Leopard Intel Debug (Tests)
Note You need to log in before you can comment on or make changes to this bug.