docs: update changelog

Author: painty

CHANGELOG.md

@@ -1,3 +1,11 @@
+**ver 3.0.0 | 15/01/2023**
+
+1. Migrated to Manifest V3.
+1. Resources are read from local caches, making it much faster and solves the [cross-origin issue](https://github.com/painty/CSS-Used-ChromeExt/issues/52).
+1. Optimized style parsing in a more efficient way.
+1. Dropped support for some outdated CSS, mostly -o- and -ms- prefixed properties.
+1. Implemented a new UI powered by Svelte, with some visual tweaks.
+
 **ver 2.5.0 | 15/03/2021**
 
 1. New. Option page.
@@ -82,15 +90,15 @@
 2. Add. Two buttons: `Copy to clipboard` & `Send to codepen`
 3. Better handling for pseudo element/class
 
-**ver 1.4.2 | 04/15/2017** 
+**ver 1.4.2 | 04/15/2017**
 
 1. Add. calculating progress display.
 
 **ver 1.4.1 | 04/09/2017**
 
 1. multiple pseudo class/element detection
 
-**ver 1.4.0 | 04/09/2017** 
+**ver 1.4.0 | 04/09/2017**
 
 1. Add. media query support
 2. Add. font-face support

README.md

@@ -22,9 +22,11 @@ You can click "Preview" to see the selected part with clean style rules.
 
 ## FAQ
 
-1. Permission to read my browsing history
+1. No result
 
-    See https://github.com/painty/CSS-Used-ChromeExt/wiki/Permission-to-read-my-browsing-history%3F
+   1. Check whether it's Chrome Web Store pages, which is `https://chrome.google.com/webstore/....`, which won't allow content script injection.
+   1. If it's a normal webpage, check site access permission https://github.com/painty/CSS-Used-ChromeExt/issues/13#issuecomment-687244215
+   1. If it's a local file, chrome won't allow local file access by default. You can turn on the "Allow access to file URLs" in the extension management page.
 
 1. Preview not right
 
@@ -33,21 +35,9 @@ You can click "Preview" to see the selected part with clean style rules.
 
 1. Not all the CSS is got
 
-    The result is generated based on the CURRENT HTML DOM. If a div doesn't exist in the document unless a specific user interaction, the result may miss out the style rules for the newly born div.
-    
-1. Always says to fresh the page
-
-   First check whether it's Chrome Web Store pages, which is `https://chrome.google.com/webstore/....`, which won't allow content script injection. If it's a normal webpage , please create an issue.
+    1. The result is generated based on the CURRENT HTML DOM. If a div doesn't exist in the document unless a specific user interaction, the result may miss out the style rules for the newly born div.
+    1. CSS custom properties (variables) are partially supported. Not working for declarations defined by $0's ancestor. Thinking it as a inheritable CSS property, as this tool won't handle inherit style.
 
 ## Changelog
 
-Go to [releases](https://github.com/painty/CSS-Used-ChromeExt/releases)
-
-For older version infomation:
 Go to the [Changelog page](CHANGELOG.md)
-
-## Dev
-
- 1. `npm install` to install all the dependencies
- 2. `npm run build` gernerate `/build/asset/js/content.js`. Drag the `build` folder to `chrome://extensions/`, remember to turn on the dev mode on the top right of the page.
- 3. `npm test` will start a local `http://localhost:1234` server. Visiting the test page and check the console.