Now that events due on the current date are indicated in the timeline
block, for consistency, the overdue filter has been updated to also
display those items.
Previously, only past dates displayed an indication of being overdue.
This update moves the badge to indicate each event that is overdue
instead, which makes the information clearer and also means it now
supports flagging events due earlier in the current day.
* The helplink has changed so the language customisation check had to be
updated to use a different selector.
* The totop string has been moved from boost to classic only and the
string must be moved too.
* The new footer toggle may sit over the [next page] button for the
timeline block for some browsers (Linux only). Changing the browser
size to large resolves this.
AMOS BEGIN
CPY [totop,boost],[totop,classic]
AMOS END
* 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.
This value was being passed in the template, but the template
had 0 hardcoded instead of injecting the context value. With the other
bug fixes in this issue correctly loading the "All" view properly on
page load, this uncovered that at load time, the course view would not
load overdue items, which also meant a behat test was failing.
The 6 month option was highlighted on load if previously selected,
which was not the case for any other options. This has been removed
so it behaves consistently.
When the timeframe filter was set to "all" when the timeline
block was initially loaded, an incorrect value rendered into
the template meant the timeframe limit was set to 0 (which will
return no results) instead of setting no limit (which would fetch all
action events, as intended).
version = 2021052500 release version
requires= 2021052500 same than version
Why 20210525? (25th May 2021) ?
Because master is going to be Moodle 4.0, to be released
on November 2021. And, until then, we are going to have
a couple of "intermediate" releases:
- Moodle 3.10 to be released 9th November 2020. (2020110900)
This version will be using versions from today to 2020110900
(once it's released the YYYYMMDD part stops advancing).
- Moodle 3.11 to be released 10th May 2021. (2021051000)
This version will be using versions from 3.10 release to 2021051000
(once it's released the YYYYMMDD part stops advancing).
That means that all versions from today to 2021051000 are going
to be used by those 2 "intermediate" releases (3.10 and 3.11).
And we cannot use them in master, because it's forbidden to have
any overlapping of versions between branches (or different upgrade
paths will fail).
So, get that 2021051000, let's add it a couple of weeks to cover
the on-sync period (or a 2 weeks delay max!) and, the first version
that master can "own" in exclusive (without any overlap) is, exactly,
25th May 2021, hence our 20210525.
If an event is not in the current year it can be confusing as the
months and days may appear to be in the wrong order.
This change adds the year to the displayed date to make the reason
for the order clear.
