fix: Guard against null form-group around name fields in session_details_form.js #5175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5174
This JS file supports the
ietf.meeting.forms.SessionDetailsForm
form. In normal use, the form is rendered with its inputs (includingname
andshort
) insidediv.form-group
elements. However, the form is also reused in thesecr.sreq
app, where the fields are rendered ad hoc. Theshort
field was recently added as an always-hidden field not contained inside adiv.form-group
, causing the JS code to fail. As a result, the visibility of various fields was not updated, including the purpose/type fields complained about in #5174.