Comment 3 for bug 1817332

Galen Charlton (gmc) wrote :

I've pushed a branch that signs off on the original patch and adds a follow-up to both implement Jane's suggestion and avoid overwriting any custom description of the setting that may have been added.


I note that when we get around to writing an Angular library settings editor, it may have to be explicitly taught to render (safe) HTML in the org unit setting type descriptions.