Bug #5717
Carriage returns do not work in edit template fields
| Status: | Verified | Start date: | 09/30/2013 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | José Raddaoui Marín | % Done: | 100% | |
| Category: | Form validation | |||
| Target version: | Release 2.0.0 | |||
| Google Code Legacy ID: | Tested version: | |||
| Sponsored: | No | Requires documentation: |
Description
1) Navigate to an archival description and enter edit mode
2) In a free-text field (e.g. scope and content), enter some text, and then press "enter" (or return or whatever).
Resulting error
No carriage return is registered. User cannot insert linebreaks.
Expected result
Pressing enter causes a carriage return in the field. As we have recently done work in 1.x (for 1.4) to ensure that these breaks are preserved when roundtripped, they should also be captured in the EAD and be able to roundtrip.
History
#1 Updated by Jesús García Crespo over 8 years ago
- Assignee changed from Jesús García Crespo to José Raddaoui Marín
Radda, it seems to be aproblem introduced by your commit commit:127267a8c26502f2b1fe062be4e04b5fe1c4f67c.
Specifically, the changes done in multiRow.js made this to happen.
I wonder if this is the line causing the error:
.first().children("select, input, textarea").focus().trigger('loadFunctions');
That shouldn't be affecting a regular textarea out of a multirow, but maybe the scope of some selectores are too big? Good luck with it.
#2 Updated by José Raddaoui Marín over 8 years ago
- Status changed from New to QA/Review
- % Done changed from 0 to 100
Applied in changeset atom|commit:ac6d2bab72c1566778a963a74110ac92770a08a0.
#3 Updated by Jessica Bushey over 8 years ago
- Status changed from QA/Review to Verified
This is working now. And showing up in the EAD export as a <lb/>