Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

urls within commits get cut off and cannot get opened by the browser #9185

Closed
staabm opened this issue Feb 27, 2020 · 3 comments · Fixed by #9931
Closed

urls within commits get cut off and cannot get opened by the browser #9185

staabm opened this issue Feb 27, 2020 · 3 comments · Fixed by #9931
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature

Comments

@staabm
Copy link

staabm commented Feb 27, 2020

Describe the bug

lookup a commits within the history of a project which contains a url.
the url - when displayed cut off - because of its length does not open properly in the browser

Version & OS

Windows10x64
GHD Version 2.3.1

Steps to reproduce the behavior

  1. clone https://github.com/phpstan/phpstan-src
  2. open the history
  3. select the commit 7d2ecf9a1f911f4bc3d64373119097e927084221
  4. click the url contained in the commit

image

Expected behavior

the url opens in the browser

Actual behavior

the browser does not open the actual url from the commit https://github.com/phpstan/phpstan/issues/3008 but it seem to open the cut-off version of it https://github.com/phpstan/phpstan/i%E2%80%A6 -> which leads to a 404 http error page on github.com

opening the same url from within github.com works like expected, see phpstan/phpstan-src@7d2ecf9

@steveward steveward added bug Confirmed bugs or reports that are very likely to be bugs priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature labels Feb 27, 2020
@steveward
Copy link
Member

Thanks for the detailed report @staabm! I'm going to label this as a bug.

@halitogunc
Copy link
Contributor

Mind if I fix that one ? I have one solution in my mind without breaking truncated summary. The thing is if I choose that way, I have to add an extra optional prop to <RichText /> component, and also a new parameter for scanForHyperlink function. What do you think ?

@steveward
Copy link
Member

@halitogunc that'd be great. Pinging @desktop/engineering for thoughts on your question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@staabm @steveward @halitogunc and others