Just file a new task once you have the necessary information.

Please reopen. It's holidays / long weekend nowadays (CA, US, CZ), so I can't provide ther required stuff immediately. We'll get back to it with more descriptions soon. Thanks.

This didn't have a reliable reproduction case, but from limited spot-checking of production logs I don't see it happening any more.

Yeah broadly, we want to supply everything as first class in Phabricator. That means everything benefits from the organization, policies, notifications, links, etc. Right now we have Phriction (wiki) and Phame (blog) which probably could take over two of your external systems. We don't have a forum, but would consider building it down the road if enough interest arrises.

We need a root problem description to move forward here.

@avivey's answer is correct.

Thanks for the report! I think this should be fixed in HEAD of master. Let us know if that doesn't work or you run into anything else.

(Okay. I'll try. Sorry, I am trying my best to cope up with your feature request rules.)

We also have Describing Root Problems which goes into this in a bit more detail, but we basically want you to take a huge step back and paint us a picture of what all happened before you ended up using Discourse.

My guess at the root problem is:

I am not sure I understand. I've also read https://secure.phabricator.com/book/phabcontrib/article/describing_problems/ by the way. I tried to explain the problem as extensive and concise as possible. You're free to totally disagree with me, but I wouldn't know how to describe the problem better. I am ready to elaborate, answer if there are any questions.

We don't consider "feature doesn't exist" to be a root problem.

Yes, that's why I mentioned the 'root problem'.

Did you read Contributing Feature Requests?

I found a workaround in the meantime: Press ` and then space (or any other key). The issue obviously is that ` is being sent like dead (combining) key on en-US keyboard layout.

https://secure.phabricator.com/book/phabricator/article/diffusion_managing/#branches

Just FYI, but on this install there's some weird rendering going on:

Firefox 44 / Ubuntu 15.04
Firefox 47.0.1 (64) Windows 8.1
Firefox 47.0.1 (64) Windows 10
Firefox 47.0.1 (64) macOS

Turns out that CustomFields sort of just work properly with EditEngine out of the box, so D16226 provides a technically-functional dashboard.panel.edit, which allows you to edit text panels like this, for example:

I don't think there's anything about this specific to Dashboards.

We haven't seen other confusion about this in context.

...which takes us back to accesskey...