Our Inclusion and Exclusion Filters are powerful ways to isolate key areas of a page. Indeed, you can set these on the session or page level, and they will exclude a targeted DOM element. Is a footer triggering false-positives? No problem, use a filter to ignore it.
But these filters can have subtle drawbacks: when you remove something from the DOM, it eliminates all impacts it has elsewhere on the page. For example, if you exclude all script tags, then no scripts will execute, and the page may not fully render.
“Selector Ignores” and “Selector Attribute Ignores” features are used by our HTML comparison feature. With a Selector Ignore, we will strip specific areas after capture but before doing an HTML comparison. This ensures the area still exists... It will not be taken into consideration when determining if a new version should be recorded. And Selector Attribute Ignores will instruct Fluxguard to disregard a specific attribute on a DOM element. For example, perhaps there is a class on a tag that is always changing with some session variable. You could use a filter to exclude it, yet this means you will also remove essential content from that tag. With a Selector Attribute Ignore, you isolate a tag’s attribute to dismiss.