New issue
Advanced search Search tips

Issue 891388 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
rdevlin....@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

runtime.Port.sender is undefined instead of being missing

Project Member Reported by emaxx@chromium.org, Oct 2 
Chrome Version: 69.0.3497.95.
OS: Chrome OS.

What steps will reproduce the problem?
(1) Run two extensions, A and B.
(2) Extension A opens a Port to B using runtime.connect().
(3) Extension A checks the presence of the field Port.sender.

What is the expected result?
The 'sender' field is missing from the Port object.

What happens instead?
The 'sender' field is present (i.e., hasOwnProperty() returns true), but its value is |undefined|.

Comment 1 by emaxx@chromium.org, Oct 2 

Not sure when this first appeared and how serious this incompatibility is, but decided to file this to be tracked at least.

This issue led to some fatal assertion failures in the smart card framework (the Smart Card Connector app and the skeleton that we provide for third-party extensions), although the workaround for this in our code is simple.

Comment 2 by rdevlin....@chromium.org, Oct 2

Status: Available (was: Untriaged)
Interesting.  Given this isn't documented one way or the other (i.e., we don't really specify whether properties will have a property descriptor but be undefined or not have a property descriptor at all), I don't think it's terribly high priority to fix.  But it is worth tracking in case this turns out to affect significantly more extensions.
►

Sign in to add a comment