Text rendering issue in visualizations with Chromium based browsers and Windows 10

[Sonja_Bauernfeind]

Qlik Sense charts may not render or display text on charts correctly.

This has been addressed in Qlik Cloud Qlik Sense Enterprise on Windows February 2024.

When using Qlik Sense with Chromium-based browsers (such as Google Chrome or Microsoft Edge) and Windows 10, text in labels and values in visualizations are sometimes not rendered correctly.

Resolution

The behavior was improved. Upgrade to Qlik Sense Enterprise on Windows February 2024. 

Workaround

Google Chrome

1. Type chrome://flags in the Google Chrome URL bar
2. Find Accelerated 2D canvas
3. Change it to Disabled

Microsoft Edge

1. Type edge://settings/system in the Microsoft Edge URL bar
2. Turn off Use hardware acceleration when available

Environment

Qlik Cloud 
Qlik Sense Enterprise on Windows 

Internal Investigation ID(s) 

IM-4962
QB-18418

[Calavera]

Hi!

Can you please tell us what is causing this issue once you've discovered the root cause? Thanks.

[Sonja_Bauernfeind]

Hello @Calavera 

The hardware acceleration setting is the root cause of this behaviour. See the resolution provided.

All the best,
Sonja 

[Calavera]

Hi@Sonja_Bauernfeind ,

Thanks. Why was Qlik working before even with the hardware acceleration enabled? What has changed?

[Sonja_Bauernfeind]

Hello @Calavera 

From what I understand, changes were done to Chromium-based browsers, which are affecting Qlik in this particular case. I am getting verification from our developers, but I believe this assertion is correct.

All the best,
Sonja 

[Sonja_Bauernfeind]

Hello @Calavera 

I wanted to update you to confirm that this is identified as an issue with changes done in Chrome (affecting the rendering engine) and Windows 10. Upgrading Windows, turning off the hardware acceleration, and potentially upgrading your graphics drivers are possible workarounds.

All the best,
Sonja 

[eyalnir_qlik]

Hi @Sonja_Bauernfeind 

is there any plan in the short or long term to fix QB-18418 as permanent solution ?

Many thanks for your answer

Eyal 

[Sonja_Bauernfeind]

Hello @eyalnir_qlik This is caused by the rendering engine in the browsers, rather than Qlik itself. If you need this reassessed, please log an idea in our ideation section.

All the best,
Sonja 

[p_verkooijen]

Hi @Sonja_Bauernfeind 

70% of users are on Windows 10 (Windows vs other OS = 70%)

https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide

65% of desktop users uses chromium browsers

https://gs.statcounter.com/browser-market-share/desktop/worldwide

Not sure what the combined total share of Windows 10 and Chromium would be, but I guess it's quite the group who (potentially) have issues with rendering Qlik objects.

Of course we understand that there was a change in the browser, and it is not Qlik that broke the rendering. However every web developer will get these issues from time to time and have to create a fix in their solution.
Not quite a issue that would be fixed through an idea, waiting for users to find the post and after this waiting to someone determining when and if it gets fixed.

Seen ideas with a lot of likes that just not seem to get into the product, there is no clear threshold. 

[eyalnir_qlik]

Hi @p_verkooijen 

totally agree with you!  Idea's can stay for months even years with no delivery. although they got some votes and likes.

In this case as mention, the workaround works for all our customers, upon some customers (OEM agreements),recently, open cases refer to this workaround which isn't feasible for them.

means, that they need to ask 3rd party customer's IT to set this Flag in chrome browsers and they want to avoid it. 

As they see it, this issue affect only Qlik visualization and other products works as expected.

@Albert_Candelario 

@Sonja_Bauernfeind 

[Sonja_Bauernfeind]

Hello @eyalnir_qlik and @p_verkooijen I'm looking into this internally for you.

All the best,
Sonja