New issue
Advanced search Search tips

Issue 867424 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 19
Components:
EstimatedDays: ----
NextAction: 2018-10-12
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Devtools Extension Issue

Reported by ambatima...@gmail.com, Jul 25

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Open the Chrome webstore
2. Add this extension https://chrome.google.com/webstore/detail/pact-engine/ghnebihkloddbfjhhainedngckegndeg?hl=en-US
3. Try to run.

What is the expected behavior?
It has to run the accessibility test on the page

What went wrong?
Although it is working absolutely fine in Developer mode. Unable to run on chrome webstore.

Did this work before? No 

Chrome version: 67.0.3396.99  Channel: n/a
OS Version: 10.0
Flash Version: 

I developing Devtools extension by following this example from github. I am able to run the extension fine in the developer mode but when i moved the same to web store. I am facing the following issue This extension may have been corrupted. and found following console error :

(Uncaught TypeError: Cannot read property 'connect' of undefined
    at createChannel (messaging.js:13)

messaging.js:13 has this code 

(function createChannel() {   
    var port = chrome.extension.connect({
        name: "Sample" 
    });
    var count=0;
    var activeTabClass;
    // Listen to messages from the background page
    port.onMessage.addListener(function (message) {
		setTimeout(function(){showResult(message);},1)       

    });

and Manifest.json has this.

{
  "name": "Sample Engine",
  "version": "1.04",
  "manifest_version": 2,
  "devtools_page": "devtools.html",
  "description": "Chrome Developer Tools",
  "icons": { "64": "images/pact.png" },
  "background": {
    "scripts": [
      "scripts/jquery1.12.4-min.js",
      "scripts/jquery-ui.min.js",
     "scripts/background.js",
	  "scripts/panel.js",
	  "scripts/tab-order.js",
	  "scripts/high-lighter.js"	  
    ],
	   "persistent": false
  },
  "content_scripts": [
    {     
      "js": [ "scripts/jquery1.12.4-min.js", "scripts/jquery-ui.min.js"],
	  "css": ["css/Injected-styles.css"]
    }
  ],

  "permissions": [
    "activeTab",
    "tabs",	
    "http://*/*",
    "https://*/*",
	"storage"  
  ]
}
 
I can reproduce the corruption in Chrome.
Interestingly it doesn't happen in Chromium.

Not sure if relevant but chrome.extension.connect and chrome.extension.sendMessage were deprecated a long time ago, so try using chrome.runtime.connect and chrome.runtime.sendMessage instead.
Labels: Needs-Triage-M67
I tried using chrome.runtime.connect and chrome.runtime.sendMessage same issue observed.
 Issue 867392  has been merged into this issue.
Labels: Triaged-ET Target-70 M-70 FoundIn-70 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #68.0.3440.75 and latest canary #70.0.3503.0.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Components: -Platform>DevTools Platform>Extensions
Labels: Needs-Feedback
Do you get an error saying the extension has been corrupted. Can you post a screencast or copy the error verbatim?
NextAction: 2018-10-12
Please see comment #7 - any corruption errors?  Without more to go on, we'll have to close this out.
The NextAction date has arrived: 2018-10-12
Status: Archived (was: Untriaged)
Archiving.  Please open a new bug if you see this again.

Sign in to add a comment