timbell

(NB sometimes the problem doesn't manifest itself visually, but in this case the first tab is unselectable until another tab is selected.)

@farfromrefug Not sure I understand - your test app doesn't use the [tabs](https://github.com/nativescript-community/ui-material-components/tree/master/packages/tabs) component? Did you try the test app that I posted?

@farfromrefug yes, that fixes it - thanks! (there's a continuous `setSelectedPosition` console log message now - maybe left in by mistake?)

@felixkrautschuk I' do the same as @jessorlisa . It works around the problem satisfactorily.

Sure, I'll do a pull request. I've been running the following change in 8.2 and 7.9.1 (my "prod") without any issues. I think it expresses the intent more clearly. ```...

Reproduced with Chrome + Firefox on Windows and Chrome on Android. I'm pretty sure it's not a client issue - the page refreshing just seems to be a reasonably reliable...

Yes, @michaelherger, that's right. (There may be other ways that can cause the `$delayedResponse = 0` code path in `Slim::Web::Cometd::handler` to be followed, however.) A simple fix might be to...

I just hit the same issue - I'm using bootstrap3 which does `.list-group-item:last-child { margin-bottom: 0; ...`. Not particularly satisfactory, but the following code changes will ensure that the (hidden)...

Sorry, the above is badly broken - please don't use it!. Detaching/reattaching the original element rather than hiding it during dragging does seem to work well: In $moveUpdate: ``` //...

I came across the same problem. It's described here: http://meyerweb.com/eric/thoughts/2011/09/12/un-fixing-fixed-elements-with-css-transforms/ You can see that the original codepen works ok in IE11, but not in Chrome or Firefox. I worked around...