Non-core contributed modules

Store / restore of accessibility information does not work

Details

  • Database:
    PostgreSQL
  • Affected Branches:
    MOODLE_19_STABLE

Description

How to reproduce the bug:

  • Login to the site
  • Alter the font size (in our case: increase the font size)
  • Change the contrast scheme (in our case: reduce contrast to level 2)
  • Hit the "Store" icon -> A message indicating success appears below within the block
  • Go to the Menu, select a course -> The settings are lost and the default font size and contrast level is present again

Assumed behaviour:

  • Settings for contrast and/or font size are preserved throughout the whole session

Attachments:

  • accessiblity_block_restore1.png : Default settings
  • accessiblity_block_restore2.png : Altered settings
  • accessiblity_block_restore3.ong : Falling back to default values after opening a course

Activity

Hide
Mark Johnson added a comment -

Hi Martin,
Thanks for the report! Please can you post the HTML source of the page you took those screenshots from?

Thanks
Mark

Show
Mark Johnson added a comment - Hi Martin, Thanks for the report! Please can you post the HTML source of the page you took those screenshots from? Thanks Mark
Hide
Martin Schwinzerl added a comment -

Hello Mark!

Thanks for your quick reply and for your comment regarding the HTML files. While generating them, I realized that the site in question now uses a different theme than the one use when I applied the header.html patch. After inserting the one-line patch, it seems to work (again) as exprected, so we can probably close this issue report. If the error occurs again, I will reopen.

Again, many thanks for your quick reply and your work, it is very much appreciated. And sorry for the false positive.

best regards
Martin

Show
Martin Schwinzerl added a comment - Hello Mark! Thanks for your quick reply and for your comment regarding the HTML files. While generating them, I realized that the site in question now uses a different theme than the one use when I applied the header.html patch. After inserting the one-line patch, it seems to work (again) as exprected, so we can probably close this issue report. If the error occurs again, I will reopen. Again, many thanks for your quick reply and your work, it is very much appreciated. And sorry for the false positive. best regards Martin
Hide
Mark Johnson added a comment -

Thanks for that Martin, I'll mark this as "Not a bug" unless it appears otherwise in the future.

Show
Mark Johnson added a comment - Thanks for that Martin, I'll mark this as "Not a bug" unless it appears otherwise in the future.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: