You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An SCTLD user reported that when entering valid coordinates in the EML editor, the input field is sometimes surrounded by a red outline, indicating an issue. No error message is shown. This problem was observed with the following longitude values: -81.77270 and -81.45697.
I was able to reproduce the problem and the issue is with the pattern regex attribute in the input element. Since we have validation implemented at the model level now, this additional regex pattern seems unnecessary and potentially conflicting. It also lacks a useful error message. We should remove the pattern regex from the coordinate input elements to rely solely on the model-level validation.
The text was updated successfully, but these errors were encountered:
Fixed in branch bug-2226-coordinate-regex. SCTLD reported that this bug prevented them from being able to submit a dataset. I was not able to reproduce that and I'm waiting for more details from that team. If, in fact, the faulty regex is preventing submission, we could consider releasing as a hotfix. Otherwise, I'll include with the next release.
SCTLD tried again and was able to submit the dataset even with the inappropriately flagged coordinate field. I think whatever the issue was with submitting that dataset was unrelated to this issue. The fix has now been merged into main and will be included with the next release.
An SCTLD user reported that when entering valid coordinates in the EML editor, the input field is sometimes surrounded by a red outline, indicating an issue. No error message is shown. This problem was observed with the following longitude values:
-81.77270
and-81.45697
.I was able to reproduce the problem and the issue is with the pattern regex attribute in the input element. Since we have validation implemented at the model level now, this additional regex pattern seems unnecessary and potentially conflicting. It also lacks a useful error message. We should remove the pattern regex from the coordinate input elements to rely solely on the model-level validation.
The text was updated successfully, but these errors were encountered: