* Updated Relative URL
As mentioned in #547, due to #542 , these links no longer works. @dotproto mentioned that a fix is on its way but maybe was delayed for some reason, so this PR was created to update the links. The directory structure info was updated accordingly.
Also, @dotproto said
> we also don't want them to be the main content everyone comes here for.
I suggest two possible approaches:
1. Collapse the version 2 samples, like this:
```
<details><summary>MV2 </summary>
[Print Extension](mv2-archive/api/printing)<br />Sends print job directly to the printers installed on the Chromebook | <ul><li>printing.getPrinterInfo</li><li>printing.getPrinters</li><li>printing.submitJob</li><li>runtime.lastError</li></ul>
</details>
```
2. Move the version 2 samples to `readme.md` in `mv2-archieve/`
* Create Readme for mv2
* Update README.md
Relocated mv2 samples
* Update README.md
Fix typo
* Update getting started code for MV3
* Small polish & cleanup in getting started
* Minor: reorder manifest version fields
* Updates based on article drafting process
* Cleanup from getting-started runthrough
Like a real web browser, the content should be focused whenever it is
navigated. Additionally, since there is a default web page shown on
start, the webview should be focused. This is unlike a new tab page in
chrome that doesn't really have content and invites the user to type
into the address bar (which should have focus in that case.)
Handle errors in chrome.sockets.tcpServer.listen() by logging it to
the console. An error here is normal and expected for app instances
created after the first instance.
The argument to the chrome.sockets.tcp.send callback is undefined if
the socketId represents a closed socket. This commit handles the error
propagation for that case. I filed bug 588126 against chrome.sockets.
The readyState variable was not initialized on socket creation, and
not being tested properly. This could cause an attempt to send the
close frame twice, and/or to close the underlying TCP socket twice.
The chrome.socket API is deprecated since Chrome 33. This commit
updates websocket-server to the chrome.sockets.tcp and
chrome.sockets.tcpServer APIs.
For convenience, the chrome.sockets.tcp socketId is wrapped with a
PSocket class with member functions read/write/close that return
Promises.
