Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Software Troubleshooting
Something wrong with Ublock Origin on Google Chrome
Message
<blockquote data-quote="Burrito" data-source="post: 813548" data-attributes="member: 72439"><p>Hmmmm.....seem like sum ting wong.</p><p></p><p>uBO is implemented differently in Chrome and Firefox sometimes.</p><p></p><p>Here is an example:</p><p></p><p style="margin-left: 20px"><span style="font-size: 18px"><em><u>uBlock Origin performance improvements thanks to WASM (Firefox only, for now)</u></em></span></p><p><em> A recent version of the content blocking extension <a href="https://github.com/gorhill/uBlock/releases" target="_blank">uBlock Origin</a> uses WebAssembly (WASM) code to improve the performance of the extension.</em></p><p style="margin-left: 20px"><em>The new uBlock Origin 1.17.4 is already available on the GitHub project website and Google and Mozilla web stores for extensions.</em></p> <p style="margin-left: 20px"><em>The new versions get pushed out to users in a rolled released which means that you may not get it immediately. Chrome and Firefox users may enforce the update. Chrome users may want to read how to <a href="https://www.ghacks.net/2018/09/25/how-to-update-chrome-extensions-manually/" target="_blank">update Chrome extensions manually</a> for information on how that is done, <a href="https://www.ghacks.net/2018/12/03/how-to-update-firefox-extensions-manually/" target="_blank">Firefox users may check this guide instead</a>.</em></p> <p style="margin-left: 20px"><em>Raymond Hill (gorhill) notes that the new code is only active in the Firefox extension and not in the extension for Google Chrome. The reason for that is that Google Chrome does not allow wasm "without adding 'unsafe-eval' to the extension's own Content Security Policy in its manifest" which Raymond considers unsafe for use).</em></p><p></p><p>To get to the specifics of your question.... you need an expert. Perhaps [USER=50782]@Windows_Security[/USER] or [USER=51905]@Evjl's Rain[/USER] or [USER=71262]@oldschool[/USER] or [USER=32260]@Andy Ful[/USER]..</p></blockquote><p></p>
[QUOTE="Burrito, post: 813548, member: 72439"] Hmmmm.....seem like sum ting wong. uBO is implemented differently in Chrome and Firefox sometimes. Here is an example: [INDENT][SIZE=5][I][U]uBlock Origin performance improvements thanks to WASM (Firefox only, for now)[/U][/I][/SIZE][/INDENT] [I] A recent version of the content blocking extension [URL='https://github.com/gorhill/uBlock/releases']uBlock Origin[/URL] uses WebAssembly (WASM) code to improve the performance of the extension.[/I] [INDENT][I]The new uBlock Origin 1.17.4 is already available on the GitHub project website and Google and Mozilla web stores for extensions.[/I][/INDENT] [INDENT][I]The new versions get pushed out to users in a rolled released which means that you may not get it immediately. Chrome and Firefox users may enforce the update. Chrome users may want to read how to [URL='https://www.ghacks.net/2018/09/25/how-to-update-chrome-extensions-manually/']update Chrome extensions manually[/URL] for information on how that is done, [URL='https://www.ghacks.net/2018/12/03/how-to-update-firefox-extensions-manually/']Firefox users may check this guide instead[/URL].[/I][/INDENT] [INDENT][I]Raymond Hill (gorhill) notes that the new code is only active in the Firefox extension and not in the extension for Google Chrome. The reason for that is that Google Chrome does not allow wasm "without adding 'unsafe-eval' to the extension's own Content Security Policy in its manifest" which Raymond considers unsafe for use).[/I][/INDENT] To get to the specifics of your question.... you need an expert. Perhaps [USER=50782]@Windows_Security[/USER] or [USER=51905]@Evjl's Rain[/USER] or [USER=71262]@oldschool[/USER] or [USER=32260]@Andy Ful[/USER].. [/QUOTE]
Insert quotes…
Verification
Post reply
Top