> It’s a form builder with a built in No Code Rules Engine. Wait... What? Is that a name that people use in a non-sarcastic way?
[deleted]
There's 200 form builders, but none do what a programmer can, so I built my own
41–50 of 82 posts
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#42I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Another thing I noticed is that your blog loads very slow, but that might be because this article is rather popular now.
> I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Do not ever use the number input type, for any purpose. If you have a number element on your form, people will accidentally mangle their own inputs, because the value in such an element silently changes when you use the mouse wheel.
Disallow wheel input...still get a number pad on tablets and mobile?
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#43> It’s a form builder with a built in No Code Rules Engine. Wait... What? Is that a name that people use in a non-sarcastic way?
Please don't pick the most provocative thing in an article or post to complain about in the thread. Find something interesting to respond to instead.
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#44Earlier quoted context omitted.
> I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Do not ever use the number input type, for any purpose. If you have a number element on your form, people will accidentally mangle their own inputs, because the value in such an element silently changes when you use the mouse wheel.
Disallow wheel input...still get a number pad on tablets and mobile?
That is what the inputmode attribute is for.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/In...
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#45https://vimeo.com/44235657 The perfect abstract does not exist and one that can do everything is the one that doesn’t have the abstraction to begin with. I.E. use the underlying API directly
thanks I'll check it out.
There will always be something that will be beyond reach for SaaS, a level of customization beyond scope of my app. This just goes a few steps further.
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#46this looks so great! congrats on the launch!
thanks I really appreciate that
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#47Earlier quoted context omitted.
It may be worth mentioning in a future blog post because you lose a lot of the built in behavior of browser input when you make everything a "text" input. It hurts accessibility and inclusiveness as well by ignoring these common browser behaviors.
GOV.UK found that type=number actually hurts accessibility and is riddled with usability problems: https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-des...
Article from 2020... many of these issues are no longer a thing and/or are just really weird to call out. From their accessibility bullets:
> cannot be dictated or selected when using Dragon Naturally Speaking
Isn't this just a speech-to-text engine? I can say that I haven't ran into anyone using this for web control in my entire career. I'm certain it has an accessibility use-case and all, but I haven't ran into a practical example. I'm very apt to write this off as "moot," and would also suspect it may have been addressed since 2020.
Does anyone here use Dragon Naturally Speaking for web control? Good faith real question.
> appears as unlabeled in NVDA's element list
Fixed - https://github.com/alphagov/reported-bugs/issues/41#issuecom...
> appears as a spin button in NVDA's object navigation, which has an edit field and two buttons inside - those buttons are unlabeled, but decrease/increase the value
Fixed - https://github.com/nvaccess/nvda/issues/9675#issuecomment-59...
> is reported as unlabeled edit field when using nvda+tab
Fixed - https://github.com/nvaccess/nvda/issues/9675#issuecomment-59...
---
I want to point out that this article is out of date and basing any sort of modern FE development decisions on it merits much more research than just "GOV.UK tried it and it hurts accessibility" ... I attest that not using the correct input type on fields is more of an accessibility issue - especially numeric fields.
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#48Earlier quoted context omitted.
As a web designer with a speciality in a11y, it hurts that you deemed this not important enough to find the true cause of your issue with the number input. I hope you can revisit this in a future update!
https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-des...
Linking that article from 2020 is problematic - please read my response here: https://news.ycombinator.com/item?id=32141468
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#49I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Another thing I noticed is that your blog loads very slow, but that might be because this article is rather popular now.
> I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Do not ever use the number input type, for any purpose. If you have a number element on your form, people will accidentally mangle their own inputs, because the value in such an element silently changes when you use the mouse wheel.
> If you have a number element on your form, people will accidentally mangle their own inputs, because the value in such an element silently changes when you use the mouse wheel.
Yeah this can happen if you're dispatching scroll events to all descendants. but typically it is not an issue if you haven't messed with how the browser scrolls with JS.
What platforms does this happen to your users on?
My anecdote is that I've used numeric fields in all sorts of situations and have never ran into this outside of scroll-hijacked sites. I tend to respect the browser's implementation of the input types and find that they're fully functional - especially in 2022.
Re: There's 200 form builders, but none do what a programmer can, so I built my own
#50> It’s a form builder with a built in No Code Rules Engine. Wait... What? Is that a name that people use in a non-sarcastic way?
Please don't pick the most provocative thing in an article or post to complain about in the thread. Find something interesting to respond to instead. https://news.ycombinator.com/newsguidelines.html
Hum... The point of the entire form-builder is to bring more flexibility by using a more powerful "No Code Rules Engine".
Given the logical absurd built on the name of the thing, I really don't think this is a goal that will bring good results. It will not generalize at all. (What is also evidenced by the fact that there are more than 200 of those around, and none solves the very common problem the author has.)
And yes, that comes from framing the solution along that phrase.