issue #64 - added release 10.0 documentation and mv3 updates

Author: Manvel

pages/documentation/actions/bg-inject.md

@@ -5,6 +5,18 @@ weight: 3
 edit: documentation/actions/bg-inject.md
 ---
 
+# bg-inject is deprecated since CBA version 10.0
+
+Since [Manifest Version 3](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security#remove-execution-of-strings) it's
+not allowed to evaluate script in the context of the extension, meaning CBA users can no more use `bg-inject` command. Previously `bg-inject` was used for injecting script into the background page of the extension where you can also access browser api and create very flexible and powerful Automation.
+Currently only extension hosted code can be executed in the context of the background page and the only way to do it is by using [bg-function](/bg-function) command. I am happy to accept commands you have used with `bg-inject` and add them to the `bg-function` command, so please let me know by
+[filing an issue](https://github.com/browser-automation/cba/issues) or feel free to creating a PR. Please let me know about your use-cases that you can
+no more support with the new MV3 compliance rules, I will try helping you there.
+
+Learn more about [MV3 compliance changes](/mv3).
+
+## bg-inject in CBA version 9.0 and less
+
 `bg-inject` provides ability of injecting script into backroung page of the
 extension where you can also access browser api.
 

pages/documentation/actions/inject-cs.md

@@ -5,6 +5,14 @@ weight: 2
 edit: documentation/actions/inject-cs.md
 ---
 
+# cs-inject is works similar to inject since CBA version 10.0
+
+Since [Manifest Version 3](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security#use-external-libraries) it's not allowed to evaluate user script in the context of the extension, meaning CBA users can no more use `cs-inject` command as they used to. Previously `cs-inject` was allowing users to inject script into the content script of the extension where it was following Extensions content security policy. Now `cs-inject` and `inject` functions are same, they both are loading scripts into the page Main context. This is another limitation introduced by the new [Manifest version 3](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3) rules for Browser extensions. This behavior may change after platforms implement [userScripts.execute()](https://github.com/w3c/webextensions/pull/540).
+
+Learn more about [MV3 compliance changes](/mv3).
+
+## cs-inject in CBA version 9.0 and less
+
 Inject is the Action that Injects javascript code into content script during
 project workflow, also you can use Jquery. It uses javascript `eval()` function
 to inject your code. so here you can write your javascript code using functions
@@ -18,7 +26,9 @@ $("body").html("Hello World");
 ```
 </div> 
 
-## async/await
+## ~~async/await~~
+
+**Note:** Since CBA version 10.0, `async/await` is not supported in the `cs-inject`.
 
 You can also use async/await in the `cs-inject` that way you can wait for an
 async function execution before proceeding with the next action.

pages/mv3.md

@@ -0,0 +1,25 @@
+---
+title: Manifest version 3
+edit: mv3.md
+---
+
+Starting from [version 10](/new_10-0) CBA is now [MV3 compliant](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3), meaning you still able to use it with newer Chrome versions. But there are multiple limitations.
+
+## Limitations
+
+- Extensions are no more allowed to execute arbitrary code in the background page, which means that CBA can no more support [bg-inject](/bg-inject) command:
+- Background pages are no more persistence and from time to time the clipboard value may be lost, we will be fixing it with current [issue](https://github.com/browser-automation/cba/issues/119).
+- [cs-inject](/inject-cs) and [inject](/inject) functions now are same, they both are loading scripts into the page Main contextScript.
+
+
+### bg-inject
+
+Since [Manifest Version 3](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security#remove-execution-of-strings) it's
+not allowed to evaluate script in the context of the extension, meaning CBA users can no more use `bg-inject` command. Previously `bg-inject` was used for injecting script into the background page of the extension where you can also access browser api and create very flexible and powerful Automation.
+Currently only extension hosted code can be executed in the context of the background page and the only way to do it is by using [bg-function](/bg-function) command. I am happy to accept commands you have used with `bg-inject` and add them to the `bg-function` command, so please let me know by
+[filing an issue](https://github.com/browser-automation/cba/issues) or feel free to creating a PR. Please let me know about your use-cases that you can
+no more support with the new MV3 compliance rules, I will try helping you there.
+
+### cs-inject
+
+Since [Manifest Version 3](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security#use-external-libraries) it's not allowed to evaluate user script in the context of the extension, meaning CBA users can no more use `cs-inject` command as they used to. Previously `cs-inject` was allowing users to inject script into the content script of the extension where it was following Extensions content security policy. Now `cs-inject` and `inject` functions are same, they both are loading scripts into the page Main context. This is another limitation introduced by the new [Manifest version 3](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3) rules for Browser extensions. This behavior may change after platforms implement [userScripts.execute()](https://github.com/w3c/webextensions/pull/540).

pages/releases/beta.md

@@ -38,7 +38,7 @@ new:
   - CBA has been open-sourced.
   - Website has been migrated from slow Drupal instance to blazing fast <a
     href="https://cmints.io/">CMintS</a> website.
-weight: 1
+weight: 10
 edit: releases/beta.md
 ---
 

pages/releases/varsion-9.md

@@ -1,7 +1,7 @@
 ---
 title: Version 9.0
 permalink: new_9-0
-weight: 1
+weight: 2
 edit: releases/varsion-9.md
 ---
 

pages/releases/version-10.md

@@ -0,0 +1,23 @@
+---
+title: Version 10.0(MV3)
+permalink: new_10-0
+weight: 1
+edit: releases/varsion-10.md
+---
+
+Current release introduces multiple breaking changes, those changes was due to the
+[new compliance rules introduced by the Chrome Platform](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3). There are
+multiple limitations introduced by the MV3, which are described in the [MV3 documentation](/mv3). See [list of all changes here](https://github.com/browser-automation/cba/releases/tag/10.0.0):
+- CBA is now [MV3 compliant](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3), meaning you still able to use it with newer Chrome versions.
+- [bg-inject](/bg-inject) - command is deprecated, Chrome platform no more
+  supports injecting user script into Background page.
+  - If your automation highly relies on bg-inject, please let me know by [filing an issue](https://github.com/browser-automation/cba/issues), I will try add new
+    [bg-function](/bg-function) command for those commands that suppose to be
+    injected in the background. I am also happy to accept PRs for this.
+- [cs-inject](/inject-cs) and [inject](/inject) functions now are same, they
+  both are loading scripts into the page Main contextScript. This is another
+  limitation introduced by the new [Manifest version 3](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3)
+  extensions.
+- Background pages are no more persistence and they will always be reloaded when
+  you execute action, or open CBA popup. Which means the clipboard content might
+  be lost on followup execution if that happens [unless current issue is fixed](https://github.com/browser-automation/cba/issues/119).

pages/releases/version-5.md

@@ -1,7 +1,7 @@
 ---
 title: Version 5.0
 permalink: new_5
-weight: 5
+weight: 6
 edit: releases/version-5.md
 ---
 

pages/releases/version-6.md

@@ -1,7 +1,7 @@
 ---
 title: Version 6.0
 permalink: new_6
-weight: 4
+weight: 5
 edit: releases/version-6.md
 ---
 

pages/releases/version-7.md

@@ -1,6 +1,6 @@
 ---
 title: Version 7.0
-weight: 3
+weight: 4
 edit: releases/version-7.md
 ---
 

pages/releases/version-8.md

@@ -1,7 +1,7 @@
 ---
 title: Version 8.0
 permalink: new_8
-weight: 2
+weight: 3
 edit: releases/version-8.md
 ---