LivelyKernel / LivelyKernel/lively.morphic
Password Input breaks when saved to Partsbin
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that password input morphs serialize and deserialize fine (i.e. copy) yet, when they are being stored as part of another part in the Partsbin they become unresponsive to any user input.
Serialization + Deserializtion seems to fix it again.
Another bug that is that the `onInputChanged()` is never being called. Neither are events such as `onKeyDown()`.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by storing a password input morph inside another part in the Partsbin, then compare its behavior before and after serialization and deserialization. Check why user input and callbacks such as onInputChanged() and onKeyDown() stop working after Partsbin restoration; done means the stored password input accepts input and invokes these handlers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100