Comment 6 for bug 332253

I had a feeling that might be the case, but based on Alexander's suggestion above, I wasn't sure where the best place to modify the .js file would be.

If Debian already has this same fix in native code, then I agree, that's the way to go.

We could use the same script at the time of packaging rather than the time of installation. (But would 'lsb_release' always return the correct values when the .js file is being packaged? I assume there are other ways to get that data for the architecture the package is being generated for, but pre-determining it seems like more of a hack.)

We could use a similar postinst script to generate a separate .js file with the current lsb_release info, and modify the default default-prefs.js to comment out the lines that set the values to empty strings.