Re: [WSG] Use of Enter key to naviagte between form fields

2007-02-27 Thread Brian Duchek

You're gonna shoot yourself in the foot if you go one step further
without diving as deep as possible into answering the question why
does he want this?

If you're making something that looks like a web form on a web page to
be accessed by web users, then it's pretty clearly folley - a short
test with some users will bear this out. Do it in front of your
insistent client and he'll have a hard time disagreeing with you.

If you're making something that looks like a tax-form wizard on an
interactive/business application that just happens to be delivered
via a browser and is targeted at people with 30 years of data-entry
experience, then the same test will reveal that having their form
submit when they hit enter (instead of moving between data fields)
will be a terrible usability burden.

Know thy user as thy self =)

Either way you'll have a difficult time overiding the default behavior
of a browser, so you better count on needing javascript enabled (and a
healthy testing budget) to develop this behavior.  When you get down
to it, it's not that hard to implement with some keypress listeners.

The idea about a confirmation dialog (while not-efficient) seemed a
good one, when used as part of a smooth degredation scheme.
/bd

On 2/27/07, Andrew Maben [EMAIL PROTECTED] wrote:


Nick Roper wrote:
Hi,
A customer has requested that they should be able to navigate between input
fields on a form by using the Enter key - i.e. to replicate the action of
the Tab key.
I've seen examples of Javascript code to do this, but I'd be interested in
any feedback on whether there are any issues with this and what the best
approach is to implement.
Thanks,
Nick

I have to agree with Darren and Barney, it is an astoundingly anti-user
proposal, as you present it.

But perhaps your customer has some convincing rationale for wanting to do
this? If so, I'm sure we'd all be fascinated to hear it.

Andrew


109B SE 4th Av
Gainesville
FL 32601

Cell: 352-870-6661

http://www.andrewmaben.com
[EMAIL PROTECTED]

In a well designed user interface, the user should not need instructions.




***
List Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Escaped 's in field values.

2004-10-19 Thread Brian Duchek
Why not just escape(selected.value) the improperly encoded value to
convert the  to amp;?


On Thu, 23 Sep 2004 16:07:25 -0400, Scott Reston [EMAIL PROTECTED] wrote:
 I've got a select form element that contains values that include escaped 
 ampersands. eg,
 select
 option value=This amp; ThatThis amp; That/option
 /select
 
 I'm finding that when I use javascript to get the value of the (selected index of 
 the) field, the value that javascript gets has the , not amp;
 
 My character set for the form is ISO-8859-1.
 
 I'm using the form input on another page and want to stay XHTML... Does anyone have 
 any insight into why I wouldn't get the whole value and what I can do to remedy the 
 situation?
 
 Scott Reston
 Director, Web Development
 Capstrat
 919/882.1966 v
 919/834.7959 f
 1201 Edwards Mill Road, Suite 102
 Raleigh, NC 27607
 www.capstrat.com
 **
 The discussion list for  http://webstandardsgroup.org/
 
 Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge
 To be held in Sydney, September 30 and October 1, 2004
 
 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
 **
 
 


-- 
Brian Duchek
=-=-=-=-=-=-=-=
e: [EMAIL PROTECTED]
c: 847.809.2140
w: www.inquiline.com
=-=-=-=-=-=-=-=
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



[WSG] css syntax question

2004-10-02 Thread Brian Duchek
Is there a syntax in CSS declarations which 'wraps' classes/ids in a
parent condition?  I'm not asking this very clearly, but the idea is
similar to the Javascript syntax...

with  {
...
}

The purpose being, I find myself writing a lot of statements like the below

#navigation p {...}
#navigation #tabs {...}
#navigation #tabs ul li a {...}

Isn't there an easier/more efficient way to apply the parent selector
#navigation to all the different groups?

#navigation {
 p {...}
 #tabs{...}
}

Does anyone know if the above works, or if it has any browser support holes? 

I only ask because I know the people on this list can chew up this
question and spit it out like no one else :-)

Thanks,
-- 
Brian Duchek
=-=-=-=-=-=-=-=
e: [EMAIL PROTECTED]
w: new.inquiline.com
=-=-=-=-=-=-=-=
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] increasing font size breaking layout

2004-09-30 Thread Brian Duchek
I use this web site for a quick preview in Safari:

http://www.danvine.com/icapture/



On Wed, 29 Sep 2004 23:07:18 -0400, Albert Gedraitis
[EMAIL PROTECTED] wrote:
 Cesar -
 
 Web users interested in your services will not be able to get much help
 if their browser is Safari 1.2.3.   Sorry, but on this browser your
 site is
 a mess.  Maybe someone else on the list can advise you what to do to
 make it Safari-accessible.
 
 Yours, Albert
 
 
 --
 
 
 On Sep 28, 2004, at 4:41 AM, cesar | cesargarcia.com wrote:
 
 
  Yes, if all elements are proportional the layouts never break, increase
  or decrease size as same the font.
 
  Take a look: http://www.gestoriagarcia.net
 
  It's my latest work, incerase or decrease the size.
 
  Sorry for my english.
 
  cesar | cesargarcia.com
  [EMAIL PROTECTED]
 
  **
  The discussion list for  http://webstandardsgroup.org/
 
  Proud presenters of Web Essentials 04 http://we04.com/
   Web standards, accessibility, inspiration, knowledge
  To be held in Sydney, September 30 and October 1, 2004
 
   See http://webstandardsgroup.org/mail/guidelines.cfm
   for some hints on posting to the list  getting help
  **
  -Mensaje original-
  De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En
  nombre de Andrew Thompson
  Enviado el: martes, 28 de septiembre de 2004 8:33
  Para: [EMAIL PROTECTED]
  Asunto: Re: [WSG] increasing font size breaking layout
 
  My understanding is that if all elements are relative/proportional, the
  layouts should never break.
 
  --
 
  On Tuesday, 28 September 2004 4:14 PM, Focas, Grant
  [EMAIL PROTECTED] wrote:
  I was wondering if people had any opinions on when its
  acceptable if at all for a layout to break when users increase
  font size.
 
  Sites I am working on look fine if text is increased or
  decreased 1 or 2 times but when they are increased repeatedly
  the layout goes a bit whacky in some browsers (Netscape 6.2 on
  PC, IE5 Mac). Specifically, elements which are absolutely
  positioned get overlapped by wrapped list navigation.
 
  It seems to me that this only happens when text gets extremely
  large on small resolution screens and therefore I shouldn't
  worry too much, but is extreme all in the eye of the beholder?
 
  Grant Focas
  **
  This message is intended for the addressee named and may contain
  privileged information or confidential information or both. If you
  are not the intended recipient please delete it and notify the sender.
  **
  **
  The discussion list for  http://webstandardsgroup.org/
 
  Proud presenters of Web Essentials 04 http://we04.com/
  Web standards, accessibility, inspiration, knowledge
  To be held in Sydney, September 30 and October 1, 2004
 
  See http://webstandardsgroup.org/mail/guidelines.cfm
  for some hints on posting to the list  getting help
  **
 
 
 
 
  **
  The discussion list for  http://webstandardsgroup.org/
 
  Proud presenters of Web Essentials 04 http://we04.com/
   Web standards, accessibility, inspiration, knowledge
  To be held in Sydney, September 30 and October 1, 2004
 
   See http://webstandardsgroup.org/mail/guidelines.cfm
   for some hints on posting to the list  getting help
  **
 
  **
  The discussion list for  http://webstandardsgroup.org/
 
  Proud presenters of Web Essentials 04 http://we04.com/
   Web standards, accessibility, inspiration, knowledge
  To be held in Sydney, September 30 and October 1, 2004
 
   See http://webstandardsgroup.org/mail/guidelines.cfm
   for some hints on posting to the list  getting help
  **
 
 
 **
 The discussion list for  http://webstandardsgroup.org/
 
 Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge
 To be held in Sydney, September 30 and October 1, 2004
 
 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
 **
 
 



-- 
Brian Duchek
=-=-=-=-=-=-=-=
e: [EMAIL PROTECTED]
c: 847.809.2140
w: www.inquiline.com
=-=-=-=-=-=-=-=
**
The discussion list for  http://webstandardsgroup.org/

Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge

[WSG] best way to format Skip Nav link

2004-09-29 Thread Brian Duchek
Hi there group of gurus and list lurkers.

What's the best way to fomat a skip navigation link at the top of a
page so it doesn't appear in modern/styled browsers, but is still
accessible to small-screen / mobile platforms and reduced-ability
environments (screen readers and the like)?

I've seen different approaches, but am getting confused by the details
I pick up here and there.

display:none;

visibility: hide;

height:1px; width:1px;

position:absolue; top: -20px left:0;

Thanks in advance for your input.

-- 
Brian Duchek
=-=-=-=-=-=-=-=
e: [EMAIL PROTECTED]
c: 847.809.2140
w: www.inquiline.com
=-=-=-=-=-=-=-=
**
The discussion list for  http://webstandardsgroup.org/

Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] Empty DT's?

2004-09-06 Thread Brian Duchek
My memory re: the previous thread is fuzzy, but let me pose a question anyway.

What's the reason to include the empty dt?  Can't you just remove it?

While it may go against the simplist interpretation of a defintion
list (i.e. a defintion title followed by the defintion data) it seems
like the definition list you want to create has an exception.  I
wouldn't call it an incorrect usage of the definition list, just a
usage that fits the semantic needs of your data.

Unless there's some other reason to include the empty tag?


On Sun, 05 Sep 2004 18:33:30 +0200, Mordechai Peller [EMAIL PROTECTED] wrote:
 Related to my last thread (Fake link,...), I'm debating which is the
 better choice: using a consistent framework, but have an (usually) empty
 dt, or use a ul for the top level? Here's what the code would look like:
 
 *dl
 dt!--optional Menu Heading--/dt
 dda href=opt1.htmlOpt1/a/dd
 dd
 dl
 dtSub-Menu Heading Opt2/dt
 dda href=opt2a.htmlOpt2a/a/dd
 dd
 dl
 dtSub-Menu Heading Opt2b/dt
 dda href=opt2b1.htmlOpt2b1/a/dd
 dda href=opt2b2.htmlOpt2b2/a/dd
 /dl
 /dd
 dd**a href=opt2c.htmlOpt2c/a/dd**
 dl
 /dd
 dd**a href=opt1.htmlOpt1/a/dd**
 dl
 
 The dt's are the headings and the dd's are the links. Very consistent
 and very semantic (except for the first empty dt). It may even simplify
 scripting because it's consistent.
 
 The alternative is to use a ul for the top level:
 
 ul
 li**a href=opt1.htmlOpt1/a**/li
 li
 dl
 dt**Sub-Menu Heading Opt2**/dt**
 dd**a href=opt2a.htmlOpt2a/a**/dd
 etc...
 
 In**consistent**, but no empty dt's.
 ***
 **
 The discussion list for  http://webstandardsgroup.org/
 
 Proud presenters of Web Essentials 04 http://we04.com/
  Web standards, accessibility, inspiration, knowledge
 To be held in Sydney, September 30 and October 1, 2004
 
  See http://webstandardsgroup.org/mail/guidelines.cfm
  for some hints on posting to the list  getting help
 **
 
 



-- 
Brian Duchek
=-=-=-=-=-=-=-=
e: [EMAIL PROTECTED]
c: 847.809.2140
w: www.inquiline.com
=-=-=-=-=-=-=-=
**
The discussion list for  http://webstandardsgroup.org/

Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**