This files describes API changes in /blocks/* - activity modules,
information provided here is intended especially for developers.

=== 19.1.1 ===

* Added role="presentation" attribute to <li> elements generated via AJAX in the AMD module of the course_navigation block.

=== 19.0 ===

* blocks/html/edit_form.php The format set in the block config is now used if it is set when dealing with untrusted blocks.
* Removed undeclared and unused $this->blockname and/or $this->version declaration from the following blocks:
    * block_mentees
    * block_totara_my_learning_nav
    * block_totara_my_team_nav
    * block_totara_quicklinks
    * block_totara_recent_learning
    * block_totara_recently_viewed
    * block_totara_recommendations
    * block_totara_recommendations

=== 14.0 ===

=== 13.0 ===

* lib/templates/block.mustache the properties $accessible_skip_from and $accessible_skip_to have been removed.
* block_section_links_renderer::render_section_links had been added with additional parameter $options for overriding the css class of list of links.
* The block_instances table now contains fields timecreated and timemodified. If third-party code
  creates or updates these rows (without using the standard API), it should be modified to set
  these fields as appropriate.
* Blocks can now be included in Moodle global search, with some limitations (at present, the search
  works only for blocks located directly on course pages or site home page). See the HTML block for
  an example.
* Block block_messages is no longer a part of core.
* The deprecated block quiz_results has now been fully removed.
* The deprecated block course_progress_report has now been fully removed.
* The deprecated block frontpage_combolist has now been fully removed.

=== 12.0 ===

* Introduced block_edit_form::has_common_settings() method to allow custom blocks to turn new settings off.
  Please note, that new settings are not built on top of the existing configuration model. Even if a third-party block already has the settings such as title override or similar
  the common settings will be an extra layer of override, which is disabled by default. Essentially that should not interfere with the existing functionality,
  the worst case scenario it will be duplicated. However implementing has_common_settings() method will allow third party blocks to opt out of using custom settings.

=== 10.0 ===

* New block_base::display_with_border_by_default() method to set whether the block type should be displayed with a border by default.
* New block_base::display_with_border() method that returns true  if the block instance should be displayed with a border.
* The collapsed class was removed from the navigation block to make it compatible with aria.
* New aria attributes were added on the navigation block [aria-expanded="false"].
* The tree JS handling were moved from YUI to AMD module (Jquery).
* lib/templates/block.mustache context object has changed, the property ->accessible_skip_from has been deprecated and will be removed in a future release.
* lib/templates/block.mustache context object has changed, the property ->accessible_skip_to has been deprecated and will be removed in a future release.
* lib/templates/block.mustache context object has changed, the property ->accessible_skip has been added and has the attributes ->id and ->title
* block_base::config_save has been deprecated and now throws an exception.
* block_manager::get_required_by_theme_block_types() is no longer static.
