✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

_{Generated for commit: 0b1080f. Link to the linter CI: here}

Thank you for your pull request @glemaitre ! 😁

It seems that "single components" names need to be centred when drop-downs are opened:

It is weird. The icon looks off but locally, I have the following alignment:

Oh I see that you meant the label is not centered. I did not understood at first.

I did solve this issue and add a couple of improvement regarding the color as well.

It looks something like this now:

The parameter names (C and kernel) are now right aligned, was this on purpose?

I think that we already have the bug currently in notebooks only. I made the change here in another PR. But I'll bring the change in this PR then.

I might not have completely understood the goal. If it is just to vertically align the ?/! icons in the middle, then changing align-items: start to align-items: center in label.sk-toggleable__label is what you need. I'm not sure where those margins and paddings came from, but IMO flex layout is commonly more robust for alignment purposes.

If you want all of them (arrow, title, ?/! icons) to be horizontally centered as well, justify-content: center does the job (as what this PR currently does).

I may also suggest against using position: absolute for the leading arrow. As mentioned above, if we don't need it to be left-aligned, then absolute positioning is just not needed. I'm not 100% sure but a potential problem of absolute positioning is that it could potentially overlap with the title if we are not careful enough leaving sufficient space for it.

These are just suggestions anyways. As long as rendering looks good, I think the css implementation does not matter too much at our scale. And I could be missing something because I only tested with very simple estimators.

The solution align-items: center apparently will work for the simple model but not for the metaestimator because they are not flex container. So actually, the part which is annoying is the display: inline-block for the meta-estimator. If I use inline-flex than I get the proper behaviour than what I tried with the no-wrap. So indeed it seems to be a better solution.

I should read the CSS book one day :)

OK so I simplify as suggested and I triggered a documentation build.