Hi, in my case, I had to alter Nate's work-around, changing line 13 from:
if(displayed == false && oldValue != undefined){
to:
if(displayed == false && newValue != undefined){
http://jsfiddle.net/XccGJ/11/
Note: I've also updated this fiddle to use AngularJS 1.2.16 instead of
1.0.0rc4.
Regards,
Patrick.
On Monday, September 24, 2012 9:13:30 PM UTC+2, Nate Alberg wrote:
>
> http://jsfiddle.net/nalberg/XccGJ/
>
> This is my work-around for current. I just force val on the element the
> first time a valid value is set.
>
> On Monday, September 24, 2012 1:39:08 PM UTC-5, (unknown) wrote:
>>
>> Personally i would prefer amplify at least attempt to display it... if
>> the browser is the thing hiding it, at least you could do work a around by
>> using all type="text" inputs
>>
>> Currently i only use type="text" for every text/number/phone/email with
>> pattern matching/validations... since browser support for input type is
>> still not consistent enough for me.
>>
>>
>> On Wednesday, June 13, 2012 1:16:52 AM UTC-5, Vojta Jína wrote:
>>>
>>> Kinda makes sense, what you are saying.
>>>
>>> It would probably make more sense, to display the invalid value in the
>>> view then.
>>> However with invalid number, you can't do that, as browser won't let you
>>> set "abc" into number input, so it's not gonna be consistent.
>>>
>>> Honestly, I think only required-invalid makes sense for me, to have in
>>> the model.
>>> Setting the model to something invalid from within your app sounds like
>>> an error to me.
>>>
>>> V.
>>>
>>>
>>> On Mon, May 28, 2012 at 4:19 AM, Pawel Kozlowski <
>>> [email protected]> wrote:
>>>
>>>> Hi!
>>>>
>>>> I was puzzled recently by the fact that 'invalid' (with a respect to
>>>> an input type) model values won't be shown in an input. Please have a
>>>> look at this jsFiddle:
>>>>
>>>> http://jsfiddle.net/pkozlowski_opensource/ADukg/190/
>>>>
>>>> The thing is that all the inputs are correctly marked as invalid but
>>>> the initial value won't be shown. Personally I find it a bit strange
>>>> since it doesn't give users any chance of correcting invalid values. I
>>>> guess it might get really confusing when, for example, you've got
>>>> 'invalid' data loaded from a backend and those date will simply
>>>> disappear when put in a form.
>>>>
>>>> What do you think?
>>>>
>>>> Cheers,
>>>> Pawel
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "AngularJS" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected].
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/angular?hl=en.
>>>>
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
