Us losing some settings when the user actively switches back and forth between languages is very different from (and less problematic than) losing settings during an update. 'Google'), but that's not something we should attempt to do in a dot release. If you would prefer to Use custom settings for history, make sure that Accept cookies from sites is selected. In the History section, select Remember history. Click the Options button, or expand the Options menu and then select Options within it. We may want to try to preserve the settings automatically for engines that have the same name for both languages (eg. Mozilla Firefox 45.0 and above (PC): Click the Firefox drop-down menu. If you see true below the value heading thats on the right side of the page, JavaScript is currently enabled this is the default Firefox setting. When you switch to a different language pack, you switch to a different set of default search engines, so settings can't really be kept, or at least not all of them. However, 'NoScript Configuration' in the Tools Menu under NoScript opens NoScript Options. The NoScript Button just togglees 'Allow Sctipts Globally' on and off without using the NoScript in the Tools Menu. Unless I'm misunderstanding something, II. Oh well, still little better than changing between no javascript and javascript I guess. should be split up into a separate issue.

> for older releases: 42.0 and 43.0.1 with the following result: I. > I also went back a bit and checked if I.

> was causing the search engines settings to break. > setting the ' to 'de' ', then just restarting FF > What I noticed for all OS'es was that installing the language pack and (In reply to Adrian Florinescu from comment #34)

Javascript firefox 45.0 and above