Bug Report for AJAX (vanilla JS)
Bug reports with severity, environment, and reproduction steps. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why AJAX (vanilla JS) developers choose splitforms for bug report
The bug report on this page integrates with AJAX (vanilla JS)'s development workflow using the form markup in your AJAX (vanilla JS) project. Whether you're deploying to a static host or a server-rendered platform, the form posts standard <code>FormData</code> to splitforms, so your backend complexity stays at zero. AJAX (vanilla JS)'s ecosystem has strong tooling for UI, but form delivery is a separate concern that splitforms handles independently — Free includes spam filtering and a submissions dashboard; Starter adds email notifications and webhooks.
Yes — this is the shortest safe path for AJAX (vanilla JS).
Use the HTML snippet on this page, keep the bug report fields visible in your AJAX (vanilla JS) UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the HTML version, then replace YOUR_ACCESS_KEY.
The posted payload contains short summary, severity, browser & os, steps to reproduce, your email (so we can follow up). Required fields are short summary, severity, steps to reproduce and your email (so we can follow up).
Vanilla JS / AJAX forms have been the no-framework default since jQuery's heyday.
User-reported bugs are signal — but only if the report has steps-to-reproduce and a screenshot. The form forces the structure, then files the issue automatically.
Built for AJAX (vanilla JS) developers who hate operating a backend.
Splitforms is the form backend for AJAX (vanilla JS) sites. One POST endpoint, no SDK, no plugin — drop the bug report into a page and ship.
Splitforms is the form backend for AJAX (vanilla JS) sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.
- ✓500 form submissions per month
- ✓2 forms on Free; unlimited forms on Pro
- ✓Spam protection (honeypot + classifier)
- ✓Webhooks: Slack, Discord, WhatsApp, custom
- ✓CSV export of all submissions
- ✓Email notifications (CC and BCC on Pro)
Drop into any AJAX (vanilla JS) project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a AJAX (vanilla JS) page, and ship. No build-time integration required.
Generate, embed, receive.
Three actions stand between you and your first bug report submission. None of them require a backend, a database, or a CAPTCHA library.
Generate a free splitforms key
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
Paste the bug report into your AJAX (vanilla JS) project
Drop the form snippet into a AJAX (vanilla JS) page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
The reason this bug report exists.
Screenshot upload (Pro) · webhooks into Linear / GitHub Issues / Slack.
Bug reports without reproduction steps waste hours of triage. The form structures the report — what happened, what was expected, steps to reproduce, browser / OS / device, screenshot. Screenshot upload is critical: 'the page broke' tells you nothing; a screenshot of the broken state tells you everything. Webhook the structured report into Linear or GitHub Issues so it lands as a triageable ticket, not a Slack message that scrolls away. For SaaS teams the time saved is huge — instead of a 4-message back-and-forth gathering basic context, the engineer opens the issue and starts debugging.
Structure the report
Required: what happened, what you expected, steps to reproduce. Optional: browser, OS, device, URL where it occurred. Most templates auto-detect browser/OS via JS so the user doesn't have to fill them.
Screenshot upload
Pro file upload — drag-and-drop a screenshot or screen recording. Multi-file accepted. Image attachments arrive on the email and via webhook with signed URLs.
Webhook into Linear / GitHub
Lands as a Linear issue or GitHub issue with the structured report as the body and the screenshot embedded. Engineer opens, reproduces, fixes — no triage thread needed.
What changes when this bug report lives in AJAX (vanilla JS).
These notes come from the AJAX (vanilla JS) platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Vanilla JS / AJAX forms have been the no-framework default since jQuery's heyday. Without splitforms, the 'AJAX' part is one fetch line; the operational part is everything else: a backend route, an SMTP provider, a database for submissions, a honeypot or reCAPTCHA, a thank-you page, error handling for HTTP 4xx/5xx, retry logic. For 'JS-only on a static host' setups (Cloudflare Pages, GitHub Pages, S3), there's literally no server to run the route on — historically that meant Formspree, Formspark, Web3Forms, Basin. Splitforms is the modern entry: same shape, better free tier, better spam filtering, and signed webhooks from Starter.
Vanilla JS deploys to any static host — the snippet is HTML + inline <script>, no build step. CSP: if your site sets connect-src 'self', add https://splitforms.com to the directive or fetch is blocked. Browser support: native fetch is in every browser back to Edge 18 — the snippet runs without polyfills on every market-share-relevant browser. The progressive-enhancement variant (Pattern B) keeps the form working when JS fails to load — useful on flaky networks, ad-blocked clients, or for accessibility tools that disable JS.
Forgetting e.preventDefault() reloads the page
Without preventDefault, the browser does its own form submission to wherever the form's action attribute points (or the current page) AND your fetch runs. You see a flash, the page reloads, and your handler's effects are lost.
FormData includes ALL form fields — even disabled ones get dropped
new FormData(form) skips inputs without a name attribute, skips disabled inputs, skips unchecked checkboxes/radios. If a field doesn't show up in your splitforms inbox, check whether it's disabled at submit time.
fetch() doesn't reject on HTTP 4xx/5xx — only network errors
If splitforms returns a 401 (bad key) or 429 (rate limit), fetch resolves successfully. You have to check res.ok or data.success yourself. Wrapping in try/catch only catches network failures, not HTTP errors.
Double-click submit fires two requests
Without disabling the button on the first click, a quick double-click sends two POSTs. Both succeed; the user sees one success message; you see two submissions. Always set button.disabled = true at the start of the handler.
Pattern A — fetch + FormData + status element
Single submit listener. new FormData(form) reads inputs, append the access key, POST. Update an aria-live status <p> with the result. ~25 lines, no library. Use the same wiring for the bug report fields on this page.
Pattern B — progressive enhancement (works without JS)
Form has a real action attribute and a redirect hidden field — works with JS disabled (browser POSTs natively, splitforms 302s). When JS is available, the listener intercepts for inline UX. Best of both worlds, no compromise. Use the same wiring for the bug report fields on this page.
What every field actually does.
Each field below ships in the bug report template — rename, remove, or add your own. Splitforms accepts any name you POST.
Short summary
Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.
Severity
Triage signal — drives whether this pages on-call or waits till Monday.
Browser & OS
Repro context for engineering — saves a back-and-forth.
Steps to reproduce
Free-text input — no character limit, expands as the visitor types.
Your email (so we can follow up)
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
One backend. Every framework.
The same bug report template works on every framework splitforms supports. Pick yours.
Bug Report on AJAX (vanilla JS) — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship AJAX (vanilla JS) forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a bug report on AJAX (vanilla JS) in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your AJAX (vanilla JS) project.