1
Otter Browser Forum / Re: Logging in to Github
But today it's gone back to not working. These companies are as efficient as the government. I wonder how they're still in business.
This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.
the new tab do not gives acces to the home pageForget about the New Tab button. Use the Home button instead, every time you want a new tab.
the homepage button do not open a new tabIt does exactly that here using the default configuration. To demonstrate this:
"OpenLinkInApplicationAction",line in the
"includeIn": "link",section?
"identifier": "SideBar",
[...]
"panels": [
"bookmarks",
"history",
"notes",
"passwords",
"transfers",
"addons"
or i have to make a new serachengine for any language of this websiteThat's what I do. How can Otter know the language of the word you're searching for?
but i know why i havn't seen it...There is!
there's no specific command in keybord shortcuts preference to open/close it in a keypress...
If you open 91 tabs in a Chromium and it's only using 5 GB, consider yourself lucky.Ha! Exactly right!
also, i noticed that while smooth scrolling exists, there are no options how many lines to skipBetter open a ticket for a feature request on GitHub.
by default it goes 1 by 1 and that is rather slow scrolling
why would people need to press F-buttons ?No. The F11 is only needed if you don't want to override settings. When Otter says YouTube "wants to enter full screen mode" select "Always allow". This will change the Website Preferences for YouTube and you'll never ever have to do anything other than click the fullscreen button (or press "f") ... just like in any other browser.
or ANY buttons ?
this should automatically work like in any other browser ...
hmm why doesn't youtube have fullscreen modeIt has. Click the "fullscreen" button on YouTube and press F11 to enter Otter's fullscreen mode and the video will be the only thing displayed on your screen.
can the top bar be removed ?
2. Tabs stacking.+1. Tab stacking is the single feature that I miss the most.
3. I imported an opera session and opened it (in the existing window/session). Wow that took a lot of time. An boy was the RAM footprint big - 5 times as big as in opera 12 at the same time! And when closing all the additionally opened tabs of the imported session and going back to only the tabs that where already open before, the memory footprint was still more than half of the max. footprint. (We're talking here going from 3 tabs to 91 tabs and back to 3 tabs. And memory-wise from about 200MB to over 5GB (!) and then down (only) to about 3,7GB (!))Otter is most likely not the culprit here. Barring any possible memory-leak bug, Otter itself is no more heavy on resources than your average application. Like any other web browser, Otter is just an interface for the layout and ECMAScript engines.
Not a very extensive test but still enough "data" for me to conclude that for me otter isn't quite there yet to replace opera 12 but it's getting closer.
Weekly report #263 (2019-01-14)While this is not very informative, these entries clearly imply the situation is temporary.
Almost there
[...]
Weekly report #262 (2019-01-07)
Still working to resolve the packaging crisis
[...]
1.0.01 release (2019-01-01)
[...]
AppImage for Linux, 64 bit (pending);
DMG for macOS (pending);
installer for Windows 7 or later, 32 bit (pending);
installer for Windows 7 or later, 64 bit (pending);
I guess that only fear of legal repercussions prevents them from publishing their own rendering engine based on that code.1. Probably it requires too much work to raise it up to be on a par with today's industry standards and that much work isn't worth anyone's time.
I have a idea. Lets go knock on Opera's door (in China) and tell them since your not using it hand over Presto! Hell the Chinese have stolen enough codes from everyone. Are just maybe, GitHub has a old copy of the source code laying around.
Great idea! I doubt that the source code has been forgotten somewhere in the open (it would have been found out by now) but it could be that, asking the right person, the source code might be handed over to us just soActually it was on GitHub (illegally of course) about a year or two ago and the repository was forked a few times before everything was taken down.