• fix compatibility with Mozilla's automated review build bot
• fix #1983: store user's cfg for linter correctly

Full Changelog: v2.3.15...v2.3.16

fix #1941: throttle scheme change
fix #1955: filtering when all entries match
fix #1958: don't colorize cm-builtin
fix #1959: update LESS
fix #1971: always remember tab's IID in MV2
fix #1972: pin lastUpdateTime to now if absent
fix #1973: filter must be present in doc to ensure init
fix #1976: remove leftover from d0c07af
fix #1977: new transifex url
detect FF 138 in Android
update locales

Full Changelog: v2.3.14...v2.3.15

Notable fixes:

• Instant inject option.

Full Changelog: v2.3.13...v2.3.14

Notable changes:

• fix #1915: raciness of soft navigation (aka AJAX sites)
• fix #1920: usercss installer for local file
• MV3: get color scheme from web pages to reduce memory footprint when instant inject is not enabled
• Firefox: restore addons->Options link. It's the only UI-facing difference so far between the attached firefox-mv2 build that is optimized for Firefox (previously we only submitted it to AMO, now it's added to releases and nightly builds) and a generic/universal mv2 build. There should be no detectable difference in performance.

Full Changelog: v2.3.12...v2.3.13

Fixes:

• Firefox on desktop was broken when using storage fallback mode.
• Firefox on desktop's scrolling in the Stylus popup was randomly disabled.

Known bugs:

• Firefox: can't install .user.css from a local file system.
  Fixed in 41b99c1. The workaround is to use a simple localhost http server or use the nightly build.

Full Changelog: v2.3.11...v2.3.12

Fixes:

• Firefox on Android.
• When publishing a new style on userstyles.world fill out the name/description/code properly.
• Increased the age column width in the style manager for Chinese and Vietnamese UI.

Known bugs:

• Entirely broken in Firefox on desktop when using storage fallback.

Workaround for Firefox on Android until the new version is published:

1. https://addons.mozilla.org/firefox/downloads/file/4338993/styl_us-1.5.51.xpi
2. chrome://geckoview/content/config.xhtml
3. extensions.update.enabled = false
4. settings
5. about Firefox
6. tap logo five times
7. navigate up
8. install extension from file

Workarounds for desktop Firefox:

Either install an older version or if you have an up-to-date backup of your styles: remove the extension, re-install it, import the backup.

Full Changelog: v2.3.10...v2.3.11

Fixes:

• Text search in style manager.
• Live reload -> config dialog -> the UI will match the updated source now.

Known bugs:

• Entirely broken in Firefox on Android.
• Entirely broken in Firefox on desktop when using storage fallback.
• Publishing a new style on userstyles.world doesn't set the name/description/code.
  The workaround is to copypaste the values manually.
  Fixed in nightlies via 41cc1dc.

Full Changelog: v2.3.9...v2.3.10

Fixes:

• Toggling/deleting a style in the popup when the current tab is a Stylus page e.g. editor.

Known bugs:

• Text search in style manager.
  Fixed in nightly via 5758302.

Notable fixes:

• Random failures after toggling/editing a style
• Autocomplete inside functions

Known bugs:

• Toggling/deleting a style in the popup when the current tab is a Stylus page e.g. editor.
  The workaround is to reload the tab after each such change.
  Fixed in nightly via 549c0c6.

Full Changelog: v2.3.7...v2.3.8

Notable changes:

• Fix #1891: styles for an old URL of the tab were applied on navigation with instant inject option enabled.

• Stylus now automatically makes a backup of the styles database into another storage to increase the chance it survives bugs in Stylus or browsers like Vivaldi that carelessly offer an option to shoot oneself in the foot by clearing extension storage in the Delete browsing data UI. The copy is compressed using gzip in modern browsers, so it's just ~10% of the original.

  Currently Stylus will restore the data automatically on the next start of the extension if the main database is empty, i.e. it won't happen if you updated some style after the database was cleared while the extension was still running (because the main storage won't be empty anymore). Eventually I'll add a UI to do it explicitly. Until then the workaround is pretty straightforward: click Export in the style manager, delete the new style(s) to make the database empty, disable and enable the extension or reload it, import the exported backup.

Full Changelog: v2.3.6...v2.3.7

Known bugs:

• Styles targeting specific parts (i.e. not the entire site) of a SPA site like fb/x/youtube may be applied incorrectly while navigating the site. Fixed in a543970.

P.S. The attached MV2 build includes a post-release fix for very old browsers without gzip compression API.