I use custom filters, but it is mostly for quickly testing filters or adding temporary filters or something more specific to my Device, I have a bunch of lists that I made, especially if I want to use Edge or something, I can easily load them in uBlock. Latest nightly added Expires: support, so now the lists won’t automatically update only every 7 days.Īlso, you make changes to the filters by using a proper text editor rather than Brave’s custom filters box.įor example, Visual Studio Code has an extension by Adguard team, it has support for ABP, Adguard and uBlock syntax which Brave uses.Īlso it has multicursor editing and a bunch of other extensions, or well, just the search/replace function with regex support is enough to want to use a text editor rather than custom filters. The process of updating list should be better soon, in couple Stable updates. I think It’s just easier if you made a github account or something like that and made your custom lists instead of having them as custom filters, that way you can just copy and paste a link and update the lists when necessary.
With the Sync, you should be able to see the code,, and all you do is save it somewhere safe, then if you need to recover it, take the first 24 words and then replace the 25th by the daily word you can find here and done. So for example you use #:root:style(color-scheme: only light !important ) for the whole page or #my-element:style(color-scheme: only light !important ) per item.īrave doesn’t allow generic cosmetics like that, so it has to be done per domain. and it can be done per item or the whole page, you can look at this for how it works. If you want to personalize the auto-dark mode, then use the Adblocker with the :style() rule to inject the color-scheme: CSS property. Use CIELAB mode in brave://flags/#enable-force-dark it is the only good mode, there is Enabled with selective inversion of non-image elements but it works just like CIELAB.
0 kommentar(er)
