Skip to content

Bubble Activation Behavior

Activation behavior controls whether Definer's pop-up bubble is available on a specific webpage. If the bubble is not available, you won’t be able to bring it up regardless of which activation trigger you use. This feature is handy if you want the bubble to appear only on certain pages or if you prefer to disable it on specific sites.

settings.avifDefiner's bubble activation behavior settings

Enabled/Disabled Indicator

Pin Definer's icon to the extensions toolbar (next to the address bar) to quickly check if the bubble is enabled or disabled on the page you're currently viewing:

  • When the bubble is enabled, the icon will be colored (yellow).
  • When the bubble is disabled the icon in the extension toolbar will be grayed out.

indicator.avifDefiner's icon in the extension toolbar

Default Behavior

Your default behavior setting establishes the baseline rule for most websites, which you can then override with specific exceptions.

Enable on all pages, except blacklisted

Definer's factory setting

With this option, the bubble is available everywhere except on sites you've specifically blocked in your "Blacklist". This is ideal if you regularly use Definer across many different websites.

Disable on all pages, except whitelisted

This setting keeps the bubble hidden everywhere except on sites you've explicitly allowed in your "Whitelist". Choose this option if you only need Definer on specific websites. For example, when learning a language on certain educational platforms or when reading content in a foreign language.

Whitelist & Blacklist

These lists contain your custom URL rules that override the default behavior:

  • Whitelist: The bubble will always be available on these sites, regardless of your default setting
  • Blacklist: The bubble will never appear on these sites, regardless of your default setting

When rules conflict, the system resolves them based on your Default Behavior:

  • If set to "Enable on all pages, except blacklisted," whitelist rules override blacklist rules
  • If set to "Disable on all pages, except whitelisted," blacklist rules override whitelist rules

precedence.avif

URL Rules

You can create precise rules to control where Definer works based on URL patterns.

Adding Rules:

  • Manually: Click the "ADD RULE" button and configure your rule
  • Automatically: Use the toggle switches in the Extension Window

popup-rule.avifToggling these switches creates URL rules automatically

You can manage your rules by:

  • Rearranging their order
  • Moving them between Whitelist and Blacklist
  • Toggling them on/off
  • Editing or deleting them via the three-dots menu

Each rule consists of a Condition and a URL pattern.
Let's go over each condition and see examples of how to use them.

Matches domain

Applies to an entire domain and all its pages.

Example:

  • Condition: Matches domain
  • URL: example.com
  • Result: Bubble works on:
    • https://example.com
    • https://example.com/hello
    • https://example.com/hello/world

NOTE

This doesn't apply to subdomains like blog.example.com

rule-condition-domain.avif

Matches URL

Applies only to an exact URL match.

Example:

  • Condition: Matches URL
  • URL: https://example.com/hello
  • Result: Bubble works only on that specific page, not on https://example.com/hello/world

rule-condition-url.avif

URL contains

Applies to any URL containing the specified text.

Example:

  • Condition: URL contains
  • URL: product
  • Result: Bubble works on:
    • https://example.com/product
    • https://example.com/products/item
    • https://store.com/view-product/123
    • https://product.com/category/details

rule-condition-contains.avif

URL starts with

Applies to any URL beginning with the specified text.

Example:

  • Condition: URL starts with
  • URL: https://docs.example.com/guides
  • Result: Bubble works on:
    • https://docs.example.com/guides
    • https://docs.example.com/guides/beginner
    • https://docs.example.com/guides/references

rule-condition-starts.avif

URL ends with

Applies to any URL ending with the specified text.

Example:

  • Condition: URL ends with
  • URL: /checkout
  • Result: Bubble works on:
    • https://example.com/checkout
    • https://store.com/cart/checkout
    • https://marketplace.org/vendors/123/checkout

rule-condition-ends.avif

Matches pattern

Uses browser URL patterns with wildcards (*) for flexible matching.

Example:

  • Condition: Matches pattern
  • URL: *://*.github.io/*
  • Result: Bubble works on all GitHub Pages:
    • https://username.github.io
    • https://organization.github.io/project
    • http://username.github.io/page

rule-condition-pattern.avif

Matches regular expression

For advanced users who need complex pattern matching using regex.

Example:

  • Condition: Matches regular expression
  • URL: ^https:\/\/[^\/]+\/users\/\d+$
  • Result: Bubble works on user profile pages with numeric IDs:
    • https://example.com/users/123
    • https://social.network/users/456
    • But not on: https://example.com/users/john

rule-condition-regex.avif

It's Not Racist

Recently, there's been a push to replace "whitelist" and "blacklist" with alternative terms because of the perceived racial connotations.

Historically, "black" and "white" have symbolized concepts like darkness versus light, unknown versus known, or danger versus safety. These color associations are not inherently racial and appear in numerous languages and cultural contexts worldwide.

Ironically, assuming racial meanings in color-based terminology might actually reinforce the idea that colors must have racial significance. Energy spent renaming established technical terms could be better directed toward addressing actual instances of bias in technology.

Requests to change these terms for the sake of political correctness will be ignored.