Skip to content

Conversation

@mano-odoo
Copy link
Contributor

@mano-odoo mano-odoo commented Jun 9, 2023

Issue 1:

The toctrees in the documentation are visually inconsistent because of
the content. Sometimes we have titles that are also links and visually
collide with the rest of the toc making it hard to read. This applies
to toctree-l1 and toctree-l2.

Fix 1:

When we have a link and title toctree-l1 or toctree-l2 in a list
containing other nested toc, we apply another styling displaying it
with the same color as a title, but with an icon and hover behavior
indicating that it is a link. (This commit also changes the direction of
the i-link icon to make it standard).

Issue 2:

When we only have toctree-l1 links without nested toc the toctree
is uselessly taking up a lot of space.

Fix: 2

In this scenario we replace the toctree-l1 class with toctree-l2 to
make them appear as a discreet list.

task-3138525
task-3138563

part of

task-3059178

@mano-odoo mano-odoo changed the base branch from 16.0 to 14.0 June 9, 2023 07:47
@robodoo
Copy link
Collaborator

robodoo commented Jun 9, 2023

@mano-odoo mano-odoo force-pushed the 14-toctree-fallback-l1-l2-mano branch 2 times, most recently from 24bf9e3 to ab9efb4 Compare June 9, 2023 14:40
@mano-odoo mano-odoo changed the title 14 toctree fallback l1 l2 mano [IMP] odoo_theme: toctrees-l1,l2 design improvement Jun 9, 2023
@mano-odoo mano-odoo requested a review from AntoineVDV June 9, 2023 15:01
@AntoineVDV AntoineVDV marked this pull request as ready for review June 9, 2023 15:18
@C3POdoo C3POdoo requested review from a team June 9, 2023 15:33
@mano-odoo mano-odoo force-pushed the 14-toctree-fallback-l1-l2-mano branch from ab9efb4 to de60c37 Compare June 15, 2023 15:44
@mano-odoo mano-odoo requested a review from edi-odoo June 26, 2023 13:44
Copy link
Contributor

@edi-odoo edi-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! @AntoineVDV could you check the JS please ?

Issue 1:
========
The toctrees in the documentation are visually inconsistent because of
the content. Sometimes we have titles that are also links and visually
collides with the rest of the toc making it hard to read. This applies
to toctree-l1 and toctree-l2.

Fix 1:
========
When we have a link and title toctree-l2 in a list containing other
nested toc, we apply another styling displaying it with the same color
as a title, but with an icon and hover behavior indicating that it is a
link. (This commit also changes the direction of the i-link icon to make
it standard).

Issue 2:
========
When we have only have toctree-l1 links without nested toc the toctree
is uselessly taking a lot of space.

Fix: 2
========

In these scenario we add a class to the toctree wrapper to replace the
toctree-l1 style with a toctree-l2.

task-3138525
task-3138563

part of

task-3059178
@AntoineVDV AntoineVDV force-pushed the 14-toctree-fallback-l1-l2-mano branch from de60c37 to 6da7828 Compare November 17, 2023 15:12
Copy link
Collaborator

@AntoineVDV AntoineVDV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, sorry for the delay! I had to put this aside while there was urgent stuff to deal with. When I had a quick look some time ago I spotted visual glitches, but after a rebase it seems to be fixed, so all good for me :)

@robodoo r+

robodoo pushed a commit that referenced this pull request Nov 17, 2023
Issue 1:
========
The toctrees in the documentation are visually inconsistent because of
the content. Sometimes we have titles that are also links and visually
collides with the rest of the toc making it hard to read. This applies
to toctree-l1 and toctree-l2.

Fix 1:
========
When we have a link and title toctree-l2 in a list containing other
nested toc, we apply another styling displaying it with the same color
as a title, but with an icon and hover behavior indicating that it is a
link. (This commit also changes the direction of the i-link icon to make
it standard).

Issue 2:
========
When we have only have toctree-l1 links without nested toc the toctree
is uselessly taking a lot of space.

Fix: 2
========

In these scenario we add a class to the toctree wrapper to replace the
toctree-l1 style with a toctree-l2.

task-3138525
task-3138563

part of

task-3059178

closes #4674

Signed-off-by: Antoine Vandevenne (anv) <[email protected]>
@robodoo
Copy link
Collaborator

robodoo commented Nov 17, 2023

@mano-odoo @AntoineVDV staging failed: ci/runbot on 7b206bdc5cb3268957926341ef3c095b574acf68 (view more at https://runbot.odoo.com/runbot/build/53851693)

@AntoineVDV
Copy link
Collaborator

@robodoo retry

robodoo pushed a commit that referenced this pull request Nov 17, 2023
Issue 1:
========
The toctrees in the documentation are visually inconsistent because of
the content. Sometimes we have titles that are also links and visually
collides with the rest of the toc making it hard to read. This applies
to toctree-l1 and toctree-l2.

Fix 1:
========
When we have a link and title toctree-l2 in a list containing other
nested toc, we apply another styling displaying it with the same color
as a title, but with an icon and hover behavior indicating that it is a
link. (This commit also changes the direction of the i-link icon to make
it standard).

Issue 2:
========
When we have only have toctree-l1 links without nested toc the toctree
is uselessly taking a lot of space.

Fix: 2
========

In these scenario we add a class to the toctree wrapper to replace the
toctree-l1 style with a toctree-l2.

task-3138525
task-3138563

part of

task-3059178

closes #4674

Signed-off-by: Antoine Vandevenne (anv) <[email protected]>
@robodoo robodoo closed this Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants