Browsers future.
1. Browser parameters.
Current URL to going Chrome parameters is chrome://about/ - this is common enter to investigate all chrome parameters.
![](Chrome-1_1.png)
The same common entering point to tuning Firefox is about:config.
![](Firefox-1_1.png)
Also Firefox has a lot of parameters as simple JSON file, for example this is own tuning protocol handler on Browser:
![](Firefox-2_1.png)
2. Support forum.
Firefox has cool support forum, you always can ask something about Firexox, for example this is my post in that forum https://discourse.mozilla.org/t/ns-binding-aborted-why-browser-unexpectedly-transform-post-request-to-get-request/122848
Chrome also has similar community https://support.google.com/chrome/threads, but I'm not active Chrome user.
3. Plugins.
This is list of my liked FF plugin.
![](Firefox-3_1.png)
4. Tune Dev tools.
Main future for developers of Dev Tools is two "Chromium compatibility" and "Remote debugging".
![](Firefox-4_1.png)
5. Direct call Socket inspector from command line.
6. Opening port.
7. Forbid Search engine.
sorry, no time ...to be continue soon ...
Related page:
- (2024) Google Cloud and Cloudflare
- (2023) CloudflareWorker and Supabase
- (2022) JS, Css
- (2022) Typescript, Webpack
- (2022) Angular, RxJs, Firebase, MongoDb
- (2022) Node, NestJs, Electron, Pwa, Telegram
- (2022) React, Redux, GraphQL, NextJs
- (2022) Angular/Typescript, JS books
![](http://forum.vb-net.com/GetTopicCount.png?id=44bce4ce-3694-44b5-b405-d9ea3e81361c)
<SITEMAP> <MVC> <ASP> <NET> <DATA> <KIOSK> <FLEX> <SQL> <NOTES> <LINUX> <MONO> <FREEWARE> <DOCS> <ENG> <CHAT ME> <ABOUT ME> < THANKS ME> |