80
edits
Firefox/Feature Brainstorming: Difference between revisions
Jump to navigation
Jump to search
→Address bar
| Line 719: | Line 719: | ||
Like in Opera browser<br> | Like in Opera browser<br> | ||
- Middle click already does this if you turn it on (and it's on by default on Linux) | - Middle click already does this if you turn it on (and it's on by default on Linux) | ||
[https://bugzilla.mozilla.org/show_bug.cgi?id=216667 bug 216667] | |||
</td></tr> | </td></tr> | ||
<tr><td> | <tr><td> | ||
| Line 2,120: | Line 2,122: | ||
**To secure a process on Linux, simply write to the /proc/self/seccomp file. The process will then only be able to communicate via existing file descriptors (be sure to close the X11 one) and existing shared memory regions. Only about four system calls are allowed for a process in secure mode: read, write, exit, and signal handler return. | **To secure a process on Linux, simply write to the /proc/self/seccomp file. The process will then only be able to communicate via existing file descriptors (be sure to close the X11 one) and existing shared memory regions. Only about four system calls are allowed for a process in secure mode: read, write, exit, and signal handler return. | ||
* Provide an about:top view that gives an accounting of which documents and plugins are using how much memory and CPU time. | * Provide an about:top view that gives an accounting of which documents and plugins are using how much memory and CPU time. | ||
* Provide a centralized UI for dynamically charting how much CPU and memory is used by each tab. As many tabs being opened, it gets hard for none script avid users to hunt down wich tab is causing firefox to drain up system resource. With a centralized UI, every user would be able to find out which tab/site is causing resource drainage | |||
</td><td> | </td><td> | ||
n/a | n/a | ||