mirror of
https://github.com/go-gitea/gitea
synced 2024-11-09 19:54:25 +00:00
2dc6f15eca
The choice regarding which forms should or should not trigger a warning is subjective. I tried to be consistent and not warn about forms that: - run an action, rather than edit data: search, send an email. - delete data: a warning about losing data would be confusing Note that forms on sign-in pages were already ignored (using a selector, rather than an explicit class on the form element). Fixes #3698.
14 lines
638 B
Cheetah
14 lines
638 B
Cheetah
<form class="ui form ignore-dirty">
|
|
<div class="ui fluid action input">
|
|
<input type="hidden" name="type" value="{{$.ViewType}}"/>
|
|
<input type="hidden" name="state" value="{{$.State}}"/>
|
|
<input type="hidden" name="labels" value="{{.SelectLabels}}"/>
|
|
<input type="hidden" name="milestone" value="{{$.MilestoneID}}"/>
|
|
<input type="hidden" name="assignee" value="{{$.AssigneeID}}"/>
|
|
<div class="ui search action input">
|
|
<input name="q" value="{{.Keyword}}" placeholder="{{.i18n.Tr "explore.search"}}..." autofocus>
|
|
</div>
|
|
<button class="ui blue button" type="submit">{{.i18n.Tr "explore.search"}}</button>
|
|
</div>
|
|
</form>
|