remove Firefox-specific CSS workaround

[minrk]

The bug being worked around appears to be fixed either in CodeMirror or Firefox (tested with FF 29).

Importantly, the workaround appears to introduce incorrect behavior

closes #5192
closes #5364

[jdfreder]

Does this fix the other flexbox problems- i.e. #5675 ?

[minrk]

No, just the scrollbar stuff. I would like folks to test it - I was able to reproduce the scrollbar bad behavior, and removing this CSS did fix it, but I'm not entirely certain about the scope of affected cases. It doesn't appear that flexbox is relevant to these scrollbar issues at all.

As for the flexbox problems, I can't seem to replicate them in either Firefox or Chrome. Can you provide a test case that still reproduces the issue in master? Neither the steps in #5675 nor in #5612 produce empty space in master.

[jdfreder]

To reproduce the lingering empty space flexbox problem:
Use OSX with Chrome 24

1. New notebook.
2. Type multiple lines in cell that is created for you.
3. Delete lines, note cell size doesn't change.

It's interesting to note that I'm not able to reproduce on Linux w/ Chrome 21..... hmmmm

[ellisonbg]

I am still seeing this issue...

On Mon, May 12, 2014 at 3:01 PM, Jonathan Frederic <notifications@github.com

wrote:

To reproduce the lingering empty space flexbox problem:
OSX
Chrome 24

1. New notebook.
2. Type multiple lines in cell that is created for you.
3. Delete lines, note cell size doesn't change.

It's interesting to note that I'm not able to reproduce on Linux w/ Chrome
21..... hmmmm

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/5843#issuecomment-42894192
.

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

[minrk]

Do you mean Chrome 34? 24 is a year old. This doesn't seem to be reproducible on Chrome 36.0.1976.2.

@ellisonbg what browser/version?

[jdfreder]

Do you mean Chrome 34? 24 is a year old

Yes, sorry

[minrk]

Okay. I can reproduce it in Chrome 34 (stable), but not Chrome 35 (β), 36 (dev), Firefox 29, or Safari 7.0.3. That suggests it's a browser bug, and better yet an already fixed browser bug. In that case, my inclination is to leave it and wait for the next Chrome release, which should be in a couple of weeks.

[mbewley]

I still see this on Firefox 29 (Ubuntu 14.04 version), and IPython 2.0.

[jdfreder]

I still see this on Firefox 29 (Ubuntu 14.04 version), and IPython 2.0.

The fix is in master, the next release to include it will be 2.1 .