This is my very first post on HN. I have been working on this pet project for a bit over a year now. The motivation for it was simple: because I use my browser in a single, fully maximized window, many times I found myself switching back and forth between two tabs, for example to copy something from one website and use it on another. I know there are many extensions that can rearrange tabs for you, but I wanted something a little bit different. I really liked how picture-in-picture works for videos - I wanted to do the same!
Easy enough, I thought. I just need to create a new browser window, move the given tab into it, then... I just need to make it always on top. Right? Well, turns out, the browser API doesn't allow you to do that. So after a lot of trial end error, I came up with a way to achieve it: I implemented a small app in C++ that can manipulate the browser window and set the always-on-top property. Then "all I needed" was to hook it up with the browser extension and voila.
I also implemented a feature I call "Smart positioning": if you enable it, the extension will analyze the DOM structure of a given site and tries to identify the largest empty area and puts the floating tab there. This way, it doesn't cover up any text, pictures or videos. It more or less works :)
Sounds pretty simple, but I spent a LOT of time trying out different things. I use Linux, so naturally I implemented it for that platform first, but I knew it would never be useful for other people if there wasn't a Windows version as well - so I did that too. I worked on this project on evenings and weekends, and I learned a lot. This was my first proper pet project and I'm really glad I was able to see it through!
The extension is available for Chrome and Firefox, and you can use it on Windows and most Linux distros. The native application doesn't have an OS/X version - sorry :) I don't own a Mac and I don't know anything about the Apple ecosystem. I'm looking for help in that department, if you're interested! :)
Reminder: in addition to the browser extension, you must also install the native application (called Companion).
Chrome Web Store: https://chrome.google.com/webstore/detail/iojgbjjdoanmhcmmih...
Firefox Addon: https://addons.mozilla.org/en-US/firefox/addon/tabfloater/
On the other hand, my desktop is 2560 pixels wide, and as a result, I've never had the need nor desire to maximise anything. I also rarely use multiple tabs, preferring separate windows instead, which I can then arrange as I please. I wonder if the popularisation of tabbed browsing has decreased the desire/visibility of comparing/contrasting in general, since as you mentioned, it is much more difficult when you can only see one site at a time.
I prefer to think of TabFloater as not an app that creates/moves/manipulates extra browser windows (even though that is what actually happens), but an app that adds an extra browser functionality (picture-in-picture). In this sense, I think it makes sense that it brings its own "always-on-topness".
I'm also aware that this app solves a pretty niche use-case - but it was fun developing it and I learned a lot!
edit: for the curious https://i.pinimg.com/originals/44/3a/7b/443a7b1de502069e3fa9...
What I was going to give feedback: An ability to locate the bin file from settings in the extension would be good, as I can't modify the registry.
As for your actual feedback: there is no way to achieve this from the extension. The extension doesn't know where the companion executable is - it is the browser that connects the two applications.
However, you can enable debugging, then you can open the companion log file, which will contain the path to the executable.
Out of curiosity, why do you need to know the location? What were you trying to change in the registry? Is this the reason you uninstalled it? Maybe I can help.
If you'd like to experiment, you can change the register script to put entries into HKCU instead of HKLM. It might just work!
I have https://github.com/tabfloater/tabfloater/issues/189 open in case there are any OS/X devs are here :)
There is a very interesting comment from one of the developers on the removal bug (https://bugs.chromium.org/p/chromium/issues/detail?id=467808):
> While closing this issue as "Fixed", I feel I need to offer a couple of words of personal explanation to the users of Trello who were directed here by the developer of the app, as well as others who can be interested.
> I'm the original developer of Panels in Chrome, and I'm the engineer who's lead a team to maintain them. I also finally removed them. Panels were a part of my life in form of time, thoughts, inspiration and passion. Our initial plans were to enable panels to all apps which wanted to use them, and we saw how those can be useful of course. It is with sadness but also with appreciation of the experience that I had to remove the feature from Chrome M54.
> The time passes and things change, we all learn. In case of Panels, we "proved" by practice that it takes a team of a few engineers full time to be able to catch up with teams of OS developers in Windows, OSX, Linux and even our own ChromeOS. The window management and graphics/input subsystems are constantly evolving and it is more or less prohibitively expensive for a small team to try to build and keep a high quality but non-standard window management mode. OSes have too many mechanisms that are linked to a specific windows behaviors (focus, window switching, active windows treatment, titlebars, where input goes, shortcuts, animations, multiple desktops, other OS gadgets etc), and usually OSes do not provide 'hooks' or APIs to integrate with those, which makes it necessary to 'reverse-engineer' and hack around. While it can be done, it quickly leads to 'card house' design that falls down even easier with the next major OS update... So the costs of development and testing rise.
> There was another factor that kept us from enabling panels for all apps. The specific UI Panels provide does not scale well if/when multiple apps are using it. It is very easy to get in trouble with multiple always-on-top windows popping up from multiple apps. Several independent apps using panels at the same time actually makes the interface annoying and hard to control. We had several apps using Panels at the same time and it was hard to manage windows because they were all intermixed. There were several design ideas on how to build some 'panel managers' and corresponding APIs but they increased the complexity significantly, especially considering those would be in addition to APIs OS provides for other windows. So we never were able to enable it for every app.
> Now, if the major OSes would adopt the concept and built into their window managers, it'd be much much easier to support it in Chrome. But it's not the case, except for ChromeOS where panels stay.
> So at the end, this was a great experiment. We are now way past the point where additional discussion can move the needle much. Google Hangouts app had millions of users and some of them loved Panels. Apparently Plus for Trello has passionate followers. The YouTube viewers is a neat idea. But we all need to move forward, the platforms change much faster and generally to the better :) Hope developers of your favorite apps will figure out even better ways to implement great UI their users demand!
I was also contemplating removing the borders and title bar of the floating window, so that it would much more like a panel, but on Windows, Chrome actually draws its own title bar, so you cannot remove it using the Windows API.
I can imagine some complexity as explained. But for example it seems reasonable to me to limit browser panel/PiP support to a single element at a time like it is now for video to avoid some of that.
This looks interesting!
I have not yet experimented, but perhaps a video element can be styled or injected with HTML/CSS to present non-video content.
I've used AutoHotKey for over a decade to do always on top switching.
;CTRL-SHIFT-SPACE switches the current window always on top
^+SPACE:: Winset, Alwaysontop, , A
Find AHK here: https://www.autohotkey.com/
AHK is open source, if you want to take a look at, here: https://github.com/Lexikos/AutoHotkey_L
You could of course move the window next to your main browser window - but, you would need to first open a new window, move your tab into that window, resize and position it manually... it's tedious.
with TabFloater it's just one click :)
Also, don't forget you have Smart Positioning :) That feature is pretty powerful IMO.
(Joking aside, this looks useful, thanks!)
This is way better than what any window manager can do.
Also, the required companion exe app on Windows was blocked twice: once by Firefox and then again by Windows.
As for the usage stats: if enabled, it sends data to Google Analytics, stuff like how many people installed it, how many people used X or Y feature. It really only exist to help me track how people use it.
It is of course completely up to you if you want to disable it - but as with any product, usage stats just help developers make the product better.
I knew these tiling managers exist for tabs, but I wanted to take a slightly different approach on multitasking. TabFloater is primarily useful if you use your browser in a single-window mode. Within one window, it's impossible (AFAIK) to arrange tabs the way you mentioned, you would need separate windows. If you'd like that functionality, the above linked extension should work great.
On i3 it looks like this add-on essentially automates opening the tab in a new window, and floating it. Which I think has some value.
If you meant an unintentional security issue, then I think we are still good. The only thing the extension communicates to the native application is the title of the current browser tab, which is arguably personal information. However the native application is running on your machine, and you chose to install it. There's no way for remote machines to get your info this way. The only scenario I can see for leaking private info is if someone creates a malware that mimics TabFloater Companion and somehow manages to get it on your machine without you knowing. Then, they will get the titles of the sites you use TabFloater on. There are so many better ways for attackers to get the same information - I think this risk is negligible.
Of course, if you see any other issue that I might have missed, do let me know!
This should be an original logo though - not made by me, but made explicitly for this project by someone.
"Always on top" is standard in KDE
Three reasons this is different:
1. The window is actually not on top of every window - it's only top of your browser. It's "attached" to your browser window, same way a real PiP would.
2. It's less clicks and also positions the window automatically for you.
3. It's cross platform. Windows doesn't have an easy user-accessible way to enable always-on-top.