Things that are obviously bugs
Details
Yesterday
Can't reproduce either - 🤷🏻♂️
Thu, Apr 25
@avivey hi!
I cant reproduce it. Is the problem still there?
Thu, Apr 18
Yeah, that might help (like specifically in the case of the Clone dialog) even though it wouldn't help with dialogs containing writable inputs. (E.g. on the repository page, click Flag For Later instead and press Shift+Tab and Escape.) A better fix would lie at https://we.phorge.it/source/phorge/browse/master/webroot/rsrc/externals/javelin/lib/Workflow.js$413 where either the getSpecialKey would need improvement itself to return true for these non-modifying keys, or it would need to be amended with a custom check in that regard. However, I don't know where that function comes from.
Probably something here should be expanded to check if the form contains at least a visible input without read-only
Mon, Apr 15
done...
Yeah, probably. I'll try to do it tonight.
Sun, Apr 14
Can this (I mean rPb445e1d80df9 )be backported into stable?
Tue, Apr 2
I can reproduce this, on an hosted Subversion repository.
Thu, Mar 28
Mar 26 2024
It might not happen on any other card, because we might not be rendering Remarkup on any other card. Interesting....
So this is quite an edge-case:
- PhabricatorMentionRemarkupRule wants to give the mention a different color, depending on if the user can view the "context object", in this case the Project.
- There's an automatic rule, saying a member of a project can always view the project
- When loading the project for the hovercard, we don't bother loading all the member list
- When loading the user for the mention, we don't bother loading all its projects
- so data is not available at the rendering point.
Mar 25 2024
DisableUsernameEditEventListener.php is the root cause.
Premising that we may want to rollback 328aee033fbd, probably this line is broken:
Ouch. Probably partially my fault. Feel free to escalate this as Task under Bug Reports - close this as obsolete then
I can't immediately reproduce with that version either. I'll try again later.
In the meanwhile:
- Try clearing your browser's cache
- Try updating Phorge to the latest commit
- Try disabling this extension: assets/DisableUsernameEditEventListener.php
I can reproduce this on master with basically any string search.
https://we.phorge.it just works fine. :L
- Phorge installation
I can't reproduce this.
Which version of phorge/arc do you have (git log -1)?
How did you install the new Instance?
Interesting. This cannot be reproduced here in this website https://we.phorge.it? isn't it? I think no
:p
(Please edit file Visibility to make them Public :D It's another bug ihih - thanks! <3)
The exception throw out when I search text in search bar:
Please also include your exact search. I think you are searching by https://foo and that is unfortunately not possible without "doing this"