Tim Schilling

@circus2271 If the bug here is that using the mobile version of the site and clicking the buttons multiple times results in the extra utilities inconsistently showing the other options,...

@circus2271 I think this is a byproduct of Browser Developer Tool's "Touch Simulation" feature and then clicking quickly. I see two events in the console when logging them on this...

@circus2271 Can you include a series of steps to reproduce this that isn't just a video please? I'm seeing what I would consider weird behavior on my phone with the...

@circus2271 thank you for that clarification! I was getting tripped up earlier by the term "double-click". I assumed that mean two very quick clicks in succession. Not two separate clicks.

cc: @thibaudcolas @nanorepublica @benjaoming as chairs of the relevant WG's. This is a minor thing, but helpful to interested folks.

Sorry, my note was short, I noticed this while doing something else and didn't spend the proper amount of time writing this up. There's no urgency to this. Thanks for...

> I think for the specific problems that have been raised here, there are multiple possible solutions and it feels like there's room to discuss what the best solutions would...

> I kept this part of the code intentionally, because I would argue that having access to the access token within the request(-session) is an important feature. I think the...

The only reason that I can come up with to not store the token is to avoid allowing the library to do more with the API as a part of...

And now I'm having second thoughts around security concerns. If we start storing the access token in the session, we're making a choice for all users of the library. That...