Cross Browser Compatiblity with Firefox 4 with ol > li / overflow: auto; #524

Closed
RobertLowe opened this Issue Mar 22, 2011 · 3 comments

2 participants

@RobertLowe

Going to post this on Bugzilla but:

With the introduction of the new Firefox 4 release, it induces an odd behavior, giving focus to li elements of a ol with overflow: auto;

form.formtastic fieldset > ol > li { overflow:auto; } /* clearing contained floats */

Regards

@justinfrench

Oh fun! Will investigate. Off the top of my head, it's only necessary to clear the floats if you're styling the containing element that has the overflow:auto; hack. You could try replacing overriding that with overflow:visible;.

If you find an acceptable work-around, PLEASE update this issue to save me some work :)

@RobertLowe

Busy consulting right now, I'll fork a fix and update you tonight if you don't beat me to the punch

@justinfrench
Owner

Ok, looks like there's still no fix (and not much noise about this) online. Was able to repeat the issue in FF4, and was able to resolve the issue by changing the overflow hack to overflow:hidden, which seems to be acceptable according to this article on Quirks Mode.

@justinfrench justinfrench added a commit that closed this issue May 7, 2011
@justinfrench Work-around for Firefox 4 giving focus to the <li> wrapper (fixes #524).
http://www.quirksmode.org/css/clearing.html states that auto and hidden work, quick test in major browsers confirms
b230629
@trimentor trimentor pushed a commit that referenced this issue May 11, 2011
@justinfrench Work-around for Firefox 4 giving focus to the <li> wrapper (fixes #524).
http://www.quirksmode.org/css/clearing.html states that auto and hidden work, quick test in major browsers confirms
f7ca5f5
@robertwahler robertwahler pushed a commit to robertwahler/formtastic that referenced this issue Jul 13, 2011
@justinfrench Work-around for Firefox 4 giving focus to the <li> wrapper (fixes #524).
http://www.quirksmode.org/css/clearing.html states that auto and hidden work, quick test in major browsers confirms
49de2d9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment