-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Form status not correctly preserved #1524
Comments
Thank you. I fixed all the issues except the "indeterminate" state of |
I understand your consideration. I don't like scripts either, but I am not against to handle script-driven matters with scripts, which is somehow of more fidelity of the original page. Even for the the checked/selected/value attributes, reducing IDL into static HTML attribute breaks form resetting, which might be something the user wants to keep, although the form in the saved page is mostly not expected to be submittable. WebScrapBook has 7 options for form status: but I choose so because it's more expected that the saved page be editable and re-savable in WSB. After all SF is not WSB and you can do whatever you want. (BTW forget my broken English, maybe it should better be "states" rather than "status" here? 😆) |
Indeed, form management in SF is much more limited than in WSB. It's also the kind of problem I need to take some time to think about. The most important thing is that it's registered somewhere, and for that I thank you very much for creating this issue. You've described the problems perfectly (my english is broken too 😋 but I would use "state" in literal translation from french to english). |
Describe the bug
The status of some form elements are not correctly preserved in the captured page.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ddd
is checked but should be unchecked.DDD
is checked but should be unchecked.EEE
is checked but should be indeterminate.Environment
The text was updated successfully, but these errors were encountered: