Message-Id: <c=US%a=_%p=msft%l=RED-72-MSG951102130715HF00E90A@red-70-msg> From: Thomas Reardon <firstname.lastname@example.org> To: Paul Barber <email@example.com>, Cc: "firstname.lastname@example.org" <email@example.com> Subject: RE: Proposal For Button Enhancements + Re: Proposal: Default Button on Forms Date: Thu, 2 Nov 1995 13:07:15 -0800 accelerator keys are a can of worms, there is no way to know which are browser accelerators vs. form accelerator. typically, all Ctrl- accelerators at explictiy labelled as such, and Alt- accelerators are underlined. curious if anyone has ideas about how to rationlize form accerators vs. builtin Windows keys. -Thomas Reardon Microsoft ---------- From: Simon Y. Blackwell[SMTP:firstname.lastname@example.org] Sent: Thursday, November 02, 1995 11:09 AM To: Paul Barber Cc: email@example.com Subject: Proposal For Button Enhancements + Re: Proposal: Default Button on Forms Paul W. Barber wrote: > > I would like to suggest that there be a way of indicating a default > Button on a Fill-out Form. > > When a form has multiple Text areas, it would be helpful to be able > to indicate a default Button. This could possible by implemented as > such: > > <INPUT TYPE="submit" DEFAULT="True" VALUE="Submit"> > Perhaps <INPUT TYPE="submit" VALUE="Submit" DEFAULT> would be more appropriate since it is more in line with the current style for other form controls, e.g. <INPUT TYPE="radio" VALUE="Submit" CHECKED> While we're at it, how about a modification which would allow the text displaed on the button to be different from the value, e.g. <INPUT TYPE="submit" VALUE="RunQuery MyQuery" VALUE="Ok"> It would also seem to be a simple matter to add the "&" Control Key specification technique ala MS Windows, e.g. "&Ok" results in an underlined "O" in the Ok displayed and sets Ctrl-O to simulate clicking the button.