Components
List of components in Dot Browser to easily identify what went wrong in bug reports.
Last updated
Was this helpful?
List of components in Dot Browser to easily identify what went wrong in bug reports.
Last updated
Was this helpful?
Anything that affects the accessibility of the browser.
Example issues for this component could be: UI bugs in the Adblocker extension, false positives in the block lists or sites which might need to be added to the block lists.
If your issue occurs in that component, it is most likely valid.
Example issues for this component could be: problems with parsing exported bookmarks files, problems with the bookmarks bar.
If the issue occurs in that component, it is most likely valid.
Example issues for this component could be: issues with building on your platform, issues with bootstrapping, build issues.
If the issue occurs in that component, it is most likely valid.
As DevTools is a large component, we have divided each section into sub-components. Make sure you state which sub-component the issue is occuring in, inside your issue.
Any issues with accessibility in the DevTools UI.
Any issues with the "Application" tab in DevTools.
Any issues parsing code or UI issues in the "Console" tab.
We do not accept issues which are reproducible in other browser engines as it probably functions as intended and is not an issue.
Any issues with the "Debugger" tab in DevTools.
We do not accept issues which are reproducible in other browser engines as it probably functions as intended and is not an issue.
Any issues with the "Inspector" tab in DevTools.
Any issues with the "Memory" tab in DevTools.
Any issues with the "Network" tab in DevTools.
Examples of issues for the Network sub-component could be: issues parsing headers, issues parsing the body, etc.
Any issues with the "Performance" tab in DevTools.
We do not accept issues which are to do with your website's performance. However, if the issue is reproducible on other websites we may accept it.
Any issues with the "Storage" tab in DevTools.
Make sure you redact any personal information like cookies, session tokens, etc.
Any issues with the "Styles Editor" tab in DevTools.
Example issues for this component could be: issues with downloading files, bad file formats, reporting false positives for the malware-detection.
If the issue occurs in that component, it is most likely valid.
If the issue occurs in that component, it is most likely valid.
Any issues with renderering web pages, compatibility issues (works on Chromium-based browsers), or anything broken in the Gecko browser engine.
If the issue occurs in that component, it is most likely valid.
If an issue occurs in that component, it is most likely valid.
Any issues with the icons in the browser.
If an issue occurs in that component, it is most likely valid.
If an issue occurs in that component, it is most likely valid.
Any issues with the Awesome Bar (primary search bar) or the secondary search bar.
Issues with the built-in search engines or the search engine system in Preferences can also count for this component.
If an issue occurs in that component, it is most likely valid.
Any issues with the Settings Web UI (about:preferences). We also count issues in the Configuration Web UI (about:config).
If an issue occurs in that component, it is most likely valid.
This component has no information yet. Sync server is still a work in progress.
Any issues with the Tabbar, Tab switcher (Ctrl+Tab) or Tabs overflow list.
If an issue occurs in that component, it is most likely valid.
Any issues with the look and feel of the browser (bad styling, awful UI on 3rd party themes).
If an issue occurs in that component, it is most likely valid.
Any issue with the extensions in the .
Any issues with the Dot Browser version of .