Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
The Internet

WHATWG calls for 'Last' Comments on Web Forms 22

Posted by timothy from the they-should-be-rounder-and-firmer dept.
hixie writes " The W3C recently acknowledged a version of the Web Forms 2.0 draft submitted to the W3C by Mozilla and Opera. Meanwhile the WHATWG has updated the Web Forms draft and released a new call for comments. Send them in!"
This discussion has been archived. No new comments can be posted.

WHATWG calls for 'Last' Comments on Web Forms More

WHATWG calls for 'Last' Comments on Web Forms

Comments Filter:

  • What Working Group?? (Score:3, Funny)

    by cylcyl ( 144755 ) on Monday April 18, 2005 @06:57PM (#12276216)
    What does the What Working group work on ?? What? What?

  • Input validation schemes (Score:3, Informative)

    by Magic Thread ( 692357 ) on Monday April 18, 2005 @07:55PM (#12276801) Homepage Journal
    From W3C's summary:
    The ability to mark a form field as required (ie. the user must complete the field before the form is submitted).
    Maybe I'm being paranoid, but can anyone else see lazy PHP coders relying on this, and forgetting to do proper server-side input checking? I mean, essentially you're just having to check everything twice... what was wrong with returning a page informing the user of his or her mistakes, exactly?

    • Re:Input validation schemes (Score:4, Insightful)

      by Nasarius ( 593729 ) on Monday April 18, 2005 @08:01PM (#12276867)
      Maybe I'm being paranoid, but can anyone else see lazy PHP coders relying on this, and forgetting to do proper server-side input checking?

      No need to pick on the PHP coders -- you can just as easily write unchecked Perl, ASP, Python, etc -- but yes, some of the biggest website vulnerabilities are caused by relying too much on JavaScript to validate input.

      I mean, essentially you're just having to check everything twice... what was wrong with returning a page informing the user of his or her mistakes, exactly?

      It's a little faster for the user (instant feedback on any mistakes), and it saves a tiny bit of server resources. And it should replace all the JavaScript hacks with one standard interface.

      • It's a little faster for the user (instant feedback on any mistakes), and it saves a tiny bit of server resources.

        Depends on what's being uploaded. If it's large, then it could be a lot faster for the user and save a lot of server resources.
      • It's a little faster for the user (instant feedback on any mistakes), and it saves a tiny bit of server resources. And it should replace all the JavaScript hacks with one standard interface.

        What's to stop server side code from parsing the XForms (or Web Forms or whatever your choice of poison is) to extract validation information, and then do the _exact_ same checks on the server side? Why, it even makes your code more easily maintainable.

        I do something similar to this with my PHP framework using XML do
        • Sorry to reply to my own post, but those interested in further reading on the topic of server-side XForms validation may find the XForms Constraints section of the XForms working draft interesting:

          http://www.w3.org/TR/2002/WD-xforms-20020118/sli ce 6.html#model-xformsconstraints
        • "What's to stop server side code from parsing the XForms "

          There's nothing to stop you from doing it that way. It's just slower by a round-trip to the server (which could be a little or a lot), and uses server resources instead of client resources, when the latter are generally more available.

          Personally, I like to occasionally try my software using a slow dialup account several time-zones away from the server, since that will be the environment for plenty of my users. I avoid network round trips like the

    • Maybe I'm being paranoid, but can anyone else see lazy PHP coders relying on this, and forgetting to do proper server-side input checking?

      I may be wrong, but I believe one of the greatest advantages of XForms for the developer is exactly that, since you have all those rules and constraints defined in a XML format, it is incredibly easy (provided your server-side language supports this) for you to use the very same XML to produce a HTML form (through Web Forms) and to do server-side checking.

      All you ha

    • Php solved this problem a long time ago with HTML_QuickForms [thelinuxco...ancy.co.uk]. Setting a field to be required is trivial and you can choose to have it check server side or client side depending on your needs. You can enforce other rules like regular expression pattern matching just as easily and there's also a bunch of canned rules like "must be a valid email address". Of course, there are undoubtedly a lot of php coders that have never heard of pear... so I guess the point stands. And of course, there's still that cr

  • this bit made me laugh... (Score:3, Funny)

    by dash2 ( 155223 ) <davidhughjones@gmail. c o m> on Tuesday April 19, 2005 @07:48AM (#12280360) Homepage Journal
    Similarly, attributes are defined to accept values that conform to certain syntaxes, but it is possible for authors to violate these constraints.

    Authors must not do this. User agent implementors may curse authors who violate these rules, and may persecute them to the full extent allowed by applicable international law.

    You can tell these guys have experience doing real implementations...

  • Every web browser needs some kind of native grid/table spreadsheet style display box. Displaying rows of data gets ugly if the data gets wide. If a form could record the row/column selected it would very useful.
    • JSF. http://developers.sun.com/prodtech/javatools/jscre ator/index.jsp
    • While we're wishing for some good UI... let's make sure the aforementioned grid includes resizeable, hideable, sortable columns.

      Oh and would it kill you guys to include some sort of early-bound scripting language? ECMA is nice and all but I can write VB code about 3 times faster than JavaScript all thanks to AutoComplete...
  • While I believe that any/all Web standards be developed by the W3C, this statement:

    The W3C Team strongly recommend that future work should be in collaboration with the W3C HTML and XForms Working Groups in order to promote the development of a single community for improving forms on the Web. The W3C Team looks forward to working with Opera Software and The Mozilla Foundation to build consensus on unified approaches to forms and related Web technologies.

    ...sounds very petulant and has the NIH ("not in

Slashdot Top Deals

If all else fails, lower your standards.

Close