• last updated 20 hours ago
Constraints: committers
Constraints: files
Constraints: dates
make init-procs more robust in case of broken setups

    • -1
    • +5
fix an at lease 11 year old bug... not sure, why this was not discovered earlier

no need to limit the width of a form label in vertical forms

Check existence when resetting package parameters. Many thanks to Markus Moser

Reinstate check, add a note why

add property to textara and text_fields to disallow cut&paste

optionally disallow cut&paste in multi-line form fields

Remove Hinweise zum Datenschutz bei Googleparameter

improve wording

disallow auto-save when exam is closed

handle cases, where autosave was rejected

cleanup (generalize and simplify code)

    • -2
    • +9
remove unused nsv variables

use "-varname" parameter for message_exists_p

- simplifying one more expression

- bump version number to 5.10.0d11

reduced the number of mutex locks for message keys lookup by a factor of two by using naviserver commands

do not try to load site-wide parameters in xo::parameters

- based xo::parameter on nsv_dict when available

- bumped version number to 5.10.0d31

- icanuse: added nsv_dict

- bumped version number to 5.10.0d37

    • -2
    • +2
fix typo

improve comments and spelling

improve comments

remove unsed mutex

fix typo

ad_urlencode_url: add a slash to the path when this is not empty, fix test case

Extend test

Avoid useless check

Expose a regression after changes for bug #3437

styling for count-down alarm

countdown alarm: add audible alarm when the countdown timer reaches expiration.

Per default, the audible alarm is turned off, but the user sees a

mute symbol. When the user activates the audible alarm, the browser

will announce the nearing end by beep signals in increasingly shorter

periods before its expiration (default settings: 60, 30, 20, 10, 5,

2s; these values can be changed via HTML). Once a user has activated

the audio signals, these are preseveed between page changes via a

cookie. On some browsers (e.g. Chrome), the audioContext settings are

so restrictive, that the full reload requires a new activation of the

alarm via a "user gesture" (i.e. clicking on the audio symbol). It

would be not surprising, if some other browsers show different

behavior, but the code follows the relatively new recommendations. The

code was tested with Chrome/Chromium 83 and Firefox 77).

    • -1
    • +128