Skip to content

Commit 8c5f79e

Browse files
committed
Facelift a couple of pages that has previously escaped because of inheritance from a sub-base page
- Legacy-Id: 8939
1 parent f63a99b commit 8c5f79e

3 files changed

Lines changed: 23 additions & 11 deletions

File tree

ietf/templates/nomcom/process_nomination_status.html

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
{% extends "nomcom/nomcom_public_base.html" %}
22

3+
{% load bootstrap3 %}
4+
35
{% block subtitle %} - Change Nomination {% endblock %}
46

57
{% block nomcom_content %}
@@ -9,13 +11,12 @@
911
{% endif %}
1012

1113
{% if need_confirmation %}
12-
<form action="" method="post">{% csrf_token %}
13-
{{ form }}
14-
15-
<div class="submitrow">
16-
<input type="submit" value="Save" name="save">
17-
</div>
14+
<form role="form" method="post">
15+
{% csrf_token %}
1816

17+
{% buttons %}
18+
<button class="btn btn-primary" type="submit">Save</button>
19+
{% endbuttons %}
1920
</form>
2021
{% endif %}
2122

ietf/templates/nomcom/remove_position.html

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
{% extends "nomcom/nomcom_private_base.html" %}
22

3+
{% load bootstrap3 %}
4+
35
{% block nomcom_content %}
46
<h2>Position: {{ position }}</h2>
57
<dl>
@@ -12,8 +14,16 @@ <h2>Position: {{ position }}</h2>
1214
</dl>
1315

1416
<h3>Do you want to remove it?</h3>
15-
<form method="post" action="">{% csrf_token %}
16-
<p><input type="submit" name="remove" value="Yes, remove it"> <a href="../">No, get me out of here</a></p>
17+
18+
<form role="form" method="post">
19+
{% csrf_token %}
20+
21+
<input type="hidden" name="remove" value="1">
22+
23+
{% buttons %}
24+
<a class="btn btn-default pull-right" href="../">No, get me out of here</a>
25+
<button class="btn btn-primary" type="submit">Yes, remove it</button>
26+
{% endbuttons %}
1727
</form>
1828

1929
{% endblock nomcom_content %}

ietf/templates/submit/note_well.html

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@
33

44
{% block submit_content %}
55
<h2>Note Well</h2>
6-
<p>Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an &quot;IETF Contribution&quot;. Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:</p>
6+
7+
<p>Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:</p>
78

89
<ul>
910
<li>The IETF plenary session</li>
@@ -15,13 +16,13 @@ <h2>Note Well</h2>
1516
<li> The RFC Editor or the Internet-Drafts function</li>
1617
</ul>
1718

18-
<p>All IETF Contributions are subject to the rules of <a href="//www.ietf.org/rfc/rfc5378.txt">RFC 5378</a> and <a href="//www.ietf.org/rfc/rfc3979.txt">RFC 3979</a> (updated by <a href="//www.ietf.org/rfc/rfc4879.txt">RFC 4879</a>). </p>
19+
<p>All IETF Contributions are subject to the rules of <a href="//www.ietf.org/rfc/rfc5378.txt">RFC 5378</a> and <a href="//www.ietf.org/rfc/rfc3979.txt">RFC 3979</a> (updated by <a href="//www.ietf.org/rfc/rfc4879.txt">RFC 4879</a>).</p>
1920

2021
<p>Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.</p>
2122

2223
<p>Please consult <a href="//www.ietf.org/rfc/rfc5378.txt">RFC 5378</a> and <a href="//www.ietf.org/rfc/rfc3979.txt">RFC 3979</a> for details.</p>
2324

2425
<p>A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.</p>
2526

26-
<p>A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. </p>
27+
<p>A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.</p>
2728
{% endblock %}

0 commit comments

Comments
 (0)