Configuration
BugDrop is configured entirely through data attributes on the script tag. No JavaScript configuration object, no external config file -- just HTML attributes. This page covers every available attribute.
Core Attributes
These attributes control the fundamental behavior of the widget.
| Attribute | Default | Description |
|---|---|---|
data-repo | (required) | GitHub repository in owner/repo format |
data-app-version | omitted | Host application version shown in System Info (1 to 128 printable characters) |
data-theme | "auto" | Widget theme: "light", "dark", or "auto" |
data-locale | <html lang> or "en" | UI language: "de", "en", "nl", "pl"; "zh-CN" in builds that include Simplified Chinese |
data-button-style | "label" | Launcher style: draggable horizontal "label" or fixed vertical "tab" |
data-position | "bottom-right" | Button position: "bottom-right" or "bottom-left" |
data-color | "#14b8a6" | Primary accent color (any CSS color value) |
data-icon | Bug icon for label, no icon for tab | Custom icon: URL to an image or "none" to hide |
data-label | localized label | Text shown on the launcher |
data-category-labels | built-in labels | Self-hosted JSON mapping from built-in categories to GitHub labels |
data-button | "true" | Show the floating button: "true" or "false" |
data-auth-token-provider | none | Name of a global function that returns a self-hosted auth token |
data-prefill-provider | none | Name of a synchronous global function that suggests built-in form defaults |
data-welcome | "Report a bug or request a feature" | Welcome message displayed at the top of the form |
data-show-issue-link | "public" | Show the GitHub issue link after submission: "public", "always", or "never" |
data-send-console-logs | "false" | Start the "Send Console Logs" checkbox checked |
Basic Example
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="acme-corp/my-app"
data-theme="dark"
data-position="bottom-left"
data-color="#ef4444"
data-welcome="Found a bug? Let us know!"
></script>
Theme Options
The data-theme attribute controls the overall color scheme of the widget:
auto(default) -- Follows the user's system color scheme.light-- White background with dark text. Suitable for most sites.dark-- Dark background with light text. Ideal for sites with dark color schemes.
<!-- Auto theme (default) -->
<script src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo" data-theme="auto"></script>
<!-- Light theme -->
<script src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo" data-theme="light"></script>
<!-- Dark theme -->
<script src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo" data-theme="dark"></script>
Language Options
The data-locale attribute controls BugDrop's built-in widget UI text -- the
feedback form, screenshot flow, annotation tools, and most success/error messages.
Brand attribution, custom labels, and server-provided error text may remain as
provided. Built-in locales are de (German), en (English), nl (Dutch),
and pl (Polish). Builds that include the Simplified Chinese update also
support zh-CN. Check your deployed widget version before selecting it.
Resolution order:
data-localeon the script tag- The page's
<html lang="...">attribute - English
Matching is case-insensitive and region subtags are accepted in both BCP 47 and
underscore formats (nl-NL, nl_NL, and NL all resolve to Dutch). Simplified Chinese
requires zh-CN or an explicit zh-Hans tag; valid extensions such as zh-Hans-TW
also select Simplified Chinese. Bare zh, zh-TW, zh-HK, and explicit zh-Hant
tags fall back to English. An unsupported value logs a console warning.
<!-- Dutch UI -->
<script src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo" data-locale="nl"></script>
<!-- Simplified Chinese UI, after deploying a build that includes it -->
<script src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo" data-locale="zh-CN"></script>
To contribute a new language, add src/widget/locales/<code>.ts implementing the
WidgetStrings interface and register it in src/widget/i18n.ts -- a unit test
enforces that every dictionary exposes exactly the same keys as English.
Position Options
The data-position attribute controls where the floating button appears:
bottom-right(default) -- Anchored to the right edgebottom-left-- Anchored to the left edge
The default label style starts near the bottom of the chosen edge. Users can drag it
vertically, and BugDrop remembers its position in the browser for the same repository and side.
Launcher Style
Add data-button-style="tab" for a compact vertical Feedback tab about two-thirds down the chosen edge.
The tab uses the localized label or your data-label override. Supply an image URL with
data-icon if you want an icon alongside the text. The tab opens the standard feedback flow
and supports the same dismiss and restore options. If you pin your widget version,
choose a release that supports data-button-style.
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-button-style="tab"
></script>
Use data-position="bottom-left" to move the tab to the left edge. Both launcher styles use the widget accent color. Add data-color="#FF9E64" for an orange launcher. Preview both launcher styles.
Issue Link Visibility
Control whether the success confirmation links to the GitHub Issue that was created.
| Value | Behavior |
|---|---|
"public" | Default. Show the issue number and GitHub link for public repositories only. Private repository submissions use a generic success message. |
"always" | Show the issue number and GitHub link whenever the server returns an issue URL, including private repositories. Use this only for trusted internal users who already have GitHub access to the target repository. |
"never" | Show the issue number for public repositories, but do not show a GitHub link. Private repository submissions use a generic success message. |
<!-- Show private repository issue links to trusted internal users -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/private-repo"
data-show-issue-link="always"
></script>
Submitter Information
Control whether the feedback form collects the submitter's name and email address.
| Attribute | Default | Description |
|---|---|---|
data-show-name | "false" | Show the name field in the form |
data-require-name | "false" | Make the name field required (implies data-show-name="true") |
data-show-email | "false" | Show the email field in the form |
data-require-email | "false" | Make the email field required (implies data-show-email="true") |
Submitter Info Example
<!-- Show both name and email, require email only -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-show-name="true"
data-show-email="true"
data-require-email="true"
></script>
When submitter information is collected, it is included in the GitHub Issue body so your team knows who reported the issue.
Prefill the built-in form
Use data-prefill-provider to name a host-owned global function. BugDrop calls it when each new
built-in details form opens, after the welcome screen. It must return an object synchronously;
Promises are not supported. Read the current in-memory app session in the function so a later
opening can reflect an account change:
<script>
window.getBugDropPrefill = () => ({
name: window.appSession?.user?.nickname,
// Offer email only if your app wants it included in the eventual Issue.
email: window.appSession?.user?.email,
descriptionTemplates: {
bug: 'What happened?\nSteps to reproduce:\nExpected result:',
feature: 'What would you like to see?\nWhy would it help?',
question: 'What would you like to know?\nWhat have you tried?',
},
});
</script>
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-show-name="true"
data-show-email="true"
data-prefill-provider="getBugDropPrefill"
></script>
The return type is { name?: string, email?: string, descriptionTemplates?: { bug?: string, feature?: string, question?: string } }, or null/undefined for no defaults. Name is limited
to 100 characters, email to 254, and each template to 4,000. Invalid, overlong, control-character,
and bidirectional-formatting fields are ignored independently; email must be accepted by the
form's email input, including a domain without empty labels or slashes. Missing or throwing
providers leave the form usable. A Promise is unsupported, and a
rejected Promise is handled without putting its value or error into the form. Diagnostics do not
include supplied values. The callback name belongs in the script attribute; personal values
belong only in the callback result, never in a script attribute, URL, or local storage.
The initial category is Bug. Until the reporter edits the description, changing category inserts
that category's template, or an empty description if none exists. Once edited, even if cleared,
category changes preserve the reporter's text. Returning from screenshot capture also preserves
the draft. A new opening calls the provider again. Supplied name and email do not reveal hidden
fields: data-show-name and data-show-email still control visibility, and neither becomes
required through prefilling.
These are editable suggestions, not verified identity. BugDrop does not prove ownership of a nickname or email. A visible prefilled email has a reminder that it will be included in the GitHub Issue if retained; Issues in a public repository are public.
Console Logs
BugDrop can include recent browser console output in the GitHub Issue. The feedback form shows a "Send Console Logs" checkbox. It is unchecked by default.
<!-- Start with Send Console Logs checked -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-send-console-logs="true"
></script>
When the checkbox is checked, the issue body includes a collapsed console-log section. BugDrop limits the amount of output and redacts obvious secret-like values such as passwords, tokens, cookies, authorization headers, and long random strings.
Dismissible Button
Allow users to dismiss the floating button so it does not obstruct their view. This is especially useful for content-heavy sites where the button might overlay important elements.
| Attribute | Default | Description |
|---|---|---|
data-button-dismissible | "false" | Allow users to dismiss (hide) the floating button |
data-dismiss-duration | Forever | How long the button stays dismissed: omit for forever, or provide a number of days (e.g., "7") |
data-show-restore | "true" | Show a small restore link after dismissing |
Dismissible Button Example
<!-- Dismissible button that stays hidden for 7 days -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-button-dismissible="true"
data-dismiss-duration="7"
data-show-restore="true"
></script>
When a user dismisses the button:
- The floating button hides
- If
data-show-restoreis"true", a small "Restore feedback button" link appears in the corner - The button stays hidden for the duration specified by
data-dismiss-duration - After the duration expires, the button reappears automatically
Feedback Categories
Users can choose from three feedback categories when submitting a report. By default, each category maps to a specific GitHub label:
| Category | Emoji | GitHub Label | Description |
|---|---|---|---|
| Bug | :beetle: | bug | Something is not working correctly |
| Feature | :sparkles: | enhancement | A new feature or improvement request |
| Question | :question: | question | A question about the product or usage |
These categories are built into the widget. Self-hosted deployments can customize which GitHub labels each category applies. There are two configuration paths:
Server-side mapping (recommended)
Set CATEGORY_LABELS on your worker. The mapping is authoritative — clients cannot override it. Two shapes are supported:
Flat shape — same labels for every repo your worker serves:
{
"bug": ["defect", "frontend"],
"feature": "product-feedback",
"question": "support"
}
Per-repo shape — different labels per repo, with an optional "*" wildcard fallback:
{
"acme-corp/my-app": {
"bug": ["defect", "frontend"],
"feature": "product-feedback"
},
"acme-corp/docs": {
"bug": "docs-bug"
},
"*": {
"bug": "triage"
}
}
The shape is detected automatically: keys containing / or equal to * mean per-repo; otherwise it's treated as flat.
Client-side mapping (self-hosts only, opt-in)
Self-hosted deployments can also let pages set labels via the data-category-labels attribute. This is disabled by default because it lets any page that loads your worker dictate which labels appear on issues. Enable it by setting ALLOW_CLIENT_CATEGORY_LABELS to the literal string "true" (case-sensitive — values like "True", "1", or "yes" keep the gate closed):
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="acme-corp/my-app"
data-category-labels='{"bug":["defect","frontend"],"feature":"product-feedback","question":"support"}'
></script>
Only enable this when your worker's ALLOWED_ORIGINS is locked down to trusted domains.
Structured variant labels
Structured submissions can request only a classification (bug, feature, question, or
feedback). They cannot send raw labels or select a named label set. Self-hosted Workers may map a
repository and variant ID to labels with VARIANT_LABELS:
{
"acme-corp/my-app": {
"export-review": ["feedback", "rating"],
"cloud-provider-question": ["enhancement", "cloud-import"]
},
"*": {
"product-suggestion": "product-feedback"
}
}
BugDrop always adds bugdrop. Missing, malformed, or invalid mappings fall back to the submitted
classification (bug, enhancement, question, or only bugdrop for feedback) and surface a
warning in Worker logs, the Issue body, and the success response. A configured variant ID is a
classification hint, not an authorization boundary: do not attach security-sensitive automation to
one of these labels without separately verifying the submitter.
The structured envelope uses the existing /api/feedback endpoint and shares its CORS, auth-token,
IP-rate-limit, repository-rate-limit, GitHub App, and response behavior. It is intentionally
field-agnostic and does not accept field schemas, screenshots, attachments, annotations, console
logs, raw labels, or labelSet values.
Auth Token Provider
Self-hosted deployments can require short-lived host-app auth tokens before BugDrop accepts feedback. This is useful when the widget is only meant for authenticated users in your product.
First, define a global function that fetches a token from your own backend:
<script>
window.getBugDropToken = async function getBugDropToken() {
const response = await fetch('/api/bugdrop-token', { credentials: 'include' });
if (!response.ok) throw new Error('Unable to create BugDrop token');
const { token } = await response.json();
return token;
};
</script>
Then reference that function on the BugDrop script tag:
<script
src="https://bugdrop.yourcompany.com/widget.js"
data-repo="owner/repo"
data-auth-token-provider="getBugDropToken"
></script>
The provider may return either a raw token or a value already prefixed with Bearer . BugDrop calls it before installation checks and feedback submissions, then sends the token in the Authorization header.
This attribute only adds the client-side header. Your self-hosted worker must also set AUTH_TOKEN_SECRET or AUTH_TOKEN_ADDITIONAL_SECRETS to enforce the token gate. One configured worker secret must be byte-for-byte identical to the host app's token-signing secret; if a valid-looking bd1 token is rejected, check for trailing newlines or quoting differences. See the Self-Hosting guide for the worker environment variables, secret hygiene notes, and token claim format.
Rules and behavior
- Recognized keys:
bug,feature,question. Other keys are ignored with a warning. - Each category accepts a single label string or an array of 1-5 strings; each label must be 1-50 characters after trimming (GitHub's limit). Labels containing control characters are rejected.
- Every issue also receives the
bugdroplabel (always added). - Precedence: when both server and client mappings are present,
CATEGORY_LABELSwins. - Fail-closed on misconfig: if
CATEGORY_LABELSis set but unusable (malformed JSON, wrong shape, or a per-repo map with no entry for the current repo and no"*"fallback), the worker uses default labels and emits a warning — it does not silently fall back todata-category-labels. This keeps a typo from handing label control back to the browser. - GitHub rejection retry: if GitHub rejects a configured label (e.g. it doesn't exist in the repo), BugDrop retries once with default labels and embeds a label-mapping warning in the issue body.
- Warnings in the response: if any warnings were emitted, the
/feedbackJSON success response includes alabelMappingWarnings: string[]field so callers can surface configuration issues programmatically.
Troubleshooting
| Symptom | Likely cause |
|---|---|
Issues are filed with default labels (bug, enhancement, question) instead of yours | CATEGORY_LABELS JSON is malformed, the shape is wrong, or the per-repo map has no entry for this repo and no "*" fallback. Check the issue body for a ## Label mapping warning section, or the worker logs for [BugDrop] Category label config warnings. |
data-category-labels is ignored | ALLOW_CLIENT_CATEGORY_LABELS is unset or not exactly the string "true". Or CATEGORY_LABELS is also set, in which case it always wins. |
| Some categories take effect but others don't | Unknown category keys (anything other than bug/feature/question) are dropped with a warning. Check spelling. |
| GitHub returns a 422 | A configured label doesn't exist in the repo. BugDrop retries with default labels automatically; the issue still gets created and the rejection is recorded in the body. |
Server Configuration
Allowed repositories
Self-hosted Workers can set ALLOWED_REPOSITORIES to restrict the repositories accepted by
installation checks and both legacy and structured feedback submissions. This is a deployment-wide
server setting: it applies to every client in that Worker environment, including direct API calls.
There is no widget attribute for it.
| Setting | Behavior |
|---|---|
| Unset, empty, or whitespace-only | No repository restriction; existing GitHub App access requirements still apply |
Standalone *, with optional surrounding whitespace | No repository restriction |
Comma- or newline-separated owner/repo names | Trim entries, discard empty entries, and match exact full names case-insensitively; CRLF is supported |
| Duplicate names | Harmless; same membership result |
example-org/* | Literal entry, with no glob expansion |
*,example-org/app | Only exact listed names match; * does not allow other repositories |
Nonblank separators only, such as , | Deny every repository |
| Unknown or malformed entries | No expansion or fallback to unrestricted access; other exact entries can still match |
The requested name is trimmed and compared case-insensitively for policy membership only. The
setting does not rewrite submitted repository names, GitHub arguments, or signed token claims.
For example, example-org/app does not match example-org/app-extra or example-org/app/extra.
Existing request validation still applies.
Configure each environment explicitly in wrangler.toml; Wrangler environment vars do not inherit
from the root vars block. These examples are commented so they do not enable a restriction:
[vars]
# ALLOWED_REPOSITORIES = "example-org/app,example-org/feedback"
[env.preview.vars]
# ALLOWED_REPOSITORIES = "example-org/app,example-org/feedback"
[env.production.vars]
# ALLOWED_REPOSITORIES = "example-org/app,example-org/feedback"
Add the setting to the existing vars block for each intended environment, then deploy through your
normal release process. Removing it, setting it blank, or using standalone * disables the
restriction. Listing a repository grants no GitHub permissions: the App must still be installed with
the required access. The list replaces neither authentication nor CORS configuration.
When a request reaches the policy check with a disallowed target, it returns HTTP 403:
{ "error": "Repository is not allowed" }
For feedback submissions, the IP limiter, authentication middleware, and repository limiter run
before the policy. Missing or invalid tokens can return 401, and exhausted quotas can return
429, before repository denial. An authenticated denied submission can consume quota. Existing
payload validation also runs before the policy. For GET /api/check/:owner/:repo, repository denial
runs before optional check authentication, so a disallowed target returns 403 even when
AUTH_TOKEN_REQUIRED_FOR_CHECK is enabled and no token is supplied. A valid token cannot override
a repository denial. See repository policy security boundaries.
Before a repository transfer or rename, list both the old and new full names. Update clients and issue tokens for the actual new repository name; token claim comparison remains exact even though the allowlist comparison is case-insensitive. Verify GitHub App access and allowed/denied behavior after the transfer, then remove the old name.
Automatic System Information
Every feedback submission automatically captures the following system information, with no configuration required:
| Field | Example | Description |
|---|---|---|
| Browser | Chrome 120.0.0.0 | Browser name and version |
| OS | macOS 14.2.1 | Operating system and version |
| Viewport | 1920x1080 | Browser window dimensions |
| Language | en-US | Browser language setting |
| URL | https://example.com/page | Current page URL |
This information is included in every GitHub Issue body under a "System Info" section, giving your team the context they need to reproduce and fix bugs.
Screenshot Behavior
Control how screenshots are collected during the feedback flow.
| Attribute | Default | Description |
|---|---|---|
data-screenshot | "optional" | Screenshot mode: "optional", "auto", or "required" |
data-screenshot-scale | "2" | Minimum pixel ratio for screenshot captures |
data-element-context-max-area | "0" | Maximum surrounding container size for Select Element captures, expressed as a multiple of the visible viewport area |
Screenshot Modes
optional-- Shows the screenshot checkbox checked by default. Users can choose full page, element, area, annotate, redact, or skip.auto-- Automatically captures a full-page screenshot after the form is submitted, without showing the manual screenshot picker or redaction step.required-- Requires a screenshot before submission. Users can choose full page, element, or area, then annotate or redact before submitting.
Manual redaction is controlled by the person submitting feedback. Use developer-configured masking for fields that should be visually covered in supported screenshot modes, especially with automatic screenshots. Auto mode warns users that a full-page screenshot will be attached, but it does not show the manual picker or annotation review step.
BugDrop preserves screenshots at their captured resolution when they fit the Worker's upload limit. The widget learns that limit during its installation check and attempts to scale larger captured or annotated PNGs down before submission. Self-hosted Workers use MAX_SCREENSHOT_SIZE_MB to set the limit; it defaults to 5 MB.
Select Element screenshots
When a user chooses Select Element, BugDrop captures the selected element and draws a rounded border around it. The border is drawn with a small 2px inner gap so it does not sit directly on top of the selected element. This keeps the default behavior tight and predictable.
The highlight uses the same styling controls as the widget:
data-colorcontrols the highlight color.data-radiuscontrols the rounded corners.data-border-widthcontrols the highlight border thickness.
GitHub issues include a screenshot caption that identifies the selected element border and includes the exact resolved highlight color.
Selected-element reports also include CSS selector metadata for the chosen element, including a full CSS path. Avoid putting secrets, customer identifiers, or other private data in DOM IDs or class names if issue visibility is broader than your internal team.
The amount of surrounding context is controlled by one attribute:
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-element-context-max-area="1.5"
></script>
- Omit
data-element-context-max-area, or set it to"0", to capture only the selected element. - Increase
data-element-context-max-areato allow larger surrounding containers. This can provide more context for triage and AI-assisted review, but may create larger images and slower captures.
Select Element captures are capped at 1x pixel ratio even when data-screenshot-scale is higher. This keeps context screenshots small enough for practical issue uploads.
The screenshot review step also links to this configuration section when a Select Element screenshot is being reviewed, so teams can discover the context setting during testing.
Developer-configured screenshot masking
BugDrop can visually mask fields that your app marks as private before a screenshot is uploaded:
<input data-bugdrop-redact value="sk_live_..." />
<section data-bugdrop-mask>Private account details</section>
Supported attributes:
data-bugdrop-redactdata-bd-redactdata-bugdrop-redacteddata-bugdrop-mask
This is visual masking, not a data-loss-prevention or security boundary. BugDrop can only mask content it can measure in the page DOM. Unmarked sensitive information can still appear, and browser rendering limits can apply to canvas, image, video, iframe, SVG, shadow DOM, pseudo-element, and highly custom control content.
Masking works in full-page, selected-element, selected-area, and automatic screenshot modes when BugDrop renders the page through its DOM screenshot path. For selected-area captures, mask rectangles are translated into the selected crop. For selected-element captures with surrounding context enabled, masks are computed relative to the captured context element.
| Capture path | Automatic DOM masks | User preview | Manual redact tool | Limitation warning | Notes |
|---|---|---|---|---|---|
| Full page | Yes | Yes | Yes | Yes | Uses DOM screenshot rendering unless the page is too complex |
| Selected element | Yes | Yes | Yes | Yes | Masks are relative to the captured element or surrounding context |
| Selected area | Yes | Yes | Yes | Yes, scoped to the crop | Masks outside the selected crop are ignored |
| Automatic screenshot | Yes | No | No | No in the current UI | Use only when marked sensitive regions are stable and supported |
| Native viewport fallback | No | Yes | Yes | Existing unavailable-mask warning | Used for very complex pages; users must review manually |
Disable screenshots or use data-screenshot="optional" on pages where sensitive
pixels cannot be reliably enclosed by DOM boxes.
<!-- Automatically attach a full-page screenshot -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-screenshot="auto"
></script>
<!-- Require a screenshot before submitting feedback -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-screenshot="required"
></script>
Custom Icon and Label
Custom Icon
The data-icon attribute lets you replace the default bug icon with your own:
<!-- Use a custom icon image -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-icon="https://example.com/my-icon.svg"
></script>
<!-- Hide the icon entirely -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-icon="none"
data-label="Feedback"
></script>
When using a custom icon URL, the image is displayed at 24x24 pixels inside the button. SVG format is recommended for best quality at all screen densities.
Custom Label
The data-label attribute adds a text label next to the button icon:
<!-- Icon + label -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-label="Report Bug"
></script>
<!-- Label only (no icon) -->
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-icon="none"
data-label="Send Feedback"
></script>
API-Only Mode
Set data-button="false" to hide the floating button entirely. This is useful when you want to trigger the widget from your own UI elements using the JavaScript API:
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="owner/repo"
data-button="false"
></script>
In API-only mode, the widget loads but no button appears. Use window.BugDrop.open() to show the feedback form programmatically. See the JavaScript API documentation for details.
Complete Configuration Example
Here is a script tag using many configuration options together:
<script
src="https://bugdrop.neonwatty.workers.dev/widget.js"
data-repo="acme-corp/my-app"
data-theme="dark"
data-position="bottom-left"
data-color="#6366f1"
data-welcome="We'd love to hear from you!"
data-show-name="true"
data-show-email="true"
data-require-email="true"
data-button-dismissible="true"
data-dismiss-duration="7"
data-show-restore="true"
data-label="Feedback"
></script>
This configuration creates a dark-themed widget in the bottom-left corner with an indigo accent color, collects the submitter's name and email (email required), and shows a "Feedback" label on the button. The button is dismissible for 7 days with a restore link.
Next Steps
- Style the widget with custom fonts, colors, borders, and shadows
- Use the JavaScript API for programmatic control
- Pin to a specific version for production stability