New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 781927 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug



Sign in to add a comment

[MD extensions] expand/collapse button not working in errors list

Project Member Reported by dschuyler@chromium.org, Nov 6 2017

Issue description

In the MD extensions errors page for an extension, the cr-expand-button elements are not responding to clicks.
 
Project Member

Comment 2 by bugdroid1@chromium.org, Nov 7 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/978f3c4fb8e40a697b9d83736f127287114f9af2

commit 978f3c4fb8e40a697b9d83736f127287114f9af2
Author: Dave Schuyler <dschuyler@chromium.org>
Date: Tue Nov 07 03:30:19 2017

[MD extensions] improve error selection and expand/collapse

This CL improves the error selection and expand/collapse functionality.
Though there are further improvements I intend to make, this is a step
forward.

Bug:  781927 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: If223f1d80ee5d92dee0f8a53be31f2806424d26d
Reviewed-on: https://chromium-review.googlesource.com/755481
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514375}
[modify] https://crrev.com/978f3c4fb8e40a697b9d83736f127287114f9af2/chrome/browser/resources/md_extensions/error_page.html
[modify] https://crrev.com/978f3c4fb8e40a697b9d83736f127287114f9af2/chrome/browser/resources/md_extensions/error_page.js

Status: Fixed (was: Started)
Created  issue 782340  to follow up on further improvement ideas.
Labels: Needs-Feedback
dschuyler@ Can you please provide the steps to verify this issue at TE end.

Thanks...
@ #4, It is confusing. For that reason this UI is changing again. Please see  Issue 782340 . I've written a description of how that UI will work. That change should land soon. Testing the fix in that Issue should cover both of these issues imo.

Sign in to add a comment