thr3ads.net - Rails spinoffs - Overriding <select multiple="multiple"> default behaviour [Mar 2008]

If this information is useful, please help other people find it:
Share via:

James

2008-Mar-11 23:22 UTC

Overriding <select multiple="multiple"> default behaviour

I''d like to override the ctrl + click behavior of a select multiple
listbox, so that each clicked item remains clicked without using the
ctrl key.  Clicking on a selected option would deselect it.

I''m trying to use Event.stop() to interrupt the default behavior, but
I must not understand the correct spot to do this.  Below is a
variation of what I''ve been trying so far without success. 
I''d
appreciate a pointer in the proper direction.

"statusList" is the id of the select multiple list box.  The function
is binding to the clicked option element.

        document.observe(''dom:loaded'', function() {
            $(''statusList'').observe(''click'',
toggleOption.bindAsEventListener(this));
        });


        function toggleOption(e){
            Event.stop(e);
            var myElement =  Event.element(e);
            myElement.selected = !myElement.selected;
        }
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Shakakai

2008-Mar-12 06:25 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

Give event.preventDefault() a try. That should stop the default
behavior associated with an event from occurring.

Cheers,
Todd

On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I''d like to override the ctrl + click behavior of a select
multiple
> listbox, so that each clicked item remains clicked without using the
> ctrl key.  Clicking on a selected option would deselect it.
>
> I''m trying to use Event.stop() to interrupt the default behavior,
but
> I must not understand the correct spot to do this.  Below is a
> variation of what I''ve been trying so far without success. 
I''d
> appreciate a pointer in the proper direction.
>
> "statusList" is the id of the select multiple list box.  The
function
> is binding to the clicked option element.
>
>         document.observe(''dom:loaded'', function() {
>            
$(''statusList'').observe(''click'',
> toggleOption.bindAsEventListener(this));
>         });
>
>         function toggleOption(e){
>             Event.stop(e);
>             var myElement =  Event.element(e);
>             myElement.selected = !myElement.selected;
>         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

James

2008-Mar-12 16:10 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

Thanks Todd,

Unfortunately, the select box continues to deselect my previous
selection on each click.  I wonder if I''m assuming too much about the
ability to prevent that action.  I suppose that there may be some
event behaviors that are above the reach of event.stop/preventDefault
and that I''ll have to manage the situation after the fact.


On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Give event.preventDefault() a try. That should stop the default
> behavior associated with an event from occurring.
>
> Cheers,
> Todd
>
> On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > I''d like to override the ctrl + click behavior of a select
multiple
> > listbox, so that each clicked item remains clicked without using the
> > ctrl key.  Clicking on a selected option would deselect it.
>
> > I''m trying to use Event.stop() to interrupt the default
behavior, but
> > I must not understand the correct spot to do this.  Below is a
> > variation of what I''ve been trying so far without success. 
I''d
> > appreciate a pointer in the proper direction.
>
> > "statusList" is the id of the select multiple list box.  The
function
> > is binding to the clicked option element.
>
> >         document.observe(''dom:loaded'', function() {
> >            
$(''statusList'').observe(''click'',
> > toggleOption.bindAsEventListener(this));
> >         });
>
> >         function toggleOption(e){
> >             Event.stop(e);
> >             var myElement =  Event.element(e);
> >             myElement.selected = !myElement.selected;
> >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

T.J. Crowder

2008-Mar-12 17:34 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

@Shakakai:
> Give event.preventDefault() a try.
Event.stop does both preventDefault and stopPropagation, so he was
already doing that.

@James:

Have you tried hooking the event during capture rather than bubbling?
(It may not be reliable or cross-browser...)  If so and you still
can''t prevent the default, it sounds like you might have to maintain
your own state information for which items are selected and re-assert
that on each click, which seems unpleasant. :)  If you''re going that
far, I wonder if you want to just replace the select box with
something custom, although then you may have a11y issues if you''re
supporting a11y.

FWIW
--
T.J. Crowder
tj / crowder software / com

On Mar 12, 4:10 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Thanks Todd,
>
> Unfortunately, the select box continues to deselect my previous
> selection on each click.  I wonder if I''m assuming too much about
the
> ability to prevent that action.  I suppose that there may be some
> event behaviors that are above the reach of event.stop/preventDefault
> and that I''ll have to manage the situation after the fact.
>
> On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > Give event.preventDefault() a try. That should stop the default
> > behavior associated with an event from occurring.
>
> > Cheers,
> > Todd
>
> > On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > I''d like to override the ctrl + click behavior of a
select multiple
> > > listbox, so that each clicked item remains clicked without using
the
> > > ctrl key.  Clicking on a selected option would deselect it.
>
> > > I''m trying to use Event.stop() to interrupt the default
behavior, but
> > > I must not understand the correct spot to do this.  Below is a
> > > variation of what I''ve been trying so far without
success.  I''d
> > > appreciate a pointer in the proper direction.
>
> > > "statusList" is the id of the select multiple list box.
The function
> > > is binding to the clicked option element.
>
> > >         document.observe(''dom:loaded'',
function() {
> > >            
$(''statusList'').observe(''click'',
> > > toggleOption.bindAsEventListener(this));
> > >         });
>
> > >         function toggleOption(e){
> > >             Event.stop(e);
> > >             var myElement =  Event.element(e);
> > >             myElement.selected = !myElement.selected;
> > >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

James

2008-Mar-12 18:37 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

Thanks T.J.,

This project does have to support IE so I didn''t attempt event
capturing.  I''ve been working on a "state saving" solution as
you
described and pondering a custom object too.  I''m not familiar with
the term "11y" but, from the context, I assume it means a long running
project that will need to be maintained after I''m hit by a bus.  That
does describe this project, so there''s my dilemma.  Certainly,
documentation is out of the question ;)

Thanks a ton for the suggestions.


On Mar 12, 11:34 am, "T.J. Crowder"
<tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> @Shakakai:
>
> > Give event.preventDefault() a try.
>
> Event.stop does both preventDefault and stopPropagation, so he was
> already doing that.
>
> @James:
>
> Have you tried hooking the event during capture rather than bubbling?
> (It may not be reliable or cross-browser...)  If so and you still
> can''t prevent the default, it sounds like you might have to
maintain
> your own state information for which items are selected and re-assert
> that on each click, which seems unpleasant. :)  If you''re going
that
> far, I wonder if you want to just replace the select box with
> something custom, although then you may have a11y issues if you''re
> supporting a11y.
>
> FWIW
> --
> T.J. Crowder
> tj / crowder software / com
>
> On Mar 12, 4:10 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > Thanks Todd,
>
> > Unfortunately, the select box continues to deselect my previous
> > selection on each click.  I wonder if I''m assuming too much
about the
> > ability to prevent that action.  I suppose that there may be some
> > event behaviors that are above the reach of event.stop/preventDefault
> > and that I''ll have to manage the situation after the fact.
>
> > On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > Give event.preventDefault() a try. That should stop the default
> > > behavior associated with an event from occurring.
>
> > > Cheers,
> > > Todd
>
> > > On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > I''d like to override the ctrl + click behavior of a
select multiple
> > > > listbox, so that each clicked item remains clicked without
using the
> > > > ctrl key.  Clicking on a selected option would deselect it.
>
> > > > I''m trying to use Event.stop() to interrupt the
default behavior, but
> > > > I must not understand the correct spot to do this.  Below is
a
> > > > variation of what I''ve been trying so far without
success.  I''d
> > > > appreciate a pointer in the proper direction.
>
> > > > "statusList" is the id of the select multiple list
box.  The function
> > > > is binding to the clicked option element.
>
> > > >         document.observe(''dom:loaded'',
function() {
> > > >            
$(''statusList'').observe(''click'',
> > > > toggleOption.bindAsEventListener(this));
> > > >         });
>
> > > >         function toggleOption(e){
> > > >             Event.stop(e);
> > > >             var myElement =  Event.element(e);
> > > >             myElement.selected = !myElement.selected;
> > > >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Shakakai

2008-Mar-12 21:07 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

It might be faster to just write your own form control. Create a list
(ul) of items the user can select and add mouse events to them to
change the className as appropriate for selected/nonselected. Dump the
result into a hidden form element, or Ajax call, and you should be all
set. The "right" approach depends largely on what you need to support
(graceful degradation, etc.). Good Luck.

-Todd

ps - T.J. thanks for pointing out the Event.stop info.

On Mar 12, 2:37 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Thanks T.J.,
>
> This project does have to support IE so I didn''t attempt event
> capturing.  I''ve been working on a "state saving"
solution as you
> described and pondering a custom object too.  I''m not familiar
with
> the term "11y" but, from the context, I assume it means a long
running
> project that will need to be maintained after I''m hit by a bus. 
That
> does describe this project, so there''s my dilemma.  Certainly,
> documentation is out of the question ;)
>
> Thanks a ton for the suggestions.
>
> On Mar 12, 11:34 am, "T.J. Crowder"
<tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > @Shakakai:
>
> > > Give event.preventDefault() a try.
>
> > Event.stop does both preventDefault and stopPropagation, so he was
> > already doing that.
>
> > @James:
>
> > Have you tried hooking the event during capture rather than bubbling?
> > (It may not be reliable or cross-browser...)  If so and you still
> > can''t prevent the default, it sounds like you might have to
maintain
> > your own state information for which items are selected and re-assert
> > that on each click, which seems unpleasant. :)  If you''re
going that
> > far, I wonder if you want to just replace the select box with
> > something custom, although then you may have a11y issues if
you''re
> > supporting a11y.
>
> > FWIW
> > --
> > T.J. Crowder
> > tj / crowder software / com
>
> > On Mar 12, 4:10 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > Thanks Todd,
>
> > > Unfortunately, the select box continues to deselect my previous
> > > selection on each click.  I wonder if I''m assuming too
much about the
> > > ability to prevent that action.  I suppose that there may be some
> > > event behaviors that are above the reach of
event.stop/preventDefault
> > > and that I''ll have to manage the situation after the
fact.
>
> > > On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > Give event.preventDefault() a try. That should stop the
default
> > > > behavior associated with an event from occurring.
>
> > > > Cheers,
> > > > Todd
>
> > > > On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > > I''d like to override the ctrl + click behavior
of a select multiple
> > > > > listbox, so that each clicked item remains clicked
without using the
> > > > > ctrl key.  Clicking on a selected option would deselect
it.
>
> > > > > I''m trying to use Event.stop() to interrupt
the default behavior, but
> > > > > I must not understand the correct spot to do this. 
Below is a
> > > > > variation of what I''ve been trying so far
without success.  I''d
> > > > > appreciate a pointer in the proper direction.
>
> > > > > "statusList" is the id of the select multiple
list box.  The function
> > > > > is binding to the clicked option element.
>
> > > > >        
document.observe(''dom:loaded'', function() {
> > > > >            
$(''statusList'').observe(''click'',
> > > > > toggleOption.bindAsEventListener(this));
> > > > >         });
>
> > > > >         function toggleOption(e){
> > > > >             Event.stop(e);
> > > > >             var myElement =  Event.element(e);
> > > > >             myElement.selected = !myElement.selected;
> > > > >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

James

2008-Mar-12 21:43 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

I''ve achieved my goal without having resolved the Event.stop()
question.  If anyone''s interested, this is how I''m allowing
multiple
selections in a <select> list box without using ctrl click.  As T.J.
suggested, I''m saving state in a separate array.  Here''s the
javascript:

var statusOptions = new Array();  // this array stores the selected
state for the options in the <select id="statusList"> list

        document.observe(''dom:loaded'', function() {
            init();  // setup the Array''s values once the
<select>
list has loaded
            $(''statusList'').observe(''click'',
toggleOption);  //
observing clicks on the <select> list
        });

        function init() {  // setting up the initial values and the
size of the array from the select element
            $$(''#statusList option'').each(function(j, index) {
                statusOptions[index] = j.selected;
            });
        }

        function toggleOption(){
            var i = $(''statusList'').selectedIndex;
            statusOptions[i] = !statusOptions[i];   // toggle the
boolean in the Array to represent the selected status
            $$(''#statusList option'').each(function(opt){
	        opt.selected = statusOptions[opt.index];   //  overwrite the
selected state of the <option>''s from the values in the array.
            });
        }

@Todd:

In retrospect, I think writing the custom object would have been more
fun and would eliminate an instantaneous flicker that exists in my
solution.  If time permits, I may redo this.

Thanks!



On Mar 12, 3:07 pm, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> It might be faster to just write your own form control. Create a list
> (ul) of items the user can select and add mouse events to them to
> change the className as appropriate for selected/nonselected. Dump the
> result into a hidden form element, or Ajax call, and you should be all
> set. The "right" approach depends largely on what you need to
support
> (graceful degradation, etc.). Good Luck.
>
> -Todd
>
> ps - T.J. thanks for pointing out the Event.stop info.
>
> On Mar 12, 2:37 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > Thanks T.J.,
>
> > This project does have to support IE so I didn''t attempt
event
> > capturing.  I''ve been working on a "state saving"
solution as you
> > described and pondering a custom object too.  I''m not
familiar with
> > the term "11y" but, from the context, I assume it means a
long running
> > project that will need to be maintained after I''m hit by a
bus.  That
> > does describe this project, so there''s my dilemma. 
Certainly,
> > documentation is out of the question ;)
>
> > Thanks a ton for the suggestions.
>
> > On Mar 12, 11:34 am, "T.J. Crowder"
<tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > @Shakakai:
>
> > > > Give event.preventDefault() a try.
>
> > > Event.stop does both preventDefault and stopPropagation, so he
was
> > > already doing that.
>
> > > @James:
>
> > > Have you tried hooking the event during capture rather than
bubbling?
> > > (It may not be reliable or cross-browser...)  If so and you still
> > > can''t prevent the default, it sounds like you might have
to maintain
> > > your own state information for which items are selected and
re-assert
> > > that on each click, which seems unpleasant. :)  If
you''re going that
> > > far, I wonder if you want to just replace the select box with
> > > something custom, although then you may have a11y issues if
you''re
> > > supporting a11y.
>
> > > FWIW
> > > --
> > > T.J. Crowder
> > > tj / crowder software / com
>
> > > On Mar 12, 4:10 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > Thanks Todd,
>
> > > > Unfortunately, the select box continues to deselect my
previous
> > > > selection on each click.  I wonder if I''m assuming
too much about the
> > > > ability to prevent that action.  I suppose that there may be
some
> > > > event behaviors that are above the reach of
event.stop/preventDefault
> > > > and that I''ll have to manage the situation after
the fact.
>
> > > > On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > > Give event.preventDefault() a try. That should stop the
default
> > > > > behavior associated with an event from occurring.
>
> > > > > Cheers,
> > > > > Todd
>
> > > > > On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > > > I''d like to override the ctrl + click
behavior of a select multiple
> > > > > > listbox, so that each clicked item remains clicked
without using the
> > > > > > ctrl key.  Clicking on a selected option would
deselect it.
>
> > > > > > I''m trying to use Event.stop() to
interrupt the default behavior, but
> > > > > > I must not understand the correct spot to do this.
Below is a
> > > > > > variation of what I''ve been trying so far
without success.  I''d
> > > > > > appreciate a pointer in the proper direction.
>
> > > > > > "statusList" is the id of the select
multiple list box.  The function
> > > > > > is binding to the clicked option element.
>
> > > > > >        
document.observe(''dom:loaded'', function() {
> > > > > >            
$(''statusList'').observe(''click'',
> > > > > > toggleOption.bindAsEventListener(this));
> > > > > >         });
>
> > > > > >         function toggleOption(e){
> > > > > >             Event.stop(e);
> > > > > >             var myElement =  Event.element(e);
> > > > > >             myElement.selected =
!myElement.selected;
> > > > > >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

T.J. Crowder

2008-Mar-13 09:43 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

James,

Glad to hear you sorted it out.
> I''m not familiar with
> the term "11y" but, from the context...
"a11y" = "accessibility" ("a" followed by 11
characters followed by
"y", kind of like i18n), e.g., being compatible with screen readers
for the blind, voice control for those with movement issues, etc.,
etc.
--
T.J. Crowder
tj / crowder software / com

On Mar 12, 6:37 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Thanks T.J.,
>
> This project does have to support IE so I didn''t attempt event
> capturing.  I''ve been working on a "state saving"
solution as you
> described and pondering a custom object too.  I''m not familiar
with
> the term "11y" but, from the context, I assume it means a long
running
> project that will need to be maintained after I''m hit by a bus. 
That
> does describe this project, so there''s my dilemma.  Certainly,
> documentation is out of the question ;)
>
> Thanks a ton for the suggestions.
>
> On Mar 12, 11:34 am, "T.J. Crowder"
<tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
>
>
> > @Shakakai:
>
> > > Give event.preventDefault() a try.
>
> > Event.stop does both preventDefault and stopPropagation, so he was
> > already doing that.
>
> > @James:
>
> > Have you tried hooking the event during capture rather than bubbling?
> > (It may not be reliable or cross-browser...)  If so and you still
> > can''t prevent the default, it sounds like you might have to
maintain
> > your own state information for which items are selected and re-assert
> > that on each click, which seems unpleasant. :)  If you''re
going that
> > far, I wonder if you want to just replace the select box with
> > something custom, although then you may have a11y issues if
you''re
> > supporting a11y.
>
> > FWIW
> > --
> > T.J. Crowder
> > tj / crowder software / com
>
> > On Mar 12, 4:10 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > Thanks Todd,
>
> > > Unfortunately, the select box continues to deselect my previous
> > > selection on each click.  I wonder if I''m assuming too
much about the
> > > ability to prevent that action.  I suppose that there may be some
> > > event behaviors that are above the reach of
event.stop/preventDefault
> > > and that I''ll have to manage the situation after the
fact.
>
> > > On Mar 12, 12:25 am, Shakakai
<cull...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > Give event.preventDefault() a try. That should stop the
default
> > > > behavior associated with an event from occurring.
>
> > > > Cheers,
> > > > Todd
>
> > > > On Mar 11, 7:22 pm, James
<JamesJReyno...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > > > I''d like to override the ctrl + click behavior
of a select multiple
> > > > > listbox, so that each clicked item remains clicked
without using the
> > > > > ctrl key.  Clicking on a selected option would deselect
it.
>
> > > > > I''m trying to use Event.stop() to interrupt
the default behavior, but
> > > > > I must not understand the correct spot to do this. 
Below is a
> > > > > variation of what I''ve been trying so far
without success.  I''d
> > > > > appreciate a pointer in the proper direction.
>
> > > > > "statusList" is the id of the select multiple
list box.  The function
> > > > > is binding to the clicked option element.
>
> > > > >        
document.observe(''dom:loaded'', function() {
> > > > >            
$(''statusList'').observe(''click'',
> > > > > toggleOption.bindAsEventListener(this));
> > > > >         });
>
> > > > >         function toggleOption(e){
> > > > >             Event.stop(e);
> > > > >             var myElement =  Event.element(e);
> > > > >             myElement.selected = !myElement.selected;
> > > > >         }--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

James

2008-Mar-13 15:46 UTC

head link

Re: Overriding <select multiple="multiple"> default behaviour

>"a11y" = "accessibility" ("a" followed by 11
characters followed by
>"y", kind of like i18n), e.g., being compatible with screen
readers
>for the blind, voice control for those with movement issues, etc.
Oh!  Now I understand.  Thanks for enlightening me.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Rails spinoffs - Mar 2008 - Overriding <select multiple="multiple"> default behaviour

Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour

Re: Overriding <select multiple="multiple"> default behaviour