×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 5/9/2011 2:03 PM, Bryce Martin wrote:
Why can't the "standard" function keys change? You are trying to adapt to
the web... so you might have to change the way things worked before...
*gasp* change? Yep, change. Remember, when you are developing for the
web, you are now in the browser's territory...so you have to play by the
browser's rules.
With IE I didn't have to "play by the browser's rules". Instead, I was
able to write applications that my users were able to use with minimal
retraining. New and shiny is worthless if it isn't as productive as old
and rusty.
Plus, I see no reason for browsers not to make all those keys accessible
to JavaScript. It's lazy coding on their part, and I don't know why my
users should lose keys on their keyboard just because somebody decided
it didn't fit this week's idea of a standard.
I can understand changing the paradigm when the device changes - e.g.,
tablets - but browsers have perfectly working keyboards attached to them
and I ought to be able to use every key on the keyboard.
Joe
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
