Previously, we rely on the fact that the SubMenuItem itself is a dismissible. So, we decide how to show/hide the number badge based on the value for the SubMenuItem's dismissible ID on the server. However, this means that if the user has dismissed the SubMenuItem and we add new dismissible child items within it (e.g. update the ID for the 'What's new in Wagtail version' child item), the number badge will not show up. This commit changes the logic to show/hide the number badge based on whether there are any undismissed items within the SubMenuItem and whether the it has been opened or not.
Fixes #10348
e.g. when trying to move an existing page when `parent_page_types`
is added after the page is created under a different parent page type than the one allowed
- Adds a new first contribution guide page
- Refines the contributing index to add more ways to get involved & cleans up that section
- Moves the committing TOC link to the bottom of the contributing index page as this is only needed for core team
- Fixes #10070
* Extract userbar BaseItem.get_context_data()
* Extract Axe config into smaller attributes and methods for easier overrides
* Add TypeScript interface for WagtailAxeConfiguration
* Improve typings for userbar.ts
* Separate Axe `runOnly` and `rules` options
* Pass request object to all axe configuration methods
* Remove Axe runOnly option if it's falsy
* Add docs for customising the accessibility checker
* Use lists for Axe include and exclude selectors
* Parse JSON script when testing accessibility checker config
* Add tests for customising accessibility checker configuration
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
- Closes #10247
- adding BulkController files and removing {% block extra_js %} from submit_translation.html
- add unit tests for new controller
- partial work on CSP compliance #7053
