Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-07 Thread Ian Eiloart
--On 6 July 2006 16:45:26 -0400 emf <[EMAIL PROTECTED]> wrote: > > Can you help me understand the basis for this claim? I have looked into > the matter somewhat deeply and this works in every browser I have come > across that supports JavaScript: And the ones that don't? -- Ian Eiloart IT Se

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Brad Knowles
Barry wrote: > I'm sure a lot of that comes from me, inspired by early experience > and my own general paranoid dinosaurism. OTOH, I remember Guido > telling me a few years ago that I might as well give up on that one, > and so I have -- mostly. That's why I love NoScript so much :). No, you're

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 6, 2006, at 4:45 PM, emf wrote: > On somewhat of a side note, I have heard a certain amount of antipathy > towards JavaScript in this forum. I know it was unpleasant in the late > '90s, but it is much better and more cross-browser these days.

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Bryan Carbonnell
On 7/6/06, emf <[EMAIL PROTECTED]> wrote: > Bryan Carbonnell wrote: > > > I have to agree with Brad on this. > > > > An option may be to give the site admin the ability to turn the JS > > on/off site wide with a mm_cfg.py variable. > > I'm a little reluctant to add another bit flip to mm_cfg when y

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread emf
Bryan Carbonnell wrote: > I have to agree with Brad on this. > > An option may be to give the site admin the ability to turn the JS > on/off site wide with a mm_cfg.py variable. I'm a little reluctant to add another bit flip to mm_cfg when you'll be able to delete the .js files or forbid access

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread emf
Brad Knowles wrote: > I would much prefer to do this without JavaScript. Because you can't > guarantee that you know the way that page would be rendered Can you help me understand the basis for this claim? I have looked into the matter somewhat deeply and this works in every browser I have come

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Bryan Carbonnell
On 7/6/06, Laura Carlson <[EMAIL PROTECTED]> wrote: > > An option may be to give the site admin the ability to turn the JS > > on/off site wide with a mm_cfg.py variable. > > Default set to off? That'd be my preference. -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Laura Carlson
Ethan wrote: >>> One example is keeping extraneous text hidden until it is >>> selected; I imagine that someone using a screen reader/portable >>> device would appreciate being able to read a "overview" page >>> variant and then being able to expand as necessary. An overview at the top of a page

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Bryan Carbonnell
On 7/6/06, Brad Knowles <[EMAIL PROTECTED]> wrote: > Ethan wrote: > > > One example is keeping extraneous text hidden until it is selected; I > > imagine that someone using a screen reader/portable device would > > appreciate being able to read a "overview" page variant and then being > > able to e

Re: [Mailman-Developers] Accessible DOM manipulations

2006-07-06 Thread Brad Knowles
Ethan wrote: > One example is keeping extraneous text hidden until it is selected; I > imagine that someone using a screen reader/portable device would > appreciate being able to read a "overview" page variant and then being > able to expand as necessary. I would much prefer to do this without Ja

[Mailman-Developers] Accessible DOM manipulations

2006-07-05 Thread emf
Laura Carlson wrote: > --On Wednesday, July 5, 2006 8:54 PM +0200 emf wrote: > >> Are you suggesting I provide *no* link for the >> screen-reader-with-javascript client and let them at some point >> figure out that they're not seeing what's going on and thus turn off >> javascript? >> >> That see