W3C home > Mailing lists > Public > public-html@w3.org > April 2015

Fwd: Re: Form element dependencies

From: sisbluesteel <sisbluesteel@aol.com>
Date: Thu, 02 Apr 2015 12:44:04 +0300
To: public-html@w3.org
Message-ID: <C3E3CB20-67D0-4C76-8533-D9AD765B1115@aol.com>



-------- Original Message --------
From: sisbluesteel <sisbluesteel@aol.com>
Sent: April 2, 2015 12:42:22 PM EEST
To: Andrea Rendine <master.skywalker.88@gmail.com>
Subject: Re: Form element dependencies

Okay,

I'm going to send the proposal to whatwg mailing list sometime soon. I'll use discussion done here as a reference and probably implement a light prototype in JS as well.

On April 2, 2015 5:23:34 AM EEST, Andrea Rendine <master.skywalker.88@gmail.com> wrote:
>Hey everybody!
>Has there been any evolution about this subject?
>Days ago I sent a message but it never reached the list. In short:
>The focus for dependency attribute and "directionality" is to choose
>ease
>of implementation or readability.
>- if @for is specified on the controller, then I think that it would be
>easier for user agents to identify the state change action.
> <controller@for> -> identify controlled (depending) element(s) ->
>controller state change -> toggle controlled element's state
> - on the other hand, specifying it on controlled elements (depending)
>makes the code more readable, I see an element and I know what controls
>it
>relies on.
>It'd be also useful to know if there are custom scripts (plugins etc)
>which
>do it as of now and how they work.
>These are some examples:
>http://dstreet.github.io/dependsOn/ - here the relationship starts from
>controlled and the function specifies what elements the controlled
>relies
>upon
>https://github.com/keyo/jQuery-Form-Dependency - more complex syntax,
>but
>same as above. The rule specifies what element's state to watch in
>order to
>enable/disable behaviors
>http://www.alpacajs.org/releases/1.1.3/examples/components/dependency/dependency-field.html
>-
>same here, the depending elements are specified before the element to
>be
>watched.
>Then it looks like community goes this way.
>
>I'd suggest some other ways to propose this feature:
>- https://www.w3.org/community/webed/wiki/HTML5_form_additions (page or
>discussion), but I don't know how often it is watched
>- WHATWG mailing list (whatwg@whatwg.org), similar to this but
>regarding
>Web Hypertext Application Technology Working Group
>- https://wiki.whatwg.org/wiki/IRC WHATWG Freenode channel (requires
>more
>dedication)
>- WHATWG wiki proposals
>(https://wiki.whatwg.org/wiki/Feature_Proposals) -
>also worth noting this page for suggestions about proposing stuff:
>http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F
>
>Yours respectfully and supportingly
>Andrea

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Received on Thursday, 2 April 2015 09:45:53 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:43 UTC