[docs] no line breaks in sklearn estimators attributes

[jmoralez]

Description

The current build for the docs doesn't create line breaks to separate different attributes in the sklearn estimators.

Reproducible example

v.3.2.1

v.3.3.0+

[StrikerRUS]

I believe this is due to some changes in sphinx_rtd_theme

LightGBM/docs/env.yml

Line 18 in f834cab

- "sphinx_rtd_theme>=0.5"

Probably our patch is related also:

LightGBM/docs/_static/js/script.js

Lines 2 to 3 in f834cab

	/* Use wider container for the page content */
	$('.wy-nav-content').each(function() { this.style.setProperty('max-width', 'none', 'important'); });

[StrikerRUS]

Probably our patch is related also:

No line breaks after removing the patch.

[jmoralez]

I don't know much about HTML and CSS but it seems that the main difference is that in the previous version the properties had the method class:

And now there is a property class:

And that class sets display: inline-block:

which allows items to be on the same line:

Compared to display: block, the major difference is that display: inline-block does not add a line-break after the element, so the element can sit next to other elements. (source)

Removing that property solves the issue:

I'm not sure where to make that change though 🤣

[StrikerRUS]

@jmoralez Thank you very much for investigating this!

I'm not sure where to make that change though 🤣

I can prepare a PR with the fix you've found.

However, I think it worth creating upstream issue in the sphinx_rtd_theme repository describing that new inline-block style for properties makes look them ugly.

[jmoralez]

However, I think it worth creating upstream issue in the sphinx_rtd_theme repository describing that new inline-block style for properties makes look them ugly.

I believe this is the same issue.

[StrikerRUS]

I guess you're right. Thanks for finding that issue!

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.