From e20ba59fc19666c2393fe20ec4b6579a652c72b3 Mon Sep 17 00:00:00 2001 From: achmizs Date: Sat, 2 Feb 2019 22:28:17 -0500 Subject: [PATCH] Document CONSTANT VIGILANCE feature in help --- src/options.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/options.html b/src/options.html index 3e5aec9..540fb9a 100644 --- a/src/options.html +++ b/src/options.html @@ -69,6 +69,9 @@

Whitelist mode

In whitelist mode, the matching patterns list is ignored. Stickies are always killed, unless the page matches one of the patterns in the exclusion patterns list.

(In whitelist mode, the behavior of the main button () in the AlwaysKillSticky popup is reversed.)

+

Constant vigilance

+

Some websites add sticky elements after loading, or make existing elements sticky (either on a timer, or based on user actions). CONSTANT VIGILANCE counteracts this behavior, by watching the DOM for mutations, and, if necessary, killing any newly-formed stickies.

+

This feature may slightly impact browser performance on some sites or some computers. If you disable it, stickies will still be killed immediately upon page load, but not thereafter.

Advanced usage

AlwaysKillSticky automatically manages the lists of matching and exclusion patterns. When you enable or disable sticky-killing for a site (by clicking the big button in the AlwaysKillSticky popup), the pattern lists are automatically modified appropriately. There is usually no need to edit the lists yourself.

However, if you prefer more fine-grained control (e.g., if you want to kill stickies on all sites on a domain, or if you want to exclude specific paths of a site), you can edit the pattern lists by hand. The matching and exclusion patterns are regular expressions (a.k.a. “regexps”). (The site RegExr.com is useful if you are not entirely familiar with how regexps work—or even if you are.)