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...

Ah, then it will be some of our local enhancements... Sorry for bothering then.

next batch is ready, should land tonight:

In the future, we might reasonably want to put tabindex="1" on the first input on form pages, like the "Edit Task" page, so that you could press tab once to quickly begin editing. If we put tabindex="1" on global search, the cost of making this change in the future will be much higher.

Phabricator has no such sidebar item. Where are you seeing this?

Good point, thanks for research. I was looking in some notes from research done several years ago, thus obviously no longer accurate.

Can you substantiate "f" being "typically used"? Here's what I see in use in the wild from a quick survey of popular sites and software:

Those are all about preferences and JavaScript handling...

This feature has a tiny impact and a huge support cost.

I can look in more detail when I'm back home. Kids have a picnic today.

That's what I plan. Just tested it on WXPx86 and FF 47.0.1 32bit and it works there.

The next step on this report would be for you to try to reproduce on a different environment.

And FF? And 32 or 64 bit?

Tested 8 and 10. I don't have Win7.

@chad Which version of Win & FF you use?

I don't see anything relevant there actually, could you please elaborate?

I can't reproduce on Windows, Chrome, FF, IE with en layouts.

See discussion in D15984.

Tested in both en and cs layouts.

/ was removed, see D15976 and the changelog:

Same problem :
Versions :
phabricator bc3ac3158448dfe966d05787fa9272f08ddc7faa (Fri, Jul 1)
arcanist 4d4d16f25985f133501f20fdddd183e525f00341 (Wed, Jun 29)
phutil dde2f74f2793f0216f0d76618ed335a9c802cfec (Fri, Jul 1)

In T11105#179265, @hach-que wrote:

This is solved with D11688, but it needs to be turned on globally (at the moment it's a per call option, which was added so that internally our custom unit test runner wouldn't deadlock).