Files
cap/docs/guide/widget.md
T

135 lines
4.4 KiB
Markdown
Raw Normal View History

2025-01-18 13:46:25 +00:00
# @cap.js/widget
2025-06-13 14:53:42 +01:00
> [!NOTE]
>
2025-03-04 11:30:35 +00:00
> **Requirements:** All modern browsers should be supported, but the build script specifically targets the last 10 versions of Chrome, Firefox, Safari and Edge.
2025-04-22 14:41:19 +01:00
`@cap.js/widget` is Cap's client-side library. It includes the `cap-widget` web component, the invisible mode and the Captcha solver. First, add it to your client-side code:
2025-01-18 13:46:25 +00:00
2025-04-22 14:41:19 +01:00
::: code-group
2025-06-13 14:53:42 +01:00
```html
2025-01-18 13:46:25 +00:00
<script src="https://cdn.jsdelivr.net/npm/@cap.js/widget"></script>
```
2025-06-13 14:53:42 +01:00
```html
2025-04-22 14:41:19 +01:00
<script src="https://unpkg.com/@cap.js/widget"></script>
```
2025-05-07 19:30:12 +01:00
2025-06-13 14:53:42 +01:00
```html
<script src="https://<server url>/assets/widget.js"></script>
2025-05-30 18:35:14 +01:00
<!-- tip: make sure to set the wasm endpoint too! -->
```
2025-04-22 14:41:19 +01:00
:::
2025-06-13 14:53:42 +01:00
::: warning
We're using the latest version of the library here for simplicity, but you should optimally pin a specific version to avoid breaking changes in the future.
2025-05-21 16:36:02 +01:00
:::
2025-01-18 13:46:25 +00:00
You can now use the `<cap-widget>` component in your HTML.
```html
2025-05-30 18:35:14 +01:00
<cap-widget id="cap" data-cap-api-endpoint="<your cap endpoint>"></cap-widget>
2025-01-18 13:46:25 +00:00
```
2025-06-13 14:53:42 +01:00
> [!NOTE]
>
> You'll need to start a server with an API exposing the Cap methods running at the same URL as specified in the `data-cap-api-endpoint` attribute.
2025-01-18 13:46:25 +00:00
2025-05-07 19:30:12 +01:00
> [!TIP] The following attributes are supported:
2025-04-12 13:39:56 +01:00
>
> - `data-cap-api-endpoint`: API endpoint (required)
> - `data-cap-worker-count`: Number of workers to use (defaults to `navigator.hardwareConcurrency || 8`)
2025-01-18 13:46:25 +00:00
Then, in your JavaScript, listen for the `solve` event to capture the token when generated:
```js{3}
const widget = document.querySelector("#cap");
2025-04-12 13:39:56 +01:00
widget.addEventListener("solve", function (e) {
2025-01-18 13:46:25 +00:00
const token = e.detail.token;
2025-04-12 13:39:56 +01:00
2025-01-18 13:46:25 +00:00
// Handle the token as needed
});
```
2025-04-23 14:52:50 +01:00
Alternatively, you can use `onsolve=""` directly within the widget or wrap the widget in a `<form></form>` (where Cap will automatically submit the token alongside other form data. for this, it'll create a hidden field with name set to its `data-cap-hidden-field-name` attribute or `cap-token`).
2025-01-18 13:46:25 +00:00
## Supported events
2025-04-12 13:39:56 +01:00
The following custom events are supported:
2025-01-18 13:46:25 +00:00
- `solve`: Triggered when the token is generated.
- `error`: Triggered when an error occurs.
- `reset`: Triggered when the widget is reset.
2025-05-30 17:52:07 +01:00
- `progress`: Triggered when there's a progress update while in verification.
2025-04-22 13:42:58 +01:00
2025-05-07 19:30:12 +01:00
## i18n
You can change the text on each label of the widget by setting the `data-cap-i18n-*` attribute, like this:
```html
<cap-widget
id="cap"
2025-05-30 18:35:14 +01:00
data-cap-api-endpoint="<your cap endpoint>"
2025-05-07 19:30:12 +01:00
data-cap-i18n-verifying-label="Verifying..."
data-cap-i18n-initial-state="I'm a human"
data-cap-i18n-solved-label="I'm a human"
data-cap-i18n-error-label="Error"
></cap-widget>
```
2025-06-16 14:18:28 +01:00
`verify-aria-label`, `verifying-aria-label`, `verified-aria-label`, `error-aria-label` are also supported for screen readers.
2025-06-13 14:53:42 +01:00
## Customizing the widget
2025-05-07 19:30:12 +01:00
2025-06-13 14:53:42 +01:00
### fetch function
You can override the default browser fetch implementation by setting `window.CAP_CUSTOM_FETCH` to a custom function. This function will receive the URL and options as arguments and should return a promise that resolves to the response.
2025-04-22 13:42:58 +01:00
```js
window.CAP_CUSTOM_FETCH = function (url, options) {
// Custom fetch implementation
return fetch(url, options);
};
2025-05-07 19:30:12 +01:00
```
2025-05-09 14:45:13 +01:00
2025-06-13 14:53:42 +01:00
## WASM URL
2025-05-09 14:45:13 +01:00
2025-05-24 09:09:18 +01:00
You can override the default WASM URL by setting `window.CAP_CUSTOM_WASM_URL` to a custom URL. This URL will be used to load the WASM module. This defaults to `https://cdn.jsdelivr.net/npm/@cap.js/wasm@0.0.4/browser/cap_wasm.min.js`
2025-06-13 14:53:42 +01:00
## Widget appearance
You can fully change how the widget looks by setting various CSS variables on the `cap-widget` element. The following CSS variables are supported:
```css
cap-widget {
--cap-background: #fdfdfd;
--cap-border-color: #dddddd8f;
--cap-border-radius: 14px;
--cap-widget-height: 30px;
--cap-widget-width: 230px;
--cap-widget-padding: 14px;
--cap-gap: 15px;
--cap-color: #212121;
--cap-checkbox-size: 25px;
--cap-checkbox-border: 1px solid #aaaaaad1;
--cap-checkbox-border-radius: 6px;
--cap-checkbox-background: #fafafa91;
--cap-checkbox-margin: 2px;
2025-06-16 14:18:28 +01:00
--cap-font: system, -apple-system, "BlinkMacSystemFont", ".SFNSText-Regular", "San Francisco",
"Roboto", "Segoe UI", "Helvetica Neue", "Lucida Grande", "Ubuntu", "arial", sans-serif;
2025-06-13 14:53:42 +01:00
--cap-spinner-color: #000;
--cap-spinner-background-color: #eee;
--cap-spinner-thickness: 5px;
--cap-checkmark: url("data:image/svg+xml,%3Csvg%20xml...");
--cap-error-cross: url("data:image/svg+xml,%3Csvg xml...");
--cap-credits-font-size: 12px;
--cap-opacity-hover: 0.8;
}
2025-06-16 14:18:28 +01:00
```