• Audit is missing the "attach, drop-voided, upgrade-to-draft-text" code that Differential has when submitting "isEditing" comments.
• Audit is missing the entire submit-editing workflow in general.

In Chrome (Version 64.0.3282.140 (Official Build) (64-bit)) the inline comment buttons have a hot-spot for tooltips to party

I reordered these elements in D21200. See also D20967.

Mooted by changes in T13513.

We've never seen other requests for this feature and currently have no customer requests for it, so I don't plan to implement it.

See T13513.

• When you load the page and there are multiple inlines which we're pushing into an edit state, we focus and select them in sequence (and the overall order is basically random). The focus + select behavior should be disabled for this edit pathway.

• When we force saves of inlines, we probably (?) save the last saved state, not the draft state.

• When you click a line, type text, get a draft, reload the page, and cancel the inline: we cancel into an empty state.

• When you click a line, type text, then go to the list view: the revision draft state has not re-synchronized based on an empty inline comment with only a draft, because saving a draft doesn't trigger a re-sync.

• In the preview, editing inline comments don't reflect draft states correctly.

• The preview section underneath the comment area doesn't mark "editing" inlines in any special way.
• The "view" links in the preview don't jump to editing comments correctly.
• The "delete" links in the preview don't put editing comments into the right state (delete is normally impossible for an editing comment).

I think that covers things here.

Thanks for the quick response! I'll give your suggestions a try, and else will continue on Discourse. Was not aware of its existence.

(This kind of question is best asked on Discourse.)

We were using the --skip-arcconfig option like this in our CI environment (jenkins).

Thanks! I didn't know it could be done from the web UI.

You can open the revision in the web UI and "Request Review". You can use arc diff --browse ... to open the web UI automatically.

We just found a real issue with this, different from what I mentioned above: We had an issue with our CI machine, and to fix it we needed to make a diff. But as the CI machine is not working, the diff won't build, which means we can't accept the diff that will solve the issue.

Is there a way to disable this option via a config in the server or a CLI parameter?

See https://discourse.phabricator-community.org/t/typeerror-w-arc-diff-when-build-plan-view-policy-does-not-contain-user/3820/. The reproduction case is "policy makes the build plan invisible".

Spotted a typo, arcainst :)

As of D21188, inlines have these remaining weird behaviors:

Just a question - are there any technical reasons why providing custom field for "projects" may not be a good idea?

In the DOM, inline comments are currently structured as a "comment row", followed by zero or more related rows (which may contain the editor UI or the undo UI).

OKAY SO

I'm having trouble reproducing figuring out how to reproduce this locally.

These issues are somewhat complicated because changesets currently have a single changeType attribute and a single fileType attribute, and a lot of rendering logic depends on these attributes. This model isn't correct in the general case.

This seems to be fixed and has deployed to the cluster.

This appears to be an issue with synthetic lint messages from Harbormaster that do not specify a line number. We reach this section of the code: