The pressed state sometimes is triggered in a runnable internally and might run after the item view has been detached.

Comment on attachment 8511998 [details] [diff] [review] Avoid NPE on parent when tab strip item is pressed (r=mcomella) Review of attachment 8511998 [details] [diff] [review]: ----------------------------------------------------------------- (In reply to Lucas Rocha (:lucasr) from comment #0) > The pressed state sometimes is triggered in a runnable internally and might > run after the item view has been detached. This seems like a pretty hard-to-find side-effect for users of TwoWayView - perhaps there is some way to fix this upstream?

(In reply to Michael Comella (:mcomella) from comment #2) > Comment on attachment 8511998 [details] [diff] [review] > Avoid NPE on parent when tab strip item is pressed (r=mcomella) > > Review of attachment 8511998 [details] [diff] [review]: > ----------------------------------------------------------------- > > (In reply to Lucas Rocha (:lucasr) from comment #0) > > The pressed state sometimes is triggered in a runnable internally and might > > run after the item view has been detached. > > This seems like a pretty hard-to-find side-effect for users of TwoWayView - > perhaps there is some way to fix this upstream? This bug is specific to our UI because we invalidate the parent when one of the child views is pressed (to update the dividers). Not something that can/should be fixed upstream.