I think I'm just going to remove the "profile picture" text from the description to resolve this. The account.editable option is very old and I'd eventually like to remove it, but making the description more clear is an easier fix for now.

Thanks! I believe I broke this in D15165, a little more than a year ago.

With text-overflow: ellipsis; and no truncation:

See this document for instructions on getting Phacility support:

(Or whatever more nuanced version of things you want to do. But that's the current fate/rationale of phabricator-home.)

.phabricator-home makes the menu full-screen on mobile, so it's currently only applied to /.

ayep

From the home page, you can uninstall Home like this:

Put this workflow inside "Edit Menu"

Two possible alternatives to crumbs I can come up with, although I don't love either:

One other thought: it might be nice to provide a way to get to the dashboard from the dashboard-in-a-menu view. Currently, there's no way to "Edit This Dashboard" from Home or Projects: you have to go to Dashboards, hunt it down, and then manage things from there.

Sounds good, let us know if you come up with repro steps.

This is now available in the Phacility cluster. It appeared to work correctly on a test instance:

The spooky emoji and icons are real lackluster, barely a respectable spook in the lot: 👻 💀 ☠ 🍖

D17311 makes this stop fataling, but you're stuck with the panel for now. This should get fixed soon, but I don't want to try to sneak anything more ambitious in before the release cut.

tyvm 🙏

Was the sequence of actions like this:

I can't reproduce this: removing panels from dashboards works fine for me:

"Bizarro Gremlin" is just an alias for Quicksand

🙉

I think we currently don't really try to handle these cases:

That tip probably does not fit on screen in any of the orientations: it obviously won't fit to the north or east. If we try to put it to the south, part of it will be offscreen to the right. If we try to put it to the west, part of it will be off the top of the screen (the rectangle we use to detect the size of the tip box is slightly larger than the actual pixel size of the tip because we get weird scrollbar interactions if we use the size of the tip exactly).

My trick is:

Here's what I see:

Yeah, I don't think I fixed it. I tried this set of steps at master prior to D17308:

I'm not sure if I actually fixed @rphl's issue or not. D17308 was just aimed at the existing issue under the theory that we'll see more of it after this ships if we aren't already seeing it, but his report definitely might be a new issue.

This should now be resolved at HEAD of master, and should promote to stable later today.

Thanks! I think this is the timeline of events:

Per above, it sounds like upgrading fixed what you were seeing?

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

Does that explain what you're seeing locally?

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

Those commits are not expected to trigger an audit after D17122 / T10312. The first line of commit messages is now always parsed as a title, even if it begins "Auditors: ...", "Tests: ...", "Reviewers: ...", etc.

PHP7.1 segfaults about a dozen times a day for me, every day, with little apparent rhyme or reason to the segfaults.

We need a neologism for "bad workaround".

(A "workaround" is to not use dashboards, but we'll fix this soon.)

See T12174 -- this is an issue with the new embedded-on-Home dashboards.

Safari / OSX:

I think it would be reasonable to treat this field as remarkup (at least, internally -- probably no bulky UI) so we end up generating a mention on the task. I have similar reservations about making "fixes X" start performing magic in surprising contexts.

Oh, I missed "inline". That reproduces for me. I'll file a separate issue.

Do you have persistent chat open?

This is from a million years ago and I now think we should only respect commit messages. If "Fixes Txxx" works or ever worked in comments, I'd say we should actually undo that.

This is more than two years old and no one else seems to have hit it since then. Declining until we see a modern report.

This report is more than two years old, and we haven't seen other similar reports. If you are still affected by this bug, please file a new request following the guidelines in Contributing Bug Reports. In particular, we need specific reproduction instructions we can follow to reproduce it locally, not just screenshots.