I will try to fix this.

I think this would be useful for me from a project manager's role to have a clean saved query to show only assigned/unassigned tasks.

I have added a revision for this: D9754 still a ton of work to go but I'm willing to do whatever it takes to get this in a shippable condition :)

@chad, I made a basic implementation. It's horribly broken (the workboard should be in the "test") panel. I will be submitting a diff in sometime when I figure things out. But I'll need lot of help figuring some stuff out.

funnily the problem doesn't seem to be there on secure.phabricator.com. Maybe updating will fix the issue. Will re-open issue if it persists.

After we've been using phabricator for a while, we found the auto-save is a better approach to handling closing-browsers. We've had people who've started writing a comment and then changed their mind half way, and appreciated not getting a "are you sure you want to quit" nagging dialog.

I know this is a 8 month old issue. But tab key moving to the Submit button, as opposed to adding spaces is becoming a deal breaker for us while writing technical specifications on phriction, and also discussing code which frequently tend to have tab characters.

@chad - the autosave functionality is fantastic. I think this compensates for the close tab issue, except for the corner cases of when the AJAX request to remarkup is still pending.

@epriestley - unfortunately I'm not at my work machine to verify but from the screenshot, but it certainly does look like I'm zoomed out, based on the screenshots.

Closed by commit rP769e921e6541.

@epriestley, I was away for a while, but I would like to get back to updating this. But I notice that PhrequentTrackController::startTracking still has the same implementation.

Was informed about why this issue is invalid in the {D7359} revision

I've added a revision {D7346} which results in something like this:

Closing this task as it isn't relavant, as pointed out by @epriestley

Yeah. I think that this is similar to T3591: Render PlantUML syntax as macro in remarkup areas. However, since that led me to T3602: Provide some kind of "process this block with an interpreter" syntax to Remarkup which should enable me to try fixing this myself...