Hi,
According to the patch notes of OutSystems UI v2.15.0 the incorrect size of the tabs header indicator should be fixed. We decided to update OutSystems UI from v2.14.0 to v2.15.0.
But the indicator still has the incorrect size.
Does anyone know how to fix this?
FYI; We cannot set the monitor and webbrowser to 100% because some monitors are 4k which makes text in the browser almost the size of a grain of sand. I've seen a solution for this and I've tested it but I was not able to read on my screen.
Thanks in advance.
Regards,
Bo
Hi @Bo Menick
Yesterday, a new version was released (2.17.0) and as I mentioned before, the way this works was refactored in order to mitigate some browser specificities under the task code ROU-4231.Hope this helps solve your issue.
Cheers,GM
I was not able to reproduce this use case in Chrome, Edge and Firefox.There's a known issue that we'll try to address in the future (under task ROU-4231 for future reference on release notes) in Safari where this still happens and with the current approach, we can't since Safari doesn't have compatibility with it. For better visibility, we added that information to the release notes.Can you please confirm that this is your scenario?
This 100% still happens in Edge. I'd be glad to work with you via Slack MVP to go through details, because it's bothering me too. It has not changed at all with the recent releases that were supposed to fix the problem.
J.Ja
Hi Gonçalo,
Unfortunately that is not my scenario. I'm using an opera browser with browser zoom 100% and monitor zoom 150%.
I just tested in Edge version 114.0.1823.41 (Official Build) (64-bit) and was not able to reproduce it.Feel free to take a look at the code on our repo and suggest a possible alternative.But I'll reach out on Slack for more info.
I have the latest version from the Forge (2.15.0). I have no clue how to install OutSystems UI from your GitHub repo. Even if I did, I can't install a non-released, non-stable version from your GitHub to my DEV environment, and then have it be forced into my TST and PRD environments on my deployments, or cause chaos in my DEV environments.
I might be able to test this in a PE, but again, I have no clue how to turn that big pile of random JS and YAML files in your repo into an OML that I can install and use.
Hi @Gonçalo Martins,
Thank you for informing me about the update.
I've just tested it and it works perfectly for me. Changing the zoom values will not break the tabs indicator anymore. Luckily.
The problem is simples to solve, all elements need to have the same width. It just because the scale is calculate with the same reference for all tabs using the css properties :
You can have like a div with display flex holding all tab-itens with flex:1 set