-
Notifications
You must be signed in to change notification settings - Fork 949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After 2 submits input fields lose the readonly attribute #1759
Comments
We experience exactly the same issue! @chrismccord are you guys planning to address that one? |
@chrismccord I've been experiencing the same issue. Any updates on that? Happy to help if you could provide some guidance. |
I just ran into this today. Does anyone have any idea what causes this to happen? |
I think the issue is that this is a side effect of the submit process:
|
My current workaround is two-fold
|
Hey there, I worked on a PR for this. You can try |
references phoenixframework#3009 references phoenixframework#2993 references phoenixframework#1759
references phoenixframework#3009 references phoenixframework#2993 references phoenixframework#1759
references phoenixframework#3009 references phoenixframework#2993 references phoenixframework#1759
Environment
Elixir 1.12.3 (compiled with Erlang/OTP 24)
1.6.2
0.17.5
macOS Monterey
Safari, Chrome
Yes
Actual behavior
I have a form in a LiveView. One field has
readonly: true
.input:read-only
selector)Recording of the bug:
https://user-images.githubusercontent.com/29657/141962054-31abaf37-5a51-49cc-96a1-12303b53f076.mp4
Repo to demo the bug:
https://github.com/egze/readonly_bug
Expected behavior
Fields don't lose their attributes after submits.
The text was updated successfully, but these errors were encountered: