In classic, the "Search forums" string still was around (in the
"Add a block" block). So, instead of searching for strings, we
use the explicit step that allows us to look for blocks.
Encode all popup data for report actions inside the action link
itself, because previously reloading a report via AJAX meant
actions no longer opened in popups, because the required JS was
absent from the page.
Before this change grunt tried to use the Linux version of files in
node_modules/.bin rather than the Windows version which is generated
by npm.
To avoid this issue we need to run the components directly.
Apart from removing these libraries because the Flash Player was deprecated
in 2017 and officially discontinued on 31 December 2020, the rtmp and useflash
settings have been removed too (they make no sense anymore).
The repository_skydrive has been removed from core. Methods for
importing files from skydrive to onedrive repository have been
deprecated and will be completely removed in Moodle 4.4.
This implementation will introduct changes to
the mod_quiz to implement the new qbank api
for view. Major changes are introduced in
the custom view and also all the legacy points
to the old qbank are changed to qbank plugins
where needed. It also deprecated and deletes
classes and scripts which were kept not to
break mod_quiz for the new api implementation.
* Have the currently selected dropdown menu item serve as the dropdown's
description in order for screen readers to announce its current
selection.
- JAWS and NVDA both read this as "[element name] [selected value]".
- Chrome screen reader (formerly ChromeVox) does not announce the
description.
* Add a title attribute so the dropdown's element name can be shown by
browsers on hover.
More notably PHPUnit to 9.5.9 that comes with some good fixes
and better support for go prospecting php81 (beta) status.
Generated with php73, that is the lower version supported
by this branch, following the instructions @ https://docs.moodle.org/dev/Composer
The step that causes the problem is:
And I navigate to "Badges > Add a new badge" in current page administration
(because "Add a new badge" is exactly on the edge (bottom) of the window)
So we need to make the window large before it, not after it, or the
"Add a new badge" link won't be ever clicked.
