I didn't say required. I said required="required"
Ramsey
On Apr 18, 2013, at 10:32 AM, John Pollard wrote:
> "required" didn't work for me, it came out as "required"="e" in my example
>
> On 18 Apr 2013, at 17:42, Ramsey Gurley wrote:
>
>> A: Inline binding suck :)
>> B: required="required"
I am just amazed that you remembered that! I have not used that in years, if
ever.
On 2013-04-18, at 11:02 AM, Kieran Kelleher wrote:
> It is not documented on every individual WODynamicElement, but it is
> documented on page 11 as a common binding that all WODynamicElements
> recognize. See
It is not documented on every individual WODynamicElement, but it is documented
on page 11 as a common binding that all WODynamicElements recognize. See the
docs for that binding on page 11 of this:
http://wiki.wocommunity.org/download/attachments/1049043/DynamicElements.pdf
On Apr 18, 2013, at
Perfect, thanks
On 18 Apr 2013, at 18:55, Kieran Kelleher wrote:
> Try this:
>
> HTML:
> ---
>
>
> WOD:
> ---
> TextField : WOTextField {
> value = aValue;
> otherTagString = "required";
> }
>
>
> otherTagString binding is just a string value that is appended to th
Try this:
HTML:
---
WOD:
---
TextField : WOTextField {
value = aValue;
otherTagString = "required";
}
otherTagString binding is just a string value that is appended to the opening
tag attributes as is.
On Apr 18, 2013, at 1:42 PM, John Pollard wrote:
> I a
I am certainly in debt to the community, but I suspect I would hinder more than
help.
I can see er.extensions.components._private.ERXWOTextField which I understand
automatically replaces the webobjects WOTextField class... is this what would
need updating? I can't say I would be confident to do
"required" didn't work for me, it came out as "required"="e" in my example
On 18 Apr 2013, at 17:42, Ramsey Gurley wrote:
> A: Inline binding suck :)
> B: required="required"
>
> Done.
>
> On Apr 18, 2013, at 8:31 AM, John Pollard wrote:
>
>> I should have said, when I do this:
>>
>>
>>
A: Inline binding suck :)
B: required="required"
Done.
On Apr 18, 2013, at 8:31 AM, John Pollard wrote:
> I should have said, when I do this:
>
>
> data-theme="e" required/>
>
> the generated HTML comes out as required="e", apparently picking up the last
> parameter that did have a val
And contribute the subclass to the community.
> You would need to extend it in Wonder, ERXWOTextField. Add an isRequired
> binding and then append the required in appendToResponse. Should be trivial.
>
> Chuck
>
>
> On 2013-04-18, at 8:31 AM, John Pollard wrote:
>
>> I should have said, whe
You would need to extend it in Wonder, ERXWOTextField. Add an isRequired
binding and then append the required in appendToResponse. Should be trivial.
Chuck
On 2013-04-18, at 8:31 AM, John Pollard wrote:
> I should have said, when I do this:
>
>
> data-theme="e" required/>
>
> the ge
Subclass WOTextField to inject html5 behaviors/flags?
Tim
UCLA GSE&IS
On Apr 18, 2013, at 8:31 AM, John Pollard wrote:
> I should have said, when I do this:
>
>
> data-theme="e" required/>
>
> the generated HTML comes out as required="e", apparently picking up the last
> parameter tha
I should have said, when I do this:
the generated HTML comes out as required="e", apparently picking up the last
parameter that did have a value.
On 18 Apr 2013, at 16:23, John Pollard wrote:
> Can WOTextField or something similar handle the "required" in:
>
>
>
> i.e. telling the
Can WOTextField or something similar handle the "required" in:
i.e. telling the browser that a field is required, it has not value assigned to
it
I couldn't see a Wonder way for this.
Many thanks
John
___
Do not post admin requests to the list. They
13 matches
Mail list logo
