-
Notifications
You must be signed in to change notification settings - Fork 77
DOM inspector
q1800 edited this page Feb 8, 2022
·
9 revisions
uBlock Origin (uBO) comes with its own custom DOM inspector, to assist in the creation of cosmetic filters, as a complementary tool to the element picker and the logger. It can be accessed by clicking the </>
icon in the logger:
A custom DOM inspector -- rather than creating hooks into the browser's own DOM inspector -- has benefits:
- Portability: does no depend on specific browser API.
- Optimal: the UI is optimized to specifically deal with cosmetic filters.
Whereas the element picker is useful to interactively create cosmetic filters through point-and-click, the DOM inspector is useful to create cosmetic filters through the internal structure of the document in your browser. For instance this allows:
- To create very specific cosmetic filters by selecting an element directly in the DOM hierarchy.
- To create exception cosmetic filters.
- Locate the filter (red text) by moving mouse around in DOM inspector tree (elements on page should highlight, you will clearly see elements previously hidden now highlighted in red)
- Click on it (hidden element highlighting should change to green)
- Click on save icon in DOM inspector toolbar (floppy disk)
- Reload page
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers