This task was filed via the "New Bug Report" form.
Wed, Apr 4
Since there's no known actual problem with this today, I don't plan to fix it.
I don't currently plan to change the remaining edge case behaviors since I'm not sure they ever occur in the wild.
Tue, Apr 3
Duplicate of T8936?
Fri, Mar 30
I confirm the Maxime Corteel patch to be working with PHPUnit 7.0.1 too.
Thu, Mar 29
I think this is sort of less bad/weird now, at least. You get a tokenizer instead, which is still empty, but you're prompted to "Type a repository name..." and the UI isn't this odd empty select thing anymore.
Mar 21 2018
Mar 16 2018
is there a chance that this problem will get fixed?
The change D17989 is already from May 2017 without any reviewer...
Mar 14 2018
Mar 7 2018
I believe the behavior of this UI should generally align well with what reasonable users might expect, now. In particular, /src/backend and /src/backend/ are now exactly the same in terms of actually resolving ownership, although the UI will continue to show you the value you entered (to avoid confusion where someone types /docs/README.md and the UI echoes back /docs/README.md/ and they have a reasonable concern that the path wasn't understood).
Probably better is to add pathIndex
Mar 5 2018
Feb 26 2018
See T13092; tangentially, it might be nice to render these stories more explicitly as "X added Y, removed Z (because Z is a subproject of Y, and objects may not be tagged with multiple mutual ancestors/descendant projects)", if some sufficiently terse phrasing can be found.
Feb 21 2018
Feb 16 2018
D19111 doesn't fix this in the general case, but should produce the desired behavior for most inputs such that the input is in the form [x](y) and y is the URI of a Wikipedia article.
The intent isn't unambiguous in the general case, consider: Blah blah (see also [x](y)).
The non-bold ones also open in a new tab.
Oh! Yes. Sort of.
Just curious, but is the bold effect intentional in the "No Encoding Relative" scenario?
Feb 14 2018
Feb 13 2018
After changes T13073, I am no longer able to reproduce this. That task has made some improvements and may have fixed whatever happened here.