
![]() |
The (current?) inbuilt tab interface of Haiku may not work too well in a browser? What about allowing for persistent and "faviconized" tabs? Very useful nowadays ("webapps"). Is the approach of Google Chrome really more fruitful? |
![]() |
Possibility of adding bookmarks to any toolbar, and/or to it's own dedicated one (like Firefox)? Using the default bookmark "format" of BeOS, storing them as files in a folder, so they can be shared amongst different browsers (for example). |
|
Popular Firefox addon: FaviconPicker (let's the user pick a custom favicon for each bookmark) combined with the possibility of removing the bookmark label (very useful when adding a lot of bookmarks, especially on low resolution displays). |
![]() |
Stylish and Greasemonkey are both two very useful and popular additions to Firefox, and could be to WebPositive as well. Easy, built-in, support for the thousands of userscripts and userstyles available would be great. With support built-in, we could have an easy way to add both userscripts and userstyles in a "unified" manner (see mockup). It would just need a name that would clearly indicate it's purpose. Styles and scripts should also be stored as files, so that they can be easily shared between computers (which also would make it easier for backup, as for bookmarks). The scripts/styles stored as files would maybe render this interface useless? (I don't know if this is even would be possible, though I can't see any reason why not) |
|
Firefox has it's AdBlock addon, which is probably one of the most popular addons available. I believe that AdBlock has purposes other than just blocking ads. It allows for blocking
any element you want. This can of course also be done by Stylish/Greasemonkey, but AFAIK, they only "hide" them. It's possible that AdBlock just hides the elements as well,
but I'm under the impression that AdBlock keeps the elements in question from downloading at all. That is most definitely useful. I understand that this is somewhat problematic (after all, most commercial internet sites depends completely on advertisement revenue). An element blocking feature don't have to be advertised as an AdBlocker per se, and besides: If we are to respect ads, then we should demand respect in return (FLASH FLASH FLASH .. YOU JUST WON 1.000.000.000, CLICK HERE!! .. FLASH FLASH FLAHS). (When watching TV we are luckily still allowed to mute the sound during commercials). This could be implemented in the right click menu, "Block this element/frame/whatever", and by providing a simple list of blocked elements, maybe something like:
* Annoying-Site-Which-I-Still-Need-To-Visit-From-Time-To-Time.com |
![]() |
Combined refresh page/stop loading. Saves space and keeps the interface minimal. |