Am 03.01.2014 19:29, schrieb A.L.E.C:
On 01/03/2014 07:13 PM, Michael Heydekamp wrote:
That's driving me nuts even more. Any hint...?
Classic skin uses cookies. Larry uses window.localStorage. Could you check with Larry?
Some hints for classic: see lines 8-18 of skins/classic/templates/mail.html. As you can see here, the elements height/position is set by PHP by reading cookie values.
To see cookies in Firefox goto Tools > Web Developer > Web console, choose Network tab, reload the page, select first GET request on the list, select Cookies tab on the right.
Thanks for those hints. I didn't check with Larry yet, although I would prefer that Classic would use use window.localStorage instead of cookies too. Is there a special reason why both skins are doing it different, and are you planning to use window.localStorage for the classic skin in the future as well?
Anyway, we've found an interestingly solution/workaround:
First, we deleted all FF cookies with SQLite Manager. Much to our surprise, that didn't have any effect.
After some playing around, we realized the following: Invoking Roundcube on our server with...
a) http://www.webmail.freexp.de: Splitter settings were neither being saved nor respected. Always the same odd default values did apply.
b) http://webmail.freexp.de: Splitter settings were being saved as well as being respected.
For IE, that doesn't make a difference apparently. For FF, it does. So we'll be solving this on our server.
Nonetheless it's still unclear where FF got those odd default values (where the splitter positions have always been reset to) from, when being invoked with the "www." prefix. Probably some ancient IE cookies, and due to the slightly different rendering of both engines, it made this annoying scrollbar appear in FF...?
Anyway, not a Roundcube issue apparently. But feel free to comment, though. At least we were quite surprised of the above.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany