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.

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

Create chapter for cfform #14

Open
cfjedimaster opened this issue Feb 10, 2014 · 6 comments
Open

Create chapter for cfform #14

cfjedimaster opened this issue Feb 10, 2014 · 6 comments

Comments

@cfjedimaster
Copy link
Owner

No description provided.

@cfjedimaster
Copy link
Owner Author

Just a placeholder.

@ryanguill
Copy link

so I keep wanting to send people here for cfform/cfinput - but its a big topic. flash forms, auto complete inputs, related selects, validation in general, tooltips, etc. Do you guys have a plan for how to tackle it? I assume jQuery is what you will suggest for most of this right?

I was thinking of contributing some to this, at least some of it - would that be ok? I'd be happy to just submit pull requests and let you guys look over it.

@cfjedimaster
Copy link
Owner Author

" Do you guys have a plan for how to tackle it?" A smaller chapter focusing on one thing is best. Like - I think we now have one on autocomplete. I definitely don't want one chapter one everything cfform can do.

" I assume jQuery is what you will suggest for most of this right?" Actually no! There is more to front-end dev then jQuery. ;) Frankly, if the person submitting the article uses Ext, or Prototype, I don't care, as long it is a clear, sensible solution.

@cfjquery
Copy link
Contributor

Well I have submitted a pull request for cfform ( on the topic of validation ).
I agree that the cfform topic will need to be split up, but not quite sure how this should be done.
I'm sure we can sort it out though.

@AnthonyKolka
Copy link

Reading the example, I see a huge red flag. Only doing client side validation is the path to compromise. It's fine to do client side validation, but one also must do server side validation, because there is nothing stopping someone from bypassing your javascript when sending data to the server.

@cfjedimaster
Copy link
Owner Author

You are right - and we will gladly take a PR that adds the server side validation in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants