Checking self.paginate_by here is not valid, as that doesn't get updated from the class-level value in the case that get_paginate_by is overridden. Django's BaseListView provides an is_paginated variable, so this could be omitted entirely - however, this returns False in the case that a view has pagination in place but only returns a single page of results, and this doesn't match the semantics we want in Wagtail (where a single page of results should display "Page 1 of 1").
This allows passing additional kwargs to the table constructor. Use this to pass use_row_ordering_attributes to PageTable, rather than patching the already-created table object.
- Removes the jQuery slide animation so content will be instantly replaced
- Removes the autofocus behaviour on the search fields as this is not helpful for screen readers / keyboard control
- Includes support for `window.header` if provided alongside dynamic adding of data-* attributes if not included
- Base implementation for #9950
- Co-authored-by: sage <laymonage@gmail.com>
- Stimulus CountController content is programatically generated but best to avoid writing HTML accidentally
- ChooserModel field required label should avoid risk of translations with HTML
- Image focal point chooser's label does not need to support HTML
- FieldBlock us using h util but this can be avoided by built in browser escaping when innerText is used
- focal-point-chooser gets value from its set up but we should avoid innerHTML if we can
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
Also includes:
- Further tone updates based on Vale
- Address other feedback to earlier parts of the tutorial
- Prep for #10197
- Fix a few cases where Draftail was spelt incorrectly
- Align with `client-side` not `clientside` as this is used most commonly
- fix javascript code snippet
- Link getting started section to elasticsearch backend, not performance page as this is more relevant.
- Mention frontend caching on performance page
- Mention prefetching image renditions on performance page
This cleans out some very old, potentially out of scope content, and makes way for the page being much easier to contribute to and extend in future.
Move deploy tutorials to 3rd-party tutorials page
4the4ryushin