90a9c3c32a
I figured out a way to stop compatibility breakages being so annoying with the prefs refactor without needing to keep a prefs dictionary around forever. If, on starting the application, we set new preference names to old preference values we can choose when to break compatibility. This will allow us to do so later on, i.e. a significant time after the rename, when many users will have had their preferences migrated and the version with the old preference names is no longer supported. Signed-off-by: Skyler Grey <skyler.grey@collabora.com> Change-Id: I5f4101fb95b5f3b2caaf9ebaf353eb591024dd97 |
||
|---|---|---|
| .. | ||
| Autolinker.js | ||
| global.js | ||
| l10n.js | ||
| ResizeObserverPolyfill.js | ||
| sanitize-url.js | ||
| select2.js | ||