Mr. Coffee

Adding "set fire to pillow" to the list of dangerous things my boys have done.

@snookca Wow, haven’t see you for song long. Had no idea you’d gone full Jesus.

@dj_georgie saw you mentioned some problems related to using Slack as a result of our use of the ARIA application role. Mind providing some additional detail to us via /feedback in Slack? Or by emailing us at feedback@slack.com.

@MarcoInEnglish @jcsteh @stommepoes The fix for this is now deployed to production.

So among the many other Slack #a11y glitches that make productivity tricky, as of today control+f6 no longer seems to work for me in some workspaces and the Slack message entry text box no longer has a label. Anyone else seeing this?

@jcsteh Just a note to let you know the fix for this has been deployed to production. Thanks again for the report, sorry for the bug and the delayed response.

@MarcoInEnglish @jcsteh @stommepoes Sounds great and thank you!

@MarcoInEnglish @jcsteh @stommepoes That is correct because that means a customer service agent is guaranteed to see it and route it to me

@jcsteh @MarcoInEnglish @stommepoes We’ve got wonderful people in customer service (@MissySB) who will make sure issues such as these are properly escalated to me

@todd @MarcoInEnglish @stommepoes So, serious question: I always try to avoid nagging people about the same bugs repeatedly, but it seems issues are legitimately getting lost (rather than just not being attended to at all). Would you prefer I just nag (once in a while) about bugs like these? :)

@jcsteh @MarcoInEnglish @stommepoes I think the problem is you are reporting them via Twitter. If you reported them via Slack using the feedback slash command they’d get reported to me and bugs would get filed

@jcsteh @stommepoes This one is my fault Jamie. For what it's worth: it is only broken in Firefox and I'll have a fix PR out tomorrow to fix this. Very sorry.

@stommepoes Yeah, this is with a browser. I'm using ctrl+f6 and it works on some Slack instances and not others.

.@sundress there is now a coffee shop in SF with piccolos on the menu!

@jcsteh @georgezamfir This one is my fault @jcsteh. I am sorry for this. I too have been struggling to repro this. I'll have another go at it today.

@georgezamfir Unfortunately, this just seems to happen arbitrarily; I can't figure out how to reliably "reproduce" it. All I know is that it is a serious productivity killer for me and is making me seriously consider asking for role=application to be disabled on our instance.

@georgezamfir Is there any ongoing work regarding the reliability of Slack keyboard shortcuts such as control+f6 and up/down arrows? I hit issues on a daily basis where control+f6 stops working, up/down arrows skip messages, etc. Have to reload to fix.

“You gotta have tight buns for girls to like you!” – Hudson Kloots, age 7

“Dada, can’t YOU just be the alpha?! You won’t get in trouble with Mommy.” – Hudson Kloots, age 7

“PUT DOWN THE NERF GUN AND PICK UP AN IPAD!”

@jcsteh @georgezamfir I will fix this one today Jamie.

@georgezamfir Oh, one more thing: the thread messages don't seem to get a role of document, so you don't get pushed into browse mode for those like you do for channel messages.

We’ve made some more keyboard improvements ⌨️ LEFT/RIGHT cursor keys now go in & out of threads UP/DOWN cursors keys now navigate through both messages & threads views We hope this makes it just a little easier to navigate Slack by keyboard ❤️

@jcsteh @georgezamfir Sorry for this. ctrl + f6 should re-focus the thread pane after you send a reply. I'll fix this. To work around, you'll have to press ctrl + f6 to focus the message pane, which will focus the root message of the thread and then press right arrow again.

@georgezamfir Hi! I might be missing something, but... how do you get back to the thread pane after writing a reply in a thread? So I find a thread in message list, hit right arrow, read replies, start typing a reply, then control+f6... which lands me in the message list, not the thread.

One of my favorite games at the grocery store: judge the contents of other people’s carts

@mikeindustries @SlackHQ @ptr @wwayneee Ugh, this bug is my fault Mike D. Sorry about that. BUT @ptr said he's going to make @wwayneee make the code change to fix it to ensure it goes out. (Gooooooo @wwayneee!)