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

Issue 673623 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression

Blocking:
issue 238804



Sign in to add a comment

Chrome.processes API doesn't available on dev channel

Reported by garyy...@kkstream.com.tw, Dec 13 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2946.0 Safari/537.36

Steps to reproduce the problem:
Execute chrome.processes.* api on extension's event page with Chrome Version 57.0.2946.0 (Official Build) dev (64-bit)

What is the expected behavior?
The API should works as expected. 

What went wrong?
Please see the attached image

Did this work before? N/A 

Chrome version: 57.0.2946.0  Channel: dev
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0
 
Screen Shot 2016-12-12 at 4.37.14 PM.png
193 KB View Download
Labels: M-57

Comment 3 by hdodda@chromium.org, Dec 14 2016

@garyyeap-- Could you please provide us the sample extension , in which you are facing the issue , that would help us in triaging the issue better.

Thanks !

Comment 4 by hdodda@chromium.org, Dec 14 2016

Labels: Needs-Feedback
Components: Platform>Extensions>API
The extension still under development, but there is an open source project: 
https://github.com/andyyoung/Process-Monitor-for-Chrome
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 28 2016

Labels: -Needs-Feedback Needs-Review
Owner: hdodda@chromium.org
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 8 by hdodda@chromium.org, Dec 29 2016

Cc: hdodda@chromium.org
Labels: -Needs-Review
Owner: ----
@could someone from extensions API team look into this.

Thanks!
Requesting someone from extensions API team to take a look into this issue.

Thanks..
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
Tested this issue on Mac 10.12.2 with chrome #57.0.2946.0 with the extension provided in the comment #6

Observed that in the extension console, it is allowing the chrome.process.* commands with without any errors.

Attaching the screencast for your reference, please look into it and let us know any steps i have missed while reproducing the scenario. 
Issue 673623.mp4
662 KB View Download

Comment 11 Deleted

Redownloaded the latest dev version: 58.0.3000.4 (Official Build) dev (64-bit)
Still no luck, attaching the screencast which follow #10 steps.
Untitled.mp4
3.3 MB View Download
Project Member

Comment 13 by sheriffbot@chromium.org, Feb 14 2017

Labels: -Needs-Feedback Needs-Review
Owner: kkaluri@chromium.org
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919 
Labels: -Needs-Review

Comment 16 by creis@chromium.org, Sep 28 2017

Blocking: 238804

Comment 17 by creis@chromium.org, Sep 28 2017

Cc: creis@chromium.org nasko@chromium.org
This API is intentionally still considered experimental and is not available for most users until several blocking bugs are fixed.

You should be able to experiment with it using the --enable-experimental-extension-apis command line flag.
Labels: Needs-Feedback Needs-Milestone
@Reporter: Could you please respond to Comment #17 and provide your inputs to take further action on this.

Thank you!

Comment 19 Deleted

Status: WontFix (was: Unconfirmed)
Mac triage: WontFix per #17.

Sign in to add a comment