Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Would it make sense to have an override for default-scheduled value fields? #38

Closed
WorldMaker opened this issue Nov 27, 2023 · 0 comments · Fixed by #68
Closed

Would it make sense to have an override for default-scheduled value fields? #38

WorldMaker opened this issue Nov 27, 2023 · 0 comments · Fixed by #68
Labels
question Further information is requested

Comments

@WorldMaker
Copy link
Owner

The <progress> element in HTML also uses the value field but probably should be default-scheduled rather than immediate because it doesn't affect user interaction like value property on HTML inputs.

What would this override look like? bind={{ bfScheduledValue: value }}?
@WorldMaker WorldMaker added the question Further information is requested label Nov 27, 2023
WorldMaker added a commit that referenced this issue Jan 4, 2024
@WorldMaker
Add an opt-in property for delayed value binding
75c28b8 
Add an override to `bind` named `bfDelayValue` that is schedulable and schedules to the key `value`.

Also, rewrite the documentation to rename "default scheduled" to "delayed scheduled" while still emphasizing its default nature. This should clear up some confusion as well as provide a better name long-term.

Resolves #38
@WorldMaker WorldMaker mentioned this issue Jan 4, 2024
Merged
WorldMaker added a commit that referenced this issue Jan 4, 2024
@WorldMaker
Add an opt-in property for delayed value binding (#68)
862ba3f 
Add an override to `bind` named `bfDelayValue` that is schedulable and
schedules to the key `value`.

Also, rewrite the documentation to rename "default scheduled" to
"delayed scheduled" while still emphasizing its default nature. This
should clear up some confusion as well as provide a better name
long-term.

Resolves #38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add an opt-in property for delayed value binding WorldMaker/butterfloat
1 participant
@WorldMaker