As you'll see, there is a difference in the way firefox and chrome compute the css top property of split-handler : firefox makes it 87px while chrome makes it auto (and gets a good rendering). The dirty trick I found was to comment the line 133 of splitter.js:
handler.css(topProp, elementTop);
Maybe it's a bug in firefox, but I thought it might be useful to document this... It happenned to me while using the splitter after a bootstrap jumbotron.
I managed to understand the problem better, see https://bugzilla.mozilla.org/show_bug.cgi?id=967803
edit : this is a bug in Webkit, so Firefox is right in its behaviour, splitter shouldn't rely on Webkit's behaviour.
This very simple example fails in Firefox (24 and 26):
As you'll see, there is a difference in the way firefox and chrome compute the css
top
property of split-handler : firefox makes it87px
while chrome makes itauto
(and gets a good rendering). The dirty trick I found was to comment the line 133 of splitter.js:Maybe it's a bug in firefox, but I thought it might be useful to document this... It happenned to me while using the splitter after a bootstrap jumbotron.