javascript - background.html vs. background.js - chrome extension -
I'm really confused here, I'm trying to understand the file extension of the Chrome extension. I am reading this document:
My status:
I want to set an oath flow so that the user can log in to the extension (other endpoint mydegango backend) Up to now, I have these files:
background.js content.js popup.html manifest.json
where my message to content.js Sends .js and get feedback back so far!
But now while reading a doctor for OHTH, I do not know what background.html is. Is this really a file in which my background.JS code contains JS code? But, if I see it in .html
, like:
"background": {"persistent": wrong, "script": ["jquery111. Js "," background.html "]
The extension is no longer working. In Oath Doctor, it says:
Place four library files in the root of your extension directory (or wherever your javascript is stored). Then include .js files in your background page ... Your background page will manage OAuth flows.
But in this, it says:
This statistic illustrates the background page of the browser action, defined by the background and the javascript code What is the behavior of browser actions in both windows?
What is the difference between background.html and background.js?
Comments
Post a Comment