mirror of
https://github.com/wagtail/wagtail.git
synced 2024-11-25 05:02:57 +01:00
c4ef290859
Fixes #11420 Two issues existed; 1. Safari will not set `document.activeElement` as expected in all other browsers, instead, when a button is clicked it will keep the activeElement as `body`. This meant that the reset of the disabled button (before the confirm triggers a click) was not working. 2. Visually the button still had the loading spinner due to w-progress controller having triggered the loading visuals, this did not block the behaviour but looked broken. See Safari behaviour docs: - https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#clicking_and_focus - https://bugs.webkit.org/show_bug.cgi?id=22261 |
||
|---|---|---|
| .. | ||
| scss | ||
| src | ||
| storybook | ||
| tests | ||
| extract-translatable-strings.js | ||
| package-lock.json | ||
| README.md | ||
| tailwind.config.js | ||
| webpack.config.js | ||
Wagtail client-side components
This library aims to give developers the ability to subclass and configure Wagtail's UI components.
Usage
npm install wagtail
import { Explorer } from 'wagtail';
// [...]
<Explorer />;
Development
# From the project root, start the webpack + styles compilation.
npm run start
You will also need:
- React DevTools – React developer tools integrated into Chrome.
- Redux DevTools – Redux developer tools integrated into Chrome.
Releases
The front-end is bundled at the same time as the Wagtail project. This package also aims to be available separately on npm as wagtail.