MD Extensions: Error Console: Lots of scrolling is needed with many extension errors |
||
Issue descriptionWhat steps will reproduce the problem? 1. Enable Dev Mode 2. Load attached extension 3. Notice the code snippet is on top and errors are on the bottom, so examining errors on the bottom becomes harder as the number of errors grows What is the expected result? Examining an error should be easy What happens instead of that? Examining an error gets harder at a rate of O(n) because of scrolling after a certain point.
,
Jan 19 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/501d93e2ee023017c8b519961b9d6c991b04cc43 commit 501d93e2ee023017c8b519961b9d6c991b04cc43 Author: Hector Carmona <hcarmona@chromium.org> Date: Fri Jan 19 00:23:31 2018 MD Extensions: Error Console: Move code section closer to stack trace. This will make the code/error association very explicit by keeping the code snippet near the stack trace inside the error that is being investigated. See bug for screenshots/video. Bug: 800994 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I7a781bd304b498edf2a5b19d58635824a54a575b Reviewed-on: https://chromium-review.googlesource.com/861915 Commit-Queue: Hector Carmona <hcarmona@chromium.org> Reviewed-by: Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#530354} [modify] https://crrev.com/501d93e2ee023017c8b519961b9d6c991b04cc43/chrome/browser/resources/md_extensions/error_page.html [modify] https://crrev.com/501d93e2ee023017c8b519961b9d6c991b04cc43/chrome/browser/resources/md_extensions/error_page.js [modify] https://crrev.com/501d93e2ee023017c8b519961b9d6c991b04cc43/chrome/test/data/webui/extensions/a11y/extensions_a11y_test.js [modify] https://crrev.com/501d93e2ee023017c8b519961b9d6c991b04cc43/chrome/test/data/webui/extensions/extension_error_page_test.js
,
Jan 19 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by hcarmona@chromium.org
, Jan 11 20182.6 KB
2.6 KB Download