refactor: rewrite config helpers to ts

[dangreen]

No description provided.

[etimberg]

@dangreen looks like some conflicts to resolve before this can be merged

[stockiNail]

@etimberg @dangreen apologize if I'm jumping in this thread but probably it would be better to evaluate pending PRs on the touched files before translating in TS. See PR #11105.

[etimberg]

@stockiNail I can go either way depending on when this gets rebased. I don't want this PR to have get rebased many times since that's a lot of work

[LeeLenaleee]

Could you rebase master into this so the CI works again?

[LeeLenaleee]

Test seem to be failing

[dangreen]

@LeeLenaleee I've got randomly failing tests that are passing successfully locally.

[stockiNail]

@LeeLenaleee I've got randomly failing tests that are passing successfully locally.

@LeeLenaleee @dangreen I think the issue is related to FF 110. I have the same issue in chartjs-plugin-annotation. See chartjs/chartjs-plugin-annotation#856 (comment)

If you see the history of the CI, you can see that the last one which ended correctly (testing the cases) was using FF 109. Starting using 110, the fixture test cases are failing randomly. And as @dangreen reported, locally it works correctly.

[stockiNail]

FYI, I had a look to new feature of FF 110: https://www.mozilla.org/en-US/firefox/110.0/releasenotes/
I see the following feature which could affect us: GPU-accelerated Canvas2D is enabled by default on macOS and Linux.

Therefore in the test PR in annotation plugin, I have tried to disable it (not sure if the property is the correct one, :() with the following Karma config:

    customLaunchers: {
      chrome: {
        base: 'Chrome',
        flags: [
          '--disable-accelerated-2d-canvas',
          '--disable-background-timer-throttling',
          '--disable-backgrounding-occluded-windows',
          '--disable-renderer-backgrounding'
        ]
      },
      firefox: {
        base: 'Firefox',
        prefs: {
          'layers.acceleration.disabled': true,
          'gfx.canvas.accelerated': false   // <--- added this one!!! --->
        }
      }
    },

and CI in the plugin ended correctly.

EDIT: I have submitted a PR chartjs/chartjs-plugin-annotation#857 in chartjs-plugin-annotation using the above configuration. Before applying here, I would wait for the results in the plugin. Anyway, I hope that 'gfx.canvas.accelerated' is the right property to disable (I haven't seen anyone else close to the feature meaning).

EDIT 2: merged in the master of plugin and sounds working. Just 1 side effect that I have seen: sometimes the test could fail due to the timeout. Re-running it, usually ends correctly.

[stockiNail]

Submitted PR to fix FF 110 acceleration: #11165