Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[10.0.01] UI configuration not being kept #1566

Open
birdmanravo opened this issue Feb 21, 2019 · 2 comments
Open

[10.0.01] UI configuration not being kept #1566

birdmanravo opened this issue Feb 21, 2019 · 2 comments

Comments

@birdmanravo
Copy link

Using the latest version in Fedora the browser does not keep any changes made to the UI. You can duplicate this behavior by moving the tab bar to the bottom of the window, then closing Otter and reopening it. The tab bar will be placed back in the default location. This also happens on Ubuntu using the latest version to have an Appimage released. There's no obvious way to save the UI's configuration and ~/.config/otter/toolBars.json is blank except for two brackets and a line break.

@birdmanravo
Copy link
Author

I'd like to add that copy & pasting toolBars.json from the master branch here on github and editing it can be used to circumvent the issue, but here in Otter clicking the "edit" button on my first comment does absolutely nothing. Still, it seems like toolBars.json is not being written to when Otter closes. I tried changing the permissions so anyone could write to it with no effect.

@Chromace
Copy link

Chromace commented Feb 22, 2019

I believe that Otter keeps its UI configuration in the sessions folder at the moment. As a result, if you set the startup behaviour to restore the previous session, the UI configuration will be saved. Of course, it would probably be better to have that sort of thing to be permanent, so even if the startup behaviour of Otter is different, it would be remembered. As a current workaround, I make the restored session read only, which essentially duplicates any of the other startup settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants