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

Issue 837145 link

Starred by 15 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Remote Debugging is missing 'Select Element Button'

Reported by dev.xfo...@gmail.com, Apr 26 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36

Steps to reproduce the problem:
1. Start chrome with remote debugging --remote-debugging-port=12345
2. Open localhost:12345 in chrome
3. Open one of the pages listed there

What is the expected behavior?
After following those steps I expect to see the remote dev tools I used to get in earlier versions including the select element button.

What went wrong?
The 'Select Element' button fails to appear.
After some initial debugging, it looks like it can't load screencast/screencast_module.js
As this fails in a subsequent call where the dev tools expect to find a ToolbarButtonProvider this does not exists as from what I can tell this is provided by the screencast code.

Did this work before? Yes 65.0.3325.230

Chrome version: 66.0.3359.117  Channel: stable
OS Version: 10.0
Flash Version:
 
chrome_remote_dev_tools.png
28.5 KB View Download
Labels: Needs-Bisect Needs-Triage-M66
Cc: sindhu.chelamcherla@chromium.org manoranj...@chromium.org
Labels: -Pri-2 -Needs-Bisect hasbisect-per-revision ReleaseBlock-Stable Triaged-ET M-66 FoundIn-66 Target-66 RegressedIn-66 OS-Linux OS-Mac Pri-1
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on reported version 66.0.3359.117 but issue is not seen on latest dev 67.0.3396.18	and latest canary 68.0.3409.0 using Mac 10.13.3, Windows 10 and Ubuntu 17.10. Hence providing reverse bisect info.

Last Bad Build: 67.0.3368.0
First Good Build: 67.0.3369.0

You are probably looking for a change made after 542655 (known good), but no later than 542656 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/94d037e89e0435217f58cb9a9ec4bcbfbef6265f..9018df6a298464edb9f50e10fd61f10222df23a5

Probably fixed by https://chromium-review.googlesource.com/953144.

@pfeldman: Please confirm the bug and help in re-assigning if this is not related to your change. Please merge to M-66 if this is safe. Adding RB-Stable for M-66. Please remove if not the case.

Thanks!



Labels: -ReleaseBlock-Stable
Status: Fixed (was: Assigned)
Fixed in M67, not a blocker.
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
Labels: -M-66 -Target-66 Target-67 M-67
Labels: -Merge-TBD
Removing "Merge-TBD" label per comment #3 and #5.

Sign in to add a comment