On Thursday 2006-09-21 11:43 -0400, Zoe M. Gillenwater wrote: > I have a form that I structured using a div wrapped around each > label-input pair. I floated the labels, so in order to make the divs > contain the floats, I added overflow: auto to them. This worked fine, > but it resulted in the divs receiving focus as I tried to tab from form > field to form field in Firefox. This was mildly annoying, so I replaced > it with floating the divs, which also contained the floats and didn't > have such a side effect. > > But I'm curious whether Firefox's behavior is correct. Are elements with > overflow: auto supposed to receive focus? Or are they not? Or is it just > one of those things not specified and left up the browsers themselves? I > couldn't find anything about it on w3.org, but I'm admittedly not the > best at looking around there.
Given that receiving focus is the only way for a user to scroll an element without a mouse, I think they should receive focus. Our current behavior is that elements with 'overflow: scroll' or 'overflow: auto' receive focus, but elements with 'overflow: hidden' do not. It would be possible to make elements with 'overflow:auto' focusable only if there was actually overflow. However, I think this would be a bad idea for users, since users get used to keyboard navigation patterns on pages they visit regularly. Whether something has enough content to overflow can vary depending on varying content (such as "news" content changing over time) or changing conditions (different browser window widths). On Thursday 2006-09-21 13:08 -0300, Manuel Razzari wrote: > Just a random guess, but maybe here's the explanation for firefox's behavior: > https://bugzilla.mozilla.org/show_bug.cgi?id=97283 > > Check after comment #50. That was a side discussion on a mostly unrelated bug; the bug about making them focusable was elsewhere: https://bugzilla.mozilla.org/show_bug.cgi?id=254966 (I just changed the summary of the bug to reflect what it was really about. Bugs often end up keeping the original summary given by the reporter before the problem was well understood, which can make them harder to find.) On Thursday 2006-09-21 13:01 -0400, Zoe M. Gillenwater wrote: > I read everything from comment 50 on, and I'm just more confused. :-) > First of all, I'm not clear if this fix is even in current versions of > Firefox. Do you know? The last comments are still people complaining The fix to 97283 is in Firefox 1.5, but not 1.0. The fix to 254966 was in Firefox 1.0. -David -- L. David Baron <URL: http://dbaron.org/ > Technical Lead, Layout & CSS, Mozilla Corporation
pgp5fc2OTS09X.pgp
Description: PGP signature
______________________________________________________________________ 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/
