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
Browsers
Web Extensions
The Death of webRequest API & uBO? Not likely, at least for now.
Message
<blockquote data-quote="Windows_Security" data-source="post: 793160" data-attributes="member: 50782"><p><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> Hold your horses. The manifest is still in draft and when changes are implemented extensions developers will have a year+ to adopt their software. It took them over 1.5 year to move from <a href="https://developer.chrome.com/extensions/manifestVersion#manifest-v1-changes" target="_blank">Manifest V1 to V2</a> and since january 2014 we are on V2 (so five years now). When they manage to speed up implementation like they did for V1 to V2 transition, it will be in Q4 of 2020 at the earliest that only the new API is allowed.</p><p></p><p></p><p></p><p>Will be interesting to see whether Raymond Hill will adopt or shift development effort to Firefox (or to Edge with the help of Hugo Xu - developer of NanoAdBlocker). Raymond Hill does not accept donations, so he develops for fun. Most programmers don't find rewriting software very inspiring when it is just for technical compliance.</p><p></p><p>Maybe this is a nice opportunity for Microsoft. They are moving to Blink engine and expect to ship early version end 2019, so maybe Microsoft uses this as an opportunity to differentiate Edge form Chrome and Chrome clones (the only browser with Blink engine and advanced Ad Blocking <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> )</p></blockquote><p></p>
[QUOTE="Windows_Security, post: 793160, member: 50782"] :) Hold your horses. The manifest is still in draft and when changes are implemented extensions developers will have a year+ to adopt their software. It took them over 1.5 year to move from [URL='https://developer.chrome.com/extensions/manifestVersion#manifest-v1-changes']Manifest V1 to V2[/URL] and since january 2014 we are on V2 (so five years now). When they manage to speed up implementation like they did for V1 to V2 transition, it will be in Q4 of 2020 at the earliest that only the new API is allowed. Will be interesting to see whether Raymond Hill will adopt or shift development effort to Firefox (or to Edge with the help of Hugo Xu - developer of NanoAdBlocker). Raymond Hill does not accept donations, so he develops for fun. Most programmers don't find rewriting software very inspiring when it is just for technical compliance. Maybe this is a nice opportunity for Microsoft. They are moving to Blink engine and expect to ship early version end 2019, so maybe Microsoft uses this as an opportunity to differentiate Edge form Chrome and Chrome clones (the only browser with Blink engine and advanced Ad Blocking :) ) [/QUOTE]
Insert quotes…
Verification
Post reply
Top