StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19487091
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-10-21T05:50:57.157
FavoriteCount
0
LastActivityDate
2013-10-21T05:50:57.157
LastEditDate
LastEditorUserId
0
OwnerUserId
638452
ParentId
11920473
PostTypeId
2
Score
18
ViewCount
0
LastEditorDisplayName
text
Body
Your background is only one page and acts like a local server that can send and receive data between the <code>content_scripts</code> and <code>default_popup</code> or other extension pages. For anyone starting out, look at each example's manifest version, which is defined in manifest.json. Version 2 has stricter security policies and inline javascript is invalid so copying sample v1 code and pasting it into background.html will not work anymore. All scripts need to be in an external file that can be included in an HTML file using the <code>src</code> attribute like <code><script src="main.js"></script></code> My understanding is that you have four commonly used components for a basic extension: <ol> <li>DOM of the tab being viewed which can only be accessed by <code>content_scripts</code></li> <li>content_scripts is an array of javascript files identified in manifest.json that are sequentially injected directly into the tab's DOM. Apparently the JS variables and functions from the tab and your content_scripts cannot interact.</li> <li>One background HTML page which Chrome either generates by concatenating an array of scripts OR is defined as one page, commonly named background.html.</li> <li><code>{"browser_action" : {"default_popup" : "popup.html"}}</code> is an optional user interface defined in manifest.json that is displayed when someone clicks your extension icon. The popup has no way to reach the tab's DOM so if the tab's content matters then it must be requested using Chrome messages like <code>chrome.extension.sendMessage</code></li> </ol> Your background is defined either as one or more <code>scripts</code>: <pre><code> "background": { "scripts": ["background.js"] }, </code></pre> Or as a <code>page</code>: <pre><code> "background": { "page": "background.html" }, </code></pre> If you want to find out what is happening inside of the background then you can use console.log but in order to inspect the output you have to launch the inspector from the Extensions page. You can even see that the background file is always named "_generated_background_page.html". <img src="https://i.stack.imgur.com/MSVxw.png" alt="enter image description here">
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POChrome extension background page html not working
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDylan Valade
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.