Hi everybody.
The new composer options are a great feature, but one customer would like to have these options hidden per default. I did not find a setting in the config file, nor is the user setting saved to the database, but only stored in localStorage or in cookie. So if a user closes his/her browser at the next message the composer options are visible again.
Am I missing something?
Thanks alot, Daniel
Ps: 1.0.0 really is a great build! Stable and cool features.
On Mon, Apr 14, 2014 at 5:11 PM, Daniel Rauer rauer@bytemine.net wrote:
Hi everybody.
The new composer options are a great feature, but one customer would like to have these options hidden per default. I did not find a setting in the config file, nor is the user setting saved to the database, but only stored in localStorage or in cookie. So if a user closes his/her browser at the next message the composer options are visible again.
With default settings, browsers don't clear cookies and localstorage entries upon closing. They're supposed to be persistent until you force-delete them.
This not only affects the compose options but also size and position of resizable boxes and other UI settings. In order to address this issue with non-standard behavior of your customer's browser, we should consider to introduce a new storage model for UI settings which can be configured to store settings on the server. This would probably make sense anyway but unfortunately isn't done with a 2-line patch.
You're welcome to open a ticket for this and add further ideas for a proper solution.
Kind regards, Thomas