Jon Roberts

I would think that using browser native date input would be more consistent, this is a tough one. I looked at this a bit. Didn't find anything that would obviously...

Can ignore my previous comment. One idea I have is to change the date input from the RangedDatePicker component to a straight rails `form.date_field`, and let standard browser & rails...

The javascript from `app/javascript/src/case_contact.js` also runs every time the form (or any page?) loads and changes the value of the input, in a kind of hacky way that browser input...

Taking out that date conversion on page load doesn't break any other specs, so I'll work up a PR for that. I can't guarantee it's the issue, but seems very...

hmm... looks like a similar setup in `app/javascript/src/all_casa_admin/patch_notes.js`, which uses same notification library, and does some **heavy** DOM manipulation, but separate from the javascript involved here.

Opened a PR (link above). I said that it "addressed" this issue rather than "resolves" since we don't know the precise issue. It will not auto-close this issue, we should...

Could be related, but I'm not sure. I thought that we'd be safe from that situation, but appartantly not... we had some discussion of it in #5974 . We could...

@bcastillo32 can do!

I put a PR up that just adds an extra day cushion for validation. Potential that contacts will be saved as occurring 'tomorrow' instead of seeing the error. @bcastillo32 do...

This would be pretty great. If pursued, I would suggest the api look more like the current `*[strategy]_list` pattern rather than passing in a relation argument. That is: ```ruby association_list(:article,...