How do I modify a dropdown box?
in [JavaScript]
|
Prev: FAQ Topic - How do I get a jsp/php variable into client-side javascript? (2010-05-03)
Next: The famous 'resend'
From: bruce on 5 May 2010 07:00 On May 5, 5:08 am, Gregor Kofler <use...(a)gregorkofler.com> wrote: > Am 2010-05-04 18:18, Dr J R Stockton meinte: > > > How about those whose date of birth was 1900-02-29? Some may still be > > alive. > > ...but not longer hanging out on tennis courts... ;-) > > --http://www.gregorkofler.com No one was ever born on 1900-02-29 as 1900 is not a leap year. 2000 was the a leap year and the first TIME the divide by 400 rule was ever used. So we know they are not at the tennis courts. Maybe at the Cabana enjoying a cool one!! Bruce
From: David Stone on 5 May 2010 09:22 In article <hrq443$oir$1(a)news.eternal-september.org>, Stanimir Stamenkov <s7an10(a)netscape.net> wrote: > Tue, 04 May 2010 08:53:37 -0400, /David Stone/: > > > The bit I was commenting on was the TAGGED address portion, and > > NOT the domain name. Would you prefer I used a real, deliverable > > domain with the fred+usenet@ part, just to make a point? Didn't > > think so! > > That's what I wanted stated clearer as I think an occasional reader > may not know about the reserved top-level domain names and the exact > valid production of the local part of an email address. Then they'd probably try sending email to help(a)example.com, and complain bitterly about the lack thereof!
From: David Stone on 5 May 2010 09:20 In article <Fs+ANRLkjE4LFw1J(a)invalid.uk.co.demon.merlyn.invalid>, Dr J R Stockton <reply1018(a)merlyn.demon.co.uk> wrote: [snip] > "First name" / Last name" can be inappropriate in some cultures - > Chinese and Mongolian, for example, IIRC. Around here, the standard has become "Given Name / Family Name", which seems to work for all the cases I've ever encountered (and we get some real jaw-crackers on the class lists!) There is even a provision for a nickname (although I forget exactly how that is referred to within the course management system) > Also, how about those who do > not use their first name - J. Edgar Hoover, George VI, for example? How > about middle initial(s)? I don't think either of those gentlemen would be filling out a web form any time soon. For the first example, the labelling I mention above works. For the limited number of those of the second case, I believe they would normally give their names for personal use as Elizabeth Windsor, etc. > And those whose date of birth does not match their birthday? The only living example I can think of has two "birthdays", the real one and the officially celebrated one, so no real conflict. Of course, you still have a sizeable number who don't know what their real date of birth is... > > How about those whose date of birth was 1900-02-29? Some may still be > alive. Again, it seems a little unlikely that such a person would be filling in a web form BUT the form should still not choke on any valid date, or make assumptions about what Feb. 29th '00 might refer to!
From: John G Harris on 5 May 2010 10:04 On Mon, 3 May 2010 at 21:38:35, in comp.lang.javascript, Garrett Smith wrote: >Ben C wrote: >> On 2010-05-03, David Stone <no.email(a)domain.invalid> wrote: >>> In article <oRaGpaE+mp3LFw6p(a)J.A830F0FF37FB96852AD08924D9443D28E23E >>>D5CD>, >>> John G Harris <john(a)nospam.demon.co.uk> wrote: >>> >>>> On Sun, 2 May 2010 at 22:08:03, in comp.lang.javascript, Garrett Smith >>>> wrote: > >[...] > >>>> But accept >>>> 2010-05-03 >>>> 2010-5-3 >>>> 2010/5/3 >>>> 2010.5.3 >>>> as equally valid. (Unless you actively want to lose customers). >>>> > >The other formats are nonstandard open to arbitrary interpretation. Imagine you learnt to use '/' and no redundant zeroes at school and you've been using this successfully for the last 40 years. Now imagine some jumped up shopkeeper says you are wrong, wrong, wrong, because computers can't understand it. Would you recommend that online shop to your friends ? As for being non-standard, you will find that the motive for producing ISO 8601:2004 was to facilitate the sending of dates across national boundaries. Also, to facilitate the sending of dates between computers. It does not concern itself with letters sent to your Aunty Lily in Australia, nor with letters sent by customers to shop keepers. >>>> John >>> Run into that before. As well as pages that reject credit card >>> numbers unless there is a space every four digits (only a single >>> field for input, but they don't tell you to include the delimiters >>> they _require_). >> Why they can't just delete the spaces or put them in themselves if >>they >> want/don't want them I don't know. >> >Although I am guessing here, it might be considered a liability of the >web site for providing an unauthorized credit card number that is not >what the user entered, where the user may claim that he did not enter >that number. Nah! The programmers can't be bothered to handle spaces, *and* get it right. John -- John Harris
From: Dr J R Stockton on 5 May 2010 13:12
In comp.lang.javascript message <4a61d8ae-e333-4849-962a-9f68f7092b78(a)d1 9g2000yqf.googlegroups.com>, Tue, 4 May 2010 11:56:12, bruce <bruceaj(a)bellsouth.net> posted: > >You are correct. The solution to my problem was easy. 4 lines of >code.. If you were to post that code, either it might be helpful to others or we could tell you of its faults. <URL:http://www.merlyn.demon.co.uk/js-date6.htm> needs more than 4 lines, IIRC. But the whole thing is much easier in HTML 5, where appropriately implemented : <URL:http://www.merlyn.demon.co.uk/js-date3.htm#HTML>. -- (c) John Stockton, nr London UK. ?@merlyn.demon.co.uk BP7, Delphi 3 & 2006. <URL:http://www.merlyn.demon.co.uk/> TP/BP/Delphi/&c., FAQqy topics & links; <URL:http://www.bancoems.com/CompLangPascalDelphiMisc-MiniFAQ.htm> clpdmFAQ; NOT <URL:http://support.codegear.com/newsgroups/>: news:borland.* Guidelines |