Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - beastie

27
Otter Browser Forum / Re: how activate auto-completion
@Quetzal: if for some reason it has been changed in your local settings you can always find it on GitHub: https://raw.githubusercontent.com/OtterBrowser/otter-browser/082bc92f76ef9ce7b98db55230b8421c5355c46b/resources/searchEngines/google.xml
Normally you'd find this in Preferences > Search tab > Google > Edit... > Suggestions Query tab.

Is that what you're looking for?

Here it works fine both in the Search Field near the address bar as well as in the Search Field in the Start Page.
28
Otter Browser Forum / Re: visited link
For some reason the forum doesn't allow .html attachments, so I've renamed it to .txt.

The // hyperlink is parsed as file:// and results in a Network error 302 (Request for opening non-local file) error while the http:// hyperlink results in a Server not found error.
29
Otter Browser Forum / Re: Feature Requests
Quote from: larry on
It would be great to switch the browser engine while running Otter browser! So that you could easily view a page rendered be different web enginges (first using the default renderer, then witch to another one, maybe to another version etc.).
This is useful 1. If a pager isn't rendered correctly in a special browser engine and
2. This is especially useful for web developers who could easily test pages using different engines!
This would be a quite nice feature, right??

Or is this possible right now? As far as I know, the browser engine can be chosen (webkit or blink) at compile time, right?
You can switch between WebKit and WebEngine through the Backends/Web option in about:config. But I'm not sure you can switch live (I doubt it would even be feasible); you'll probably have to restart the browser.
Right now on Windows there's a separate "experimental" WebEngine version. So both browser engines are available for download. The WebEngine version is experimental because many features you take for granted in WebKit must be implemented manually in WebEngine. But I guess some time in the near future, both browser engines will be fully and equally supported and maybe we'll see them both bundled in the same setup. Or it may be too big to download, I don't know. You'll have to wait for @Emdek to shed some light on the matter.
On BSD and Linux, if you have fairly up-to-date packages you should already have access to both engines.

A much better alternative that is also readily available is to simply run two concurrent instances, each with it's own profile and cache directory (hint: --profile and --cache command line switches).
31
Otter Browser Forum / Disabling IFrames?
Hello all!

Opera used to have opera:config#Extensions|IFrames for disabling inline frames.

Does Webkit provide anything like it?
33
Otter Browser Forum / Re: a major crush
Quote from: exley on
funnily our OS used to be under our avatar
now yo have to hold your mouse to see it

as for otter, i wrote the version
I suggested that because this data is automatically detected by the forum software and can very well be inaccurate or outright false due to user-agent masking.

Quote from: exley on
as the engine, whatever it is by default...
It's WebKit, unless you've downloaded the so-called qtwebengine version available in the experimental directory on SourceForge.

Quote from: exley on
which btw i don't like, why does otter even include 2 types of engines ?
its just a mess how things are going,
Where you see a mess, others see freedom of choice - which is a tenet of free open-source software. Otter is actually a real gem for providing that choice. When choosing between these two you have to consider functionality, long-term support and potential privacy concerns.

Quote from: exley on
and even more complicated as
there is no straight-forward "to use just 1 thing"
At any given time, either you're using one or the other. What's so complicated or confusing?

For Windows, the default is WebKit and there's a special version (mentioned above) for WebEngine because you don't have these installed on their own and it takes forever to compile such huge projects as browser engines.
On other operating systems like BSD or Linux, these are already installed in the form of libraries as part of bigger projects (Qt5) and switching between the two is just a matter of choosing from the Backends/Web option drop-down box in about:config.
34
Otter Browser Forum / Re: a major crush
@exley, @szyk 

Adding your specs (OS, Otter version, WebKit vs WebEngine and Qt version) will be useful. I use Otter quite a lot on Windows and FreeBSD, both the latest version and an older one and I didn't experience more than flickering on the aforementioned website and have never had any problem on Google and any of its related websites.
35
Otter Browser Forum / Re: a major crush
You may also want to use the F12 menu to enable/disable JavaScript on the fly, since the website has a CAPTCHA system that requires JavaScript.
36
Otter Browser Forum / Re: a major crush
Okay, so it turns out I can't reproduce this even using the latest version. I did see some weird flickering effect in the advertising tab, but I was able to close the tab right away with MMB. And all the rest went well. No freeze and no crash whatsoever.

If you frequently use that website though I suggest you disable JavaScript using custom Website Preferences. This makes it load much faster and without any annoying interruption.
37
Otter Browser Forum / Re: a major crush
Are you using the latest version? Using an older version, I have no problem at all downloading a random .torrent file; and I'm not waiting 10 seconds or anything. I don't have the latest on this machine. I'll have to test tomorrow on another one.

By the way, what you've been experiencing is a crash. A crush is something entirely different (but something that may nevertheless be just as bad). ;)
39
Otter Browser Forum / Re: (Pre) RC 11 release (01.08.2018)
Quote from: larry on
Where has the "AppImage for Linux" gone?
No update since week 233...
Aren't they supported annymore?
Check the homepage as well as the OP above: it's not the "AppImage for Linux" only. If you notice on SourceForge, only 233 has it all (Windows/XP, Linux, DMG, etc.); after 233, it's just the README and the source code archive.

Quote from: larry on
Can anyone build the current RC and upload the binary to sourceforge (or wherever)?
Any reason you don't build them yourself? Genuine question, not trying to be snarky...

On FreeBSD, I usually track MASTER. It's super easy to build and takes just a few minutes on any hardware that's not more than a decade old.

As you may know, packages take a lot of resources to be built because they have all the libraries bundled together.
41
Otter Browser Forum / Re: youtube ??
A year or so ago, and for months in a row, I had to use the mobile version and mask as Chrome. Now I mask as Opera 12.

Also try both the WebKit and the WebEngine versions of Otter.
43
Otter Browser Forum / Re: SSL/TLS Certificate Issue - How to Ignore?
Quote from: pantoframe on
There must be an about:config edit or a box I can untick that will completely disable those
security warning messages.  Before I download and install Otter, I need a 100% certain yes
or no about disabling those messages.  If yes, give me the exact procedure.

I know a lot about browsers because I've used several dozen.  However, I am not a programming
expert.  I can easily edit about:config, but I cannot write code.  If there is a way to disable
those security messages it must be relatively simple.
.ini files are just configuration files. There's no programming involved at all. And anyway modifying them is only necessary if you want to customize/organize/optimize what Otter generates automatically.

You should get an error page when visiting some websites. If you click the Advanced then Load Insecure Page buttons, Otter will automatically add an entry for that domain to the file in this form:
Code: [Select]
[domain]
Security\IgnoreSslErrors="<Base 64 digest>"
45
Otter Browser Forum / Re: Containers, please?
Quote from: Pref on
Also, it means higher memory usage. We have six company's profiles on gmail to deal with different projects. Six browsers running?! And each of them deals with Google Docs differently?

Containers solve everything.
Not necessarily 6 different browsers, but 6 different instances of the same browser. This may seem like an over-complicated version of the containers idea, but in the mean time it does the job.
46
Otter Browser Forum / Re: disgusting look...
Quote from: smaragdus on
It is not the end of the world, I agree, it is just the end of my interest in Otter if the first stable release will not be shipped with an option to easily switch icons. The ugly icon set is a fly in the ointment which is ruining my browsing experience. It will be a pity if the developers let such a nuisance repel potential users (many former Firefox users are searching for alternatives).
It's the first stable release indeed, not the final version for all eternity. As you can see (in this very thread and on GitHub), even the way icon sets are loaded and displayed is still a work in progress and the whole browser is under heavy development.

Check these GitHub issues:

Just bear with it, keep in mind the limited manpower and in the meantime you can use the old icon set.
48
Otter Browser Forum / Re: disgusting look...
Quote from: smaragdus on
I cannot believe that there are no free icon sets better than the current one, even Oxygen will be fine if it can be used with new releases.
Please check my post from a year ago if you want to use Oxygen. You may be missing a few icons here and there, but otherwise it should work fine.

I don't like the "new" icon set that much, but other people like that kind of look. IMO it's not the end of the world. After all it's just what it is: an icon set. A browser is much more than that.
50
Otter Browser Forum / Re: User agent fonction
That's the whole idea behind user agents.

Web pages change their behavior (including how they look) depending on the browser (real or masqueraded) being used to display them.

The user agent feature basically allows the browser to masquerade as another browser.

So what's the problem here?