@wolandark Yes, that's it. I'm glad you found it! Out of curiosity: So you're trying to customize the theme/colors a bit? Do you suggest any general enhancements of the colors that should be applied for all users?

Yes I'm customizing both the light and the dark themes for myself.

So far I have a catppuccin-ish dark theme and a gruvbox-ish light theme going on.

I would suggest the ability to read a custom light.css and dark.css to be added to ezra-bible-app. That way we could make many themes for users, and you know people love themes.

It would even be better if we could have more than two themes listed in the settings from custom css files at xdg-home.

On another note, this is really bothering me:

Do you see that the top of the next line is almost poking into the ui-select-menu-status field? That makes the ui feel somewhat clunky.

adding these css rules seems to be working well for me.

.ui-selectmenu-status {
    line-height: 1.4em;
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}

Thanks for your suggestions @wolandark.

Theming ability

Regarding the theming ability with a choice for a light color theme and a dark color theme: So the assumption would be that we have the two default themes as it is and then the additional css files could be used to make modifications on top of that?

That would translate into having one custom theme <style> tag in the index.html file where the currently active css file would be switched based on the night mode setting.

I would be open to make something like that happen. In the first step without any UI selectors, just the possibility to replace CSS files. Does that make sense?

Issue with wrapping text in Bible translation selection menu

Thank you for looking into a solution right away.
Would you mind opening an issue and then raising a PR with your suggested CSS changes?

No problem, I opened an issue and a PR. Hope that helps.

we have the two default themes as it is and then

That makes sense. We could possibly have a dropdown menu that lists all *.css files under a certain path and applies one when selected. I assume it will be consistent with the bible selection workflow.

In the first step without any UI selectors

I agree. Custom UI changes can wait. Just the colors.

Ok! I just opened issue #1128 to keep track of this.