GitLab

related to #17100740

Use the pagination markup so that it really looks like the page links.

(closes #17084333)

[pagination] Use CW 3.23 API instead of reimplementing do_paginate to customize pagination extra links

(related #17084333)

Introduced in 92ab4759805e

else you get valuable information that is not displayed anywhere.

Closes #17059496

Following 011730a4af73 in cubicweb.

next_tabindex() is gone in cubicweb 011730a4af73

This is expected for proper caching and will be made mandatory by cubicweb's
722690d7ae28

Closes #16347567

Also a bit of flake8.

Closes #14544064.

`cubicweb.form.css` should not be loaded with cubciweb-boostrap.
Currently (cw =< 2.23) it is done by AutoClickAndEditFormView and can not be
easily overrided in cubciweb-boostrap. We should at some point rewrite AutoClickAndEditFormView
in cw to ease overriding. Until it is done we juste use empty `cubicweb.form.css` file

closes #14458715

Already done in site_cubicweb, which is the proper place as the formwidget
module isn't reloadable.

Tuple unpacking in function arguments is verboten.

Use new function attribute names (introduced in 2.6, and still present
in 3.x) instead of the old func_* ones.

- do not call self._cw.message twice as it is then popped from the session data
- add alert dismiss functionality to the close button

Closes #13835109.

This was due to the use of an old CW 3.20 dbapi-related API call.

Closes #13835004.