I don't know if that is part of this task, but the global typeahead search should hide all disabled users, wikis and repos, shouldn't it? This is nothing you want as a fast suggestion...

Just as a reminder for me: Using a css variable for the height of the tags would be best. I could be overwritten at any point.

Well, my idea would be:

• Updates map

• Fixes some js linting warnings

In T15630#15618, @aklapper wrote:

For consideration of the bigger picture, I'd like to mention https://collinmbarrett.com/block-web-fonts (performance etc) and for example Firefox 118+ blocking font fingerprinting in private windows (yes, private only, but I can vaguely imagine expansion).

Broader CSS discussion: T15734

I am honestly surprised by the notion, the user base of phorge is still using old, small or low resolution screens. I always thought this project was catered towards tech-savvy devs and/or corporations and will be used in contexts where a FullHD screen is the default case. Maybe we should sharpen our target audience 😅

In T15630#15566, @aklapper wrote:

In T15630#15561, @bekay wrote:

Times have changed and we all have very big screens.

Absolutely not. Maybe in some richer countries to some extent, but not on my mobile phone. (And even if that was true, scaling exists for a reason.)

And on another note: Times have changed and we all have very big screens. I think we should increase the default font size of 13px to 14px. It is about time...

In T15630#15553, @sirocyl wrote:

Of these, I like 1 and 3 (Noto and Inter) better. How does Atkinson look? (I haven't gotten around to changing the font on my end yet, heh)

Here you can see the fonts with Phorge itself. For me the clear winner is Noto Sans. It can add some real modern style to the site.

I like the first three the most.

Maybe I should create a slowvote poll to reach a decision?

Or what about Inter? It is open source and looks very readable: https://rsms.me/inter/

I have landed my solution.

The new font family styles does look not very nice on macOS, look at the bold texts...

• Update Map

• Increase line height

Updates map

In D25521#14952, @speck wrote:

Thanks!

@aklapper @valerio.bozzolan I think the styles for remarkup should stay seperated. We shouldn't blur modular css definitions just to safe some lines or multiple declarations.

• Seperates styles

@aklapper This task created a small regression. It is really so small I don‘t think it needs a task. Maybe you can accept my revision D25522.

In T15645#15201, @speck wrote:

@bekay while in this area of code would you have any pointers on these other issues I’d like to fix at some point?

1. File browse widget doesn’t work unless logged in, for publicly accessible repos
2. The search results pop up width is often too narrow to show the full results path, and truncates the end of the path instead of beginning.

Adds return value to annotation and fixes wrong path when locating file from within a directory.

@speck @valerio.bozzolan My revision is ready to be tested 😄

• Adds map

In D25520#14909, @avivey wrote:

Thanks
also - need to run bin/celerity map before landing?

@aklapper @valerio.bozzolan See D25520.

In T15715#15174, @aklapper wrote:

I guess you could get the result that you're looking for by editing the file webroot/rsrc/css/aphront/typeahead.css and removing the line white-space: nowrap; from the definition of div.jx-typeahead-results a.jx-result. I just don't know which side effects this may have in other places...

Under the hood branches are already supported by the locate feature. The whole file tree is loaded via AJAX, when you first click in the input field. This tree represents the current selected branch.

Well, no opinions from the team. I still think this should be implemented... 😁

I still like this. Why is this not going forward? 😄

This is now resolved.

Add back code which shouldn't be removed.

Fix linting warnings.