When an fatal exception is triggered :

Because there are more and more referenced issues and, because some of them may need further discussion in order to find the best solution, IMHO it may be a good idea to create a sub task for each issue reported isn't it ?

Another on when displaying a maniphest with a lot of comments :

Concerning the dashbord's big pannel :

In workboard, when a maniphest's is drag and dropped, available triggers information windows is broken.

In workboard, when maniphest's edit button style is broken on mouse over.

I'll do it next time, I always do my best to serve my master !

Yeah bob, feel free to add your nice screenshots in the Task description for more visibility. You are a good minion!

In workboard, empty column's drop zone is a little bit 'agressive' isn't it ?

Hi, I can also see this one that looks weird in big pannels available on dashboards

Also, I apologize for not completing this, hadn't had much spare time until recently. I will work on this soon.

Done.

Hi @Bukkit can you please publish F281219? thanks :)

clicking such a link w/javascript disabled will do nothing. Changing it to #123 and no JS will do something....

Implicitly, Phorge generally works fine for browsers where Javascript is completely disabled.

4. Why these nice URLs are set in these links, if nobody visit them?

Less priority of course, since this Task I authored is super-stupid

OK I've done my best :D I admit it helped me psychologically.

If this is a feature request, then add all the things needed for a feature request - as in, "why would this feature be needed" and "what problem you're trying to solve".

Is this a bug or a feature request?

Why would it need to be a that?
Is this a bug or a feature request?

OK this was easy, but it really cannot be improved more than this in Legalpad or Phame. And this deserves a dedicated fix.

I'm 99% sure that this only affects Phame and Legalpad. I tested in Audit, Maniphest, Paste, Pholio and Files without issues.

This situation could be improved even more doing:

Increasing priority to normal since this feature is supposed to help to collaborate with others, but at the moment you only collaborate with yourself as default

I'm mentioning this small thing in the Changelog since some people may have legacy Dashboards with a Panel that was Archived just to try. So there is less surprise on your Phorge homepage.

I'm quite sure we have to set PhabricatorApplicationTransaction.php::setIgnoreOnNoEffect(bool) somewhere but I don't know where ihih

So I'm following proposal n. 2 in D25363.

I've explored a bit the codebase and this seems a desired non-feature.

I don't see file F281219

I think we have an implementation:

Any comment about the first proposal would be awesome. Probably it's not so difficult

The relevant part seems to be

This is partially related to Comments

In T15448#9857, @avivey wrote:

In any case, it should be generic - on "search results page", although probably requires each SearchEngine to define the available fields in order to actually support this feature.

Unsure if tagging as Bug Reports

See https://we.phorge.it/T15533#11839 - the env-selecting code in ExecFuture has this logic: