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

Issue 669626 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Dec 2017
Cc:
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Platform>Extensions: chrome.runtime.connect is not defined on page load (race condition)

Reported by ast...@lastpass.com, Nov 29 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:50.0) Gecko/20100101 Firefox/50.0

Steps to reproduce the problem:
Sadly, this does not seem to be a 100% reproducible issue as I can only make it happen if I refresh the extension page a few times. I have attached a screenshot proving that it does happen though.

What is the expected behavior?
I would expect chrome.runtime.connect to be available before any of the extension page JS loads.

What went wrong?
chrome.runtime.connect is undefined.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 54.0.2840.98  Channel: stable
OS Version: OS X 10.11
Flash Version: 23.0.0.207
/Screen Shot 2016-11-29 at 2.38.20 PM.png
77.9 KB View Download

Comment 1 by ast...@lastpass.com, Nov 29 2016 

One thing to note: this is occurring in an extension page that is a child window (iframe) of a parent extension page. Debugging the case shown in the screenshot a bit further, I can see that the parent.chrome.runtime.connect is defined at that point in time.

Comment 2 by manoranj...@chromium.org, Nov 29 2016

Labels: M-54

Comment 3 by durga.behera@chromium.org, Dec 1 2016

Cc: durga.behera@chromium.org
Components: Platform>Extensions
Labels: Needs-Feedback
asteel@: Could you please help with the extension and more description about the steps to reproduce it from Test Engg end.
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 11 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment