Adblock Plus のレビュー
Adblock Plus 作成者: Adblock Plus
合計レビュー数: 11,371
- 5 段階中 1 の評価Firefox ユーザー 10043150 によるレビュー (8年前)Version 3.0 is a disaster. The developers must be getting paid by a competitor to destroy their product. It has become useless. Now even Tools in Google Search is blocked, can't change language and period anymore. Ridiculous.
開発者の返信
投稿日時: 8年前You can read up on the background of this update here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension. If you have issues, our forums is where you can get help. - With the current ABP and Firefox 56.0.2, if I click the Firefox Home icon, the URL is cleared but the contents of the page remain. My Home setting is about:blank, so the page should be cleared. I have two possible workarounds. (1) Disable ABP. I would prefer not to do that. (2) Close the tab for the page that did not get cleared and open a new tab with a blank page.
- 5 段階中 5 の評価Firefox ユーザー 13416886 によるレビュー (8年前)
- 5 段階中 2 の評価Firefox ユーザー 13416786 によるレビュー (8年前)After the latest ABP update the firefox is taking too much memory (1gb+ )... never had this problem with 2.x.x versions ...i dont have any other addons installed in my browser so i suspect this is an ABP issue
- 5 段階中 1 の評価Firefox ユーザー 13416703 によるレビュー (8年前)Seit Update am 06.11.2017 unbrauchbar. Man kann ABP nicht mehr vorübergehend komplett ausschalten.
- 5 段階中 1 の評価Firefox ユーザー 12486790 によるレビュー (8年前)wow - I cant believe that the developers ruined this app with the last update! All the previous functionalities are gone! you can't even unblock items that you mistakenly blocked.
開発者の返信
投稿日時: 8年前You can read up on the reasons here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension - 5 段階中 1 の評価Firefox ユーザー 13416370 によるレビュー (8年前)Mais que se passe t'il avec Adblock, la nouvelle version est franchement nul, pourquoi avoir changer ?? Je ne comprend pas ce changement brutal ! Quelqu'un a une idée pour ajouter un autre bloqueur de publicité ?
開発者の返信
投稿日時: 8年前You can read up on the reasons here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension - 5 段階中 1 の評価Firefox ユーザー 13416366 によるレビュー (8年前)The last update makes ABP into a complete garbage. What on earth is going on in the developer's head?!
開発者の返信
投稿日時: 8年前You can read up on the reasons here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension - 5 段階中 1 の評価google_crawler によるレビュー (8年前)What the hell append here? From one of the most useful addons it turned into some chromefied useless piece of dung. It doesn't even serve its basic function now. No option to view and block blockable elements on the page. Extremely disappointing..
開発者の返信
投稿日時: 8年前You can read up on the background here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension. As to blockable items, this was replaced by a Developer Tools panel - press Ctrl+Shift+I (Cmd+Option+I on macOS) to open Developer Tools, then switch to the Adblock Plus panel. You might need to reload the page, requests performed before the panel was opened aren't being displayed. - Cette nouvelle version de Adblock Plus compatible avec Firefox 57 est décevante. D'abord la fonction pour bloquer des éléments sur une page ne fonctionne tout simplement pas ensuite le choix de liste de blocage qu'on peut ajouter est très réduit et pour terminer les fonctionnalités des options ne sont même pas toutes traduites (en l’occurrence (en français). Avoir pris tout ce temps pour ce résultat décevant, honnêtement ça ne valait pas la peine.
開発者の返信
投稿日時: 8年前We are aware of the issue with the Block Element dialog and are investigating it. You should expect it to be addressed with a follow-up release soon. You can still add any filter list you want, nothing changed here (you can use the links on https://adblockplus.org/subscriptions for example). As to missing translations, everybody is free to help out with those on https://crowdin.com/project/adblockpluschrome and https://crowdin.com/project/adblockplusui (strangely, French is supposed to be 100% translated). - 5 段階中 4 の評価Firefox ユーザー 12450292 によるレビュー (8年前)Is it possible to change the colour of that icon number? It's almost invisible...
http://up.picr.de/30882107cl.jpg
.開発者の返信
投稿日時: 8年前That appears to be an issue with the Firefox theme you are using. It's a generic icon badge, we don't determine its color. For me, it's perfectly readable. - 5 段階中 5 の評価Firefox ユーザー 6116640 によるレビュー (8年前)
- 5 段階中 1 の評価Firefox ユーザー 13415449 によるレビュー (8年前)Had to downgrade to previous version. No open blockable items menu and incompatible with element hiding helper. If it is not broken then don't fix it.
開発者の返信
投稿日時: 8年前Blockable items list has been replaced by a Developer Tools panel - press Ctrl+Shift+I (Cmd+Option+I on macOS) to open Developer Tools, then switch to the Adblock Plus panel. A move obvious way to open it would be great but sadly currently not possible (we filed a Firefox bug on that a year ago). You might need to reload the page, requests performed before the panel was opened aren't being displayed. As to Element Hiding Helper, it's sadly not possible to make it compatible with Firefox 57 but we want to incorporate parts of its functionality in Adblock Plus later. - 5 段階中 3 の評価Firefox ユーザー 13415425 によるレビュー (8年前)This add-on is no longer worth using. The updated UI is horrible, complete with social links added in. The user functionality has been seriously reduced, a list of commands is gone and been replaced by an inept alternative. Until the latest update has been reverted, do not use ABP.
EDIT: Turns out the developer is right, this isn't the fault of the add-on dev but mozzila themselves. I will be using an earlier version of firefox to combat this.開発者の返信
投稿日時: 8年前Reverting the update is not an option that is available to us, only improving the current state. You can read more about this under https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension 開発者の返信
投稿日時: 8年前Blockable items list has been replaced by a Developer Tools panel - press Ctrl+Shift+I (Cmd+Option+I on macOS) to open Developer Tools, then switch to the Adblock Plus panel. A move obvious way to open it would be great but sadly currently not possible (we filed a Firefox bug on that a year ago). You might need to reload the page, requests performed before the panel was opened aren't being displayed. As to Element Hiding Helper, it's sadly not possible to make it compatible with Firefox 57 but we want to incorporate parts of its functionality in Adblock Plus later.- 5 段階中 3 の評価jorvnx10624 によるレビュー (8年前)The Blockable Items Window must back!
Adblock better than ublock because of The Blockable Items Window show links in real time.開発者の返信
投稿日時: 8年前Blockable items list has been replaced by a Developer Tools panel - press Ctrl+Shift+I (Cmd+Option+I on macOS) to open Developer Tools, then switch to the Adblock Plus panel. A move obvious way to open it would be great but sadly currently not possible (we filed a Firefox bug on that a year ago). You might need to reload the page, requests performed before the panel was opened aren't being displayed. - 5 段階中 1 の評価Firefox ユーザー 13415357 によるレビュー (8年前)Love v2.x, but this new v3 is absolute garbage. Not exaggerating... it's the worst update in the history of the program. I actually had to restore the older version from backup and shut off updates because it was so bad. The interface has gone from power user friendly to toddler friendly. Important features to allow custom filters have been removed entirely, or made so rudimentary as to not even bother. Wow. Who ever thought v3 could possibly be a good idea? I'm dumbfounded at the horrible interface. Just... so bad. Avoid this version like the plague. Do not attempt to upgrade if you're lucky enough to still be on v2.x.
開発者の返信
投稿日時: 8年前You can read up on the background here: https://adblockplus.org/blog/the-plan-towards-offering-adblock-plus-for-firefox-as-a-web-extension. While we'll keep improving the current state and add missing features back, going back to the old codebase sadly isn't an option.