-
Notifications
You must be signed in to change notification settings - Fork 22
Nano Adblocker / Defender for Chromium-based Edge issues megathread #253
Comments
@jspenguin2017 I understand, you will add nano defender too, if it is chromium base. When you add? People still waiting. |
@seba2282 The insider extensions store is currently invite-only. I don't know when Microsoft will start to accept submissions. |
@jspenguin2017, can you tell more details, how works that insider extension program? I saw Nano Adblocker. |
@seba2282 What specifically? |
@jspenguin2017, you said about extension insider store. Can you more details, how extensions start be in that? Nano Adblocker is. What with Nano Defender? |
@seba2282 I got an invitation email from Microsoft for Nano Adblocker, but didn't get one for Nano Defender. |
If you want informations, I know, Windows 10 19H1 will not have Edge on Chromium. Maybe will be in Windows 10 19H2. Important is, Windows 10 as separate will be on abonament or only with some services like xbox pass and office 365. |
The install package of Chromium-based Edge leaked yesterday. You can test with that package. As the program has a switch to "install extensions from other sources", I think upload Nano adblocker/defender will only be useful for users who cannot access Google services, for example, users in mainland China. |
@lychichem I'll wait for an official release to confirm. |
@jspenguin2017 and you can't give new versions Nano Adblocker to actual Microsoft Edge? |
@seba2282 For Chromium-based Edge, Microsoft will be managing the extensions for now. For legacy Edge, see my comment here: #40 (comment) |
@jspenguin2017 it would be nice if support for older Edge could be maintained because, even though the new Edge will be out in a couple of weeks, it will be released as a preview which most regular users won't use. No one knows when the new Edge will be available as a stable build, it will probable be available either for the 1909 or 2003 Windows build, so 6 months or 1 year where regular users won't receive any new Nano Adblocker versions. |
@ivanmestre If enough people want another build for legacy Edge, I will reconsider. Cast your vote by adding 👍 to the comment above. |
@jspenguin2017 Thanks, also Nano Adblocker works great on the new Edge. Both the one in the Edge Insider Extensions page and the one on the Chrome Store. I believe they are the same extension, but the one on the Edge Insider page is an older build. I believe what Microsoft did was listing the extensions that are currently in the Microsoft Store for old Edge and publishing the Chrome version on the Insider page. I think that's the case because Nano Adblocker on the Microsoft Store on old Edge is version 0.0.85.0 and the one in the Edge Insider page on new Edge is version 1.0.0.77. |
@jspenguin2017, Nano Adblocker will be continue for old MS Edge? Is few time before MS give final MS Edge Chromium-base. |
@seba2282 I have explained it above: #253 (comment) #253 (comment) |
Any information about few support for old Edge until time, when will be Final Edge Chromium? |
There's only 4 upvotes on the post above, so chances are I won't release new builds for the old Edge. The Chromium-based Edge should be ready in a few months, it's already out for public beta: |
@jspenguin2017, you didn't think about people who hasn't GitHub accounts? I guess is more people, who like your Nano products and they won't have actual any insiders Edge or other insider products and they wait for final version as regular. You only look on people who active on GH. But on others who haven't accounts GH... |
@seba2282 Obviously I'm not expecting hundreds of upvotes, even though most people don't have a GitHub account, 4 votes is still too little. I know the new Edge is not yet bundled with Windows, but people can just go download it, I don't see how is that a problem. |
Please keep the Nano Adblocker for EgdeHTML up to date. The new Chromium based one is awful on any touch & pen devices. It may/will take a very long time to match the usability of the old Edge, if ever at all. Who knows what's going to happen with the new incarnation of Edge, where the old one is perfectly fine and way better. Thank you. |
I'll reconsider once there's ~20 votes. There's about 140 Internet users for every 1 GitHub user, 20 votes equates to about 2800 Internet users, which seems reasonable. Some work is needed on Edgyfy side. I need an up-to-spec polyfill for |
Hello. When will the 1.00.104 version be available in the Microsoft store? |
When @jspenguin2017 give update. So after 6-12 months. Because Edge Chromium will after that time as stable and integrate with Windows 10. Author still isn't interesting old Edge. |
I'm talking about an update for the new edge because I use it since the day of the release for insiders. |
Dear jspenguin2017, thank you for taking into consideration the option of updating the Nano Adblocker for EdgeHTML once there are 20 votes for it. Hopefully happens soon. I think Microsoft will never give up completely on EdgeHTML, at least not in the near future. I'm all Surface, same many of my friends and a proper touch & pen support is indispensable for us. |
@gdata1 The extension store for the new Edge is fully managed by Microsoft, and I can't update the listing. Note that you can install extensions directly from the Chrome WebStore to get newer versions. |
@jspenguin2017 Apologies for my late reply caused by a very busy period as usual before Christmas. |
@PeteAtGH If you're using my projects in an enterprise environment, then you really need to consider hiring a freelancer to contribute back instead of relying on my volunteer work. |
Microsoft Edge Addons store is now open for submissions today. Hope to see Nano Defender in new Microsoft Edge Addons store. |
@kevin12314 If you want to get it now: https://microsoftedge.microsoft.com/addons/detail/ijfkmnlofajajikjhfiigelipempcklj |
@jspenguin2017 |
ever since updating to the recent January Windows Update, Nano Adblocker no longer seems to work with Windows 10 version 1909 (the old one not the new Chromium based one)...is it just me or is it a known issue? |
@TitusTroy The version for legacy Edge is no longer maintained. You should upgrade to the new Chromium based Edge. |
thanks for the info...so the older version doesn't work at all anymore?...I was going to wait a few weeks before using Chromium Edge in case there were any bugs...so a new version of Nano Adblocker is available for Chromium Edge? |
I tested Nano Adblocker on the Legacy Edge and it looks like it's working. |
I don't know if the older version still works or not (I haven't tested it), it should still work unless something changed in legacy Edge. There is a newer version of NA (and ND) available for Chromium based Edge, I have tested them and they work properly. |
so after I download the new Chromium Edge do I still need to go to the Microsoft Store to find the new version of Nano Adblocker? |
@TitusTroy It should ask you, if not, you may have to install it manually. Note that this is not a tech support forum, for general questions about how to use Edge, you should search on Google first. |
@jspenguin2017 That's fine, I understand. The current version for EdgeHTML works perfectly fine so I'll be patiently waiting for an updated version. |
Even though I am still in university, my time is not cheap. Instead of thanking me for creating these projects, you decided to complain about terminating support of a dead platform. That is not nice. You cannot afford to hire a freelancer to keep a project you use maintained is not a reason for me to spend my time maintaining it for free. I repeat what I said, unless someone step up to contribute to the maintenance of the legacy Edge build, it will no longer receive updates. |
Your time, your business, your problem, your decision, your project. I never complained, you must have read someone else's comments, that's not fair, I always expressed my gratitude for your work, check my posts. And the "platform" is not dead, at least not yet, still a default browser on every current and insider build, incl. W10 X emulator, W10 S, HoloLens 2, Xbox, etc. Works properly with Office 365 online, SharePoint, variety of corporate and specialist websites, etc., where the new ChrappyEdge fails. Have a look on Microsoft's domestic and enterprise forums at the amount of negative posts about the NewEdge. Nevertheless, your choice but many thanks again for creating this project and all your hard work as well as time you put into it. Cheers. |
It is my time, my decision, and my project. However, it is your business and your problem. I do not use the legacy Edge anymore and the new Edge works fine for me. I ran into far more issues with the legacy Edge and I am happy to ditch it as soon as the new Edge came out. If you chose to use legacy Edge in your businesses, then it is not up to me to solve your problems. In your previous comments, you are pushing me to release an update for legacy Edge. I took it as a complain but it does not matter, it is a complain or not will not change the current situation. My decision is final, unless another maintainer step up to contribute, the legacy Edge build will not be updated. |
@jspenguin2017 Tell true, is easier make updates for chromium. What you will make when Manifest 3 finally welcome for Chromium and will be obligation in all browsers basic Chromium? You wondered about that scenario? |
Yes, it is way easier to develop for Chromium, the debugger just works and never crashes, unlike the legacy Edge or Firefox. As for dealing with Manifest V3, there are many potential solutions proposed in the Manifest V3 megathread. Also, Chromium forks are not forced to take all changes from the upstream, so it is very possible that some forks will keep the old I certainly considered the scenario where all Chromium-based browsers moved to strictly Manifest V3, some solutions discussed in the megathread account for this worst case scenario. |
@jspenguin2017 Well but I don't trust to end Google corporation. They can make chaos with all Chromium project if they obligation will want for all Manifest 3. But... |
@seba2282 The Chromium project is open source, so Google is not able to force Chromium forks to switch to Manifest V3 only. Let's stay on topic, for further discussions about Manifest V3, please use the other megathread. |
@jspenguin2017 about Nano Adblocker, you can give mechanism which can remove all frustrated eu cookies from sites? |
There are already anti-cookie notice lists, if that's what you are talking about |
@llacb47 www.dobreprogramy.pl without extension I don't Care About Cookies, Ublock Origin/Nano Adblocker don't remove cookies. Suggest try that site. |
Try |
@seba2282 Nano has some abilities to remove cookie notices, but that is not the focus. You can open new issues in the Nano Filters repository regarding cookie notices but those will be low priority. This is getting off topic, open new issues for other general questions. |
@llacb47 I try when I be on PC @jspenguin2017 with fully respect. But your product after be few times and using by users, did can have special mechanism on remove cookies. Maybe to dedicated nano filters you give? Be in true. Cookies in EU are seriously annoying. I don't know how look that in USA and others continents. And I write in topic about Nano products. That function look nice for European user. Please look on my suggest. ☺ |
I cannot access/open any websites when Nano AdBlocker is turned on in Microsoft Edge Chromium. I also have Nano Defender Pro intalled. EDIT: Removing and re-installing the extension has fixed the problem (which was weird in the first place) |
@dhimanAdhikari That can happen when the installation files are corrupted. A reinstall usually corrects the issue. |
Nano Adblocker: https://microsoftedge.microsoft.com/addons/detail/epbkapkgcmdmfpogenoebpdeibmfinpf
Nano Defender: https://microsoftedge.microsoft.com/addons/detail/ijfkmnlofajajikjhfiigelipempcklj
Important: Both extensions are considered beta and may not work correctly. Be sure to report issues so they can be resolved, we can't fix issues that we aren't aware of!
The text was updated successfully, but these errors were encountered: