Tested the issue on 62.0.3202.18 using Ubuntu 14.04 and is not reproducible with below steps.

1.Opened devtools and opned html file. Added breakpoint.
2.Collapsed call stack panel, now used step over next function call button. Callstack panel is seen collapsed for every step over function.

Attaching video for reference.

@Reporter: Could you please let us know whether we are missing anything in steps? and could you check whether you are able to reproduce this issue on latest canary?

Deleted: Issue 766086.ogv 1.4 MB

	Issue 766086.ogv 1.4 MB View Download

@sc00335 The only release channels available for Linux are Stable, Beta and Dev.

But following your steps, I also couldn't reproduce this. Here's how you can reproduce it.

1. Start a node.js 6.x application with "node --inspect ."
2. Open about://inspect in Chromium
3. Select "inspect" on Remote Target #LOCALHOST
4. Open "sources" set a breakpoint on some code that will be executed
5. Wait for the breakpoint to hit
6. Collapse the "Call Stack"
7. Step into
8. Observe Call Stack being open again

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

For your convenience, here's how to quickly set this up:

Create a file (index.js) with the following content:

'use strict'
let http = require('http')
http.createServer((req, res) => {
  console.log('Incoming request.')
  res.writeHead(200, {'Content-Type': 'text/plain'})
  res.write('Hello World!')
  res.end()
}).listen(8080)

* Bash: Run: "node --inspect index.js"

You will see something like this:

To start debugging, open the following URL in Chrome:
    chrome-devtools://devtools/remote/serve_file/...

Bash: Copy the uri
Chromium: Open the uri
Chromium: Press Ctrl + P
Chromium: Type "index.js"
Chromium: Put breakpoint on the console.log line
Bash (new session): curl localhost:8080
Chromium devtools will take focus when the breakpoint is hit
Chromium: Collapse Call Stack
Chromium: Step over
Chromium: Observe Call Stack open again.

Tested the issue on 62.0.3202.18 using Ubuntu 14.04 and is not reproducible with below steps.

1. Created a file with given content
2. Started a node.js 6.x application with ""node --inspect .""
3. Opened about://inspect in Chrome
4.Given the break point on console log
5.Collapsed Call Stack
6.Performed Step over. Callstack panel is seen collapsed for every step over function.


@Reporter - Could you please verify the screen cast and please let us know if anything missed from our side.

Deleted: 766086.ogv 2.0 MB

	766086.ogv 2.0 MB View Download

@Keerthan I'm using google-chrome-beta 62.0.3202.29 for recent tests. Is this okay, or do I absolutely need to test this with Chromium in stead of Chrome?

If the latter, can you tell me how to get a recent build of Chromium on Ubuntu 16.04 first?

Thank you for providing more feedback. Adding requester "keerthana.v@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@keerthana in the video you're not going to the inspect tab, you're just opening the dev tools while on a new tab. The start page is still visible. The webcontent under Sources > Top should not be visible.

You need to go literally go to chrome://inspect/#devices and connect to a remote target.

Deleted: Screenshot from 2017-09-22 14-30-19.png 87.2 KB

	Screenshot from 2017-09-22 14-30-19.png 87.2 KB View Download

Deleted: Screenshot from 2017-09-22 14-33-35.png 214 KB

	Screenshot from 2017-09-22 14-33-35.png 214 KB View Download

 Issue 768257  has been merged into this issue.

Node v6 points you to an old version of the DevTools front end to ensure compatibility. You can click "Open dedicated DevTools for Node" on chrome://inspect to use the newest version of DevTools with the older version of node.