New issue
Advanced search Search tips

Issue 823585 link

Starred by 1 user
Status: Duplicate
Merged: issue 823577
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

set port name failed (port is returned by chrome.runtime.connectNative)

Reported by xu.sen...@gmail.com, Mar 20 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36

Steps to reproduce the problem:
1. I'm developer, I'm using native messaging to call a native app via chrome.runtime.connectNative(appName)
2. port = chrome.runtime.connectNative(appName)
3. See "What went wrong?"

What is the expected behavior?

What went wrong?
Here are my codes:
nativePort = chrome.runtime.connectNative(appName);
nativePort.name = 'appName';
My problem is: port.name is not set to the value 'appName', it's empty

I can't reproduce this issue on release edition(65)  and beta edition(66). 

Did this work before? Yes Chrome 66 Beta Edition is OK, Chrome 67.0.3371.0 Dev Edition 64bit is not working

Chrome version: 67.0.3371.0  Channel: dev
OS Version: 10.13.3
Flash Version:

Comment 1 by xu.sen...@gmail.com, Mar 20 2018 

I can reproduce it on Windows/Chrome canary

Comment 2 by krajshree@chromium.org, Mar 20 2018

Labels: Triaged-ET Needs-Triage-M67
Mergedinto: 823577
Status: Duplicate (was: Unconfirmed)
The issue looks similar to issue id: 823577. Hence merging into the issue id: 823577.
Please feel free to undupe if not the case.

Thanks...!!

Comment 3 by xu.sen...@gmail.com, Mar 20 2018 

I think it is not the same issue to 823577, could you check it. Thanks a lot
►

Sign in to add a comment