the problem is that we specifically used transform in a previous patch from @jugglinmike so that we could use the GPU to do animations (which we don't see on the device right now, probably because other properties are triggering a reflow), and therefore I don't want to use this here.

Plus this really feels like a hack, right ?

To prevent any future problem, I'd rather prevent this in JavaScript. We have a handy "isEditMode" boolean in "ThreadListUI". Should be possible to sneak in handleEvent and use preventDefault if we're in edit mode in the click event ? I think it should be enough.

I think it's safe to do it whatever the click event target is (because the thread link is probably the only "real" link we have and want to follow in the whole app, so preventDefault won't likely mess up with other behaviors) but if you want to be really safe you can check if `e.currentTarget` equals `this.container`.

And do a unit test ;)