Here's an interesting one for you guys... I had a user email me this morning saying his keysrc file stopped working after he upgraded from Dillo 2.2 to 3.0. Neither his existing keysrc nor a fresh one would work on his machine, while I couldn't reproduce the problem on mine. We just now discovered by chance it wasn't his keysrc that was the problem, but -- strangely enough -- that he had set start_page=about:blank in his dillorc. I've forwarded his original message below (with names and headers removed for privacy), which includes a more detailed explanation. I was just curious if anyone could reproduce this in mainline before I filed a bug report, or if this behavior was specific to Dillo-Win32. I don't have a Unix system handy now, or else I'd just test it myself. :-) Cheers, ~Benjamin ------- Forwarded message ------- I tracked down the source of the behavior and I think it should be reproducible now. In dillorc I had the following line: start_page=about:blank (By now you've probably figured out I'm a Firefox user..) Apparently Dillo 3 does not like for start_page to have this value, and will only load keysrc after a non-blank page is loaded?! This doesn't happen in Dillo 2.2 (20110630) but I'm not sure if this is an intentional change in behavior; probably not, considering the following weirdness: These values allow keysrc to be loaded without having to load a non-blank page: start_page=about:blank#any comment start_page= Sorry, I haven't had a chance to try any of this out in Linux, so still not sure whether this is an upstream regression.. For completeness my old cookiesrc, dillorc, and keysrc files are all attached (files that reproduce the artifact).