No, the question is not difficult to understand at all (the example provided is excellent) but it is not easy to answer, and as I've seen so far, not the easiest topic to research either. I also read most of the comments from #50 on and the only thing that appears to be clear-cut is that this is eaither a bug or how Firefox was intended to work.
Of utmost interest is whether or not there are published Firefox specs that can be perused at will. I would think that would put this to rest right quick! Ralph ----- Original Message ----- From: "Zoe M. Gillenwater" <[EMAIL PROTECTED]> Date: Thursday, September 21, 2006 12:55 Subject: Re: [css-d] overflow: auto elements receiving focus when tabbing To: css-d@lists.css-discuss.org > Mark J. Reed wrote: > > On 9/21/06, Zoe M. Gillenwater <[EMAIL PROTECTED]> > wrote:>> Well, I agree with you, but that's hardly relevant. > > > > I dunno. Independently coming up with the same > expectation goes > > toward the validity of that expectation . . . > > Not necessarily. Take margin collapsing, for instance. Almost no > one > would think it's intuitive until it was explained to them, and > many > still wouldn't agree with it. Just because we think elements > with > overflow: auto that don't actually overflow shouldn't receive > focus when > tabbing doesn't mean the standards writers or browser developers > agree > with us. In fact, the Firefox developers obviously don't! So > again, I'm > not interested in what people think should happen -- and that's > not > on-topic for this list -- but rather what really should happen. > Or, as I > said in my original email, I would like to know if this is > something > that no one has specified what should happen, and it's just > completely > up to the browsers (very possible). > > > > >> Firefox doesn't do what we think it should do, and my > question, > >> again, is whether it is > >> correct for it to do what it is doing. > > > > Correct according to what, though? CSS doesn't even > specify what user > > agents are supposed to do with "overflow: auto"; getting down > to how > > keyboard shortcuts behave is way out of scope. Is there > a formal spec > > for Gecko? > > Yes, the W3 specs. :-) Again, though, I've acknowledged that > there may > be no spec that specifies what a browser should do in this case, > and > thus it would be up to the browser to decide. I just want to > know if > this is or isn't the case. > > Does everyone finally understand my question? I didn't think it > was that > complicated. :-) > > Zoe > > -- > Zoe M. Gillenwater > Design Services Manager > UNC Highway Safety Research Center > http://www.hsrc.unc.edu > > > ______________________________________________________________________ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 > List wiki/FAQ -- http://css-discuss.incutio.com/ > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
