mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-05 20:24:13 +03:00
6befca1695
Backport #27592 by @JakobDev If you set a checkbox as required in a issue form at the moment, the checkbox is checked and read only, what does not make much sense. With this PR, the Checkbox actually needs to be checked. The label supports now also Markdown. This matches GitHub's behaviour. And yes, I know the CSS is a ugly workaround. It looks like the given CSS code is part Fomantic and I don't know how to change that. The Maintainers are free to change that. ![grafik](https://github.com/go-gitea/gitea/assets/15185051/3f35be75-b0b4-42a7-9048-a4970384a035) Co-authored-by: JakobDev <jakobdev@gmx.de>
14 lines
452 B
Handlebars
14 lines
452 B
Handlebars
<div class="field">
|
|
{{template "repo/issue/fields/header" .}}
|
|
{{range $i, $opt := .item.Attributes.options}}
|
|
<div class="field inline">
|
|
<div class="ui checkbox gt-mr-0">
|
|
<input type="checkbox" name="form-field-{{$.item.ID}}-{{$i}}" {{if $opt.required}}required{{end}}>
|
|
<label>{{RenderMarkdownToHtml $.context $opt.label}}</label>
|
|
</div>
|
|
{{if $opt.required}}
|
|
<label class="required"></label>
|
|
{{end}}
|
|
</div>
|
|
{{end}}
|
|
</div>
|