It turns out that contrary to the API documentation, I am able to move a tab from an app-style window to a regular tab-based window. Not perfect, but it should help (and is also a good stopgap for the 1Password issue). Your message got me thinking, and I may have a solution. I agree with you that this limitation is annoying. This is an ironic limitation, given that one of my primary reasons for wanting a Chrome-based SSB in the first place is so that I can use Chrome's superior Developer Tools. The only option is to have them pop out as a separate window. on the right side or along the bottom of the window, as they can be in a normal Chrome window. Ultimately, a unified experience is what I'm looking for: one where the user need not make an up-front decision about whether an SSB is an "App Window" or "Browser Tabs" based.Īs an aside, another downside of Chrome's -app mode is that the Developer Tools cannot be rendered inside the app (i.e. Unfortunately, in a Chrome-based SSB, there seems to be no way to hide the location bar except by (1) running the browser in -app mode, which is an all or nothing proposition or (2) hitting CMD-SHIFT-F to enter full screen mode, which is almost never what I actually want.Īgain, these may be fundamental limitations for Epichrome based on its dependence on Chrome itself, but perhaps there's something I'm missing. The behavior described above is close to perfect. Again, once I've typed or pasted the url, I hit escape, and I'm back to a minimal layout (now with the two tabs visible):.This is no problem in Fluid, I just hit CMD-T and it brings up a second tab (or CMD-click on a link), prompting me for the location. Occasionally, I will want a second tab.When I'm done, I just hit escape, and the location bar hides itself again, restoring maximum real estate to the app.This is no problem, I simply hit CMD-L, and Fluid reveals the location bar, allowing me to do whatever I want. Occasionally, I will want to look at or directly manipulate the URL in the location bar for some reason.For example, the window I'm typing in now is a Fluid-based SSB for GitHub. Use that SSB with the address / tab bar hidden, so as to maximize screen real estate.My typical use case with Fluid is as follows: Iv'e read that it has been used on pontoon boats with success.This may be more of an observation than a bug report or feature request, per se, as I think I may be discussing fundamental limitations of Chrome as an SSB platform. I bought the Shark Hide to use on my new aluminum trailer. Both products will remain oily (it's lanolin after all). The FF you buy in regular cans or jars - meant to be brushed on - is quite a bit thicker. Note that the spray versions of FF are thinned for easier application. Fluid Film could never do that - it never really cures or hardens. They say it can last on aluminum boat hulls for a few years. It has solvents that evaporate out of the finish, so it has a "curing" behavior. From what I read about Shark Hide, it appears to be more of a sealant, and maybe a little more permanent. S219 wrote:Fluid Film is made from lanolin and is an oily product that never hardens or cures but does stay put by itself if not disturbed - it basically leaves a film that never dries out. ![]() I have never used FF on aluminum, but I am sure it would work well there too. One of the most used items in my shop is a can of FF with a brush built into the lid - it's a real convenient way to use it. I also use it on battery terminals and electrical connections on my trailers and boats (silicone grease is also great for that). It works great to leave a long lasting film that can lubricate and ward off rust. I have been using FF on my tractors, implements, tools, and equipment for years - mostly steel/iron stuff. ![]() Fluid Film is made from lanolin and is an oily product that never hardens or cures but does stay put by itself if not disturbed - it basically leaves a film that never dries out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |