Community
Participate
Working Groups
In 3.3, view tab titles that are too wide get just cut, so that the user does not see that a view is e.g. not really called "Project" but "Project Explorer". I agree that the ellipsis was using up too much real estate. A solution that keeps using the full width but still makes it clear that a tab is cut would be to render the last character(s) with a gradient going from left to right from the original title text color towards the background color.
We played around with treatments like this but never hit on anything that looked particularly good. They all looked like a graphic bug. A solution may still exist but it'll require a convincing mockup from someone. Agree that some rendering/indication would still be valuable.
Created attachment 76437 [details] A quick hack Just made for creating screenshots. Not optimized in any way. Only works for selected tab.
Created attachment 76438 [details] Screenshots (mockup)
Thanks for the prototype code and screen cap Markus. It somewhat matches what we did before, although I think you did a slightly nicer rendering. But still I wonder if people will interpret it correctly or just think its a smugde/graphics error?
This looks really nice! I'm not too concerned about it looking like a graphics error because the width of the tab shows that it has to truncate the text in some way. And it is much smoother than clipping it.
Created attachment 76549 [details] Mockup 2 Here's how it could look like with stacked views (upper part) an how it looks today (lower part). I quite like it, and I think you wouldn't notice the fading without looking specially at a single tab. But when you look at a tab closely, then you see that there's something special about the last characters -- and the IMHO obvious interpretation is that there's something missing and that the tooltip will tell the whole thruth. Implementation note: performance offenses aside, there's also a layouting problem at the spot where the black text ends and the fading starts. In Mockup 2, you can e.g. see, that a pixel is missing between "Ja" and "vado". I guess some string width measurements are not 100% reliable here (could even be a kerning issue). Furthermore, the final solution would need to make sure that the first character is always black.
Removing 3.5 target milestone. We are in the end-game now. Please have a look and decide if this should be targeted at 3.6.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
