15
edits
Paulmcauley (talk | contribs) |
|||
| Line 475: | Line 475: | ||
* Ability to split the browser window vertically or horizontally, similar to emacs windows, and load different urls into each. Common usage cases for this are when you want to see two different pages at once conveniently, monitoring multiple sites at once, etc. | * Ability to split the browser window vertically or horizontally, similar to emacs windows, and load different urls into each. Common usage cases for this are when you want to see two different pages at once conveniently, monitoring multiple sites at once, etc. | ||
** Simply allow to split the window vertically with the same page for working with long pages, as in Visual Studio .NET. | ** Simply allow to split the window vertically with the same page for working with long pages, as in Visual Studio .NET. | ||
* UI-level Multicolumn mode, like Emacs Follow mode - split the browser window into two (or more) panes, showing the same page, the right pane leading on from the left pane. Excellent in these days of wide monitors and inexplicably narrow fixed-width web pages! | * UI-level Multicolumn mode, like Emacs Follow mode - split the browser window into two (or more) panes, showing the same page, the right pane leading on from the left pane. Excellent in these days of wide monitors and inexplicably narrow fixed-width web pages! | ||
* Similar to above - many web pages consist of div/table elements of less than 800 px which are aligned to the left of the screen. With a large monitor of >1600 px the entire right-hand side of the screen is wasted whitespace. Add a button to automatically paginate the display into columns if a width of e.g. <800 px is detected. Pages could also be progressed through one at a time with previous/next buttons on the scrollbar or in a similar way to Adobe Reader/existing browser print preview functions. | |||
* Text readability improvements: 1)button/keybind to automatically narrow text to a pre-configured width - text extending accross the whole width of the window is cumbersome to read - possibly configurable to multi-column mode; 2)"Visibility imprint" - on quick scroll operations (PgUP, PgDn, mousewheel...) the previously visible area should be delimited by a frame/line for a certain period of time, after which the frame disappears or fades out, so it's easier to find the last read line; and 3)Improved automatic scrolling: finer control for very slow scrolling and freeing up the mouse. Like current autoscrolling, only finer controls (the current slowest is still too fast) and the possibility to detach the mouse, for instance by re-clicking the middle button, upon which the mouse is free to move but the page continues autoscrolling. | * Text readability improvements: 1)button/keybind to automatically narrow text to a pre-configured width - text extending accross the whole width of the window is cumbersome to read - possibly configurable to multi-column mode; 2)"Visibility imprint" - on quick scroll operations (PgUP, PgDn, mousewheel...) the previously visible area should be delimited by a frame/line for a certain period of time, after which the frame disappears or fades out, so it's easier to find the last read line; and 3)Improved automatic scrolling: finer control for very slow scrolling and freeing up the mouse. Like current autoscrolling, only finer controls (the current slowest is still too fast) and the possibility to detach the mouse, for instance by re-clicking the middle button, upon which the mouse is free to move but the page continues autoscrolling. | ||
* Allow 'drag & drop' of links anywhere on the browser window (not just the tab bar) to open the link in a new background tab (e.g. 'drag & drop' links from Google Search Results/Google News/Digg Front Page etc. to open several background tabs) | * Allow 'drag & drop' of links anywhere on the browser window (not just the tab bar) to open the link in a new background tab (e.g. 'drag & drop' links from Google Search Results/Google News/Digg Front Page etc. to open several background tabs) | ||
edits