[Bug]: Content tabs component rendering exception on narrow screen

[SuperManito]

Context

fix method

.tabbed-set {
    overflow: hidden !important;
}

Bug description

see picture

Related links

• Reporting a bug

see picture

Reproduction

see picture

Steps to reproduce

see picture

Browser

Chrome

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues and discussions.
• I assure that I have removed all customizations before submitting this bug report.
• I have attached a .zip file with a minimal reproduction using the built-in info plugin.

[squidfunk]

Thanks for reporting. The stretching of the content tabs to the entire screen is by design. Other than that I don't understand the problem. If you only give us "see picture" and no minimal reproduction, that's all we can do here.

[SuperManito]

Thanks for reporting. The stretching of the content tabs to the entire screen is by design. Other than that I don't understand the problem. If you only give us "see picture" and no minimal reproduction, that's all we can do here.

This is not normal. See here

[SuperManito]

Thanks for reporting. The stretching of the content tabs to the entire screen is by design. Other than that I don't understand the problem. If you only give us "see picture" and no minimal reproduction, that's all we can do here.

I don't understand what else you need from me. This is obviously a component style issue. Even providing a minimal copy requires using browser developer tools to reproduce. The content reproduced is also regular Markdown content.

Also, I cannot find any examples of using admonition components and tab components together on your official website. You can try it locally. Please take user feedback seriously.

[squidfunk]

It's all described here and here ☺️ You ticked all boxes in "Before submitting", so you agreed to have read it. Note that, as maintainers, we reserve the right to close incomplete issues, which this issue clearly falls under.

[SuperManito]

It's all described here and here ☺️ You ticked all boxes in "Before submitting", so you agreed to have read it. Note that, as maintainers, we reserve the right to close incomplete issues, which this issue clearly falls under.

Yes. Developers have the right not to see any open issues. I will not submit any issue for this project.

[facelessuser]

I think you were specifically being pointed at the requirement to provide a minimal reproduction. There are a lot of things that could be going wrong, the first step is to provide a minimal reproduction so they can make sure you aren't introducing 3rd party plugins that are breaking thing, using odd syntax that breaks HTML construction, etc. An image is not sufficient due to all the places things could go wrong.

[maximilienkohl]

You want something from the maintainers, then it's legitimate for them to want a reproduction from you. That way the maintainers can fix the problem faster and more efficiently

[SuperManito]

I think you were specifically being pointed at the requirement to provide a minimal reproduction. There are a lot of things that could be going wrong, the first step is to provide a minimal reproduction so they can make sure you aren't introducing 3rd party plugins that are breaking thing, using odd syntax that breaks HTML construction, etc. An image is not sufficient due to all the places things could go wrong.

I understand that developers need minimal reproducibility. I am also a developer. But the reproducibility method of this project seems very troublesome and I am tired of creating it. It is the attitude of the developer that makes me feel a little disappointed. I don't want to say more to avoid causing some damage to the community ecology of this project.

[squidfunk]

Are you stupid?! You want something from the maintainers, then it's legitimate for them to want a reproduction from you. That way the maintainers can fix the problem faster and more efficiently

@maximilienkohl I must remind you to use inclusive language and be respectful, as noted in our code of conduct. Calling somebody stupid is not better than providing no reproduction. We will not accept such behavior.

[squidfunk]

I think you were specifically being pointed at the requirement to provide a minimal reproduction. There are a lot of things that could be going wrong, the first step is to provide a minimal reproduction so they can make sure you aren't introducing 3rd party plugins that are breaking thing, using odd syntax that breaks HTML construction, etc. An image is not sufficient due to all the places things could go wrong.

I understand that developers need minimal reproducibility. I am also a developer. But the reproducibility method of this project seems very troublesome and I am tired of creating it. It is the attitude of the developer that makes me feel a little disappointed. I don't want to say more to avoid causing some damage to the community ecology of this project.

As mentioned by @facelessuser, the error could be hiding in your customizations, which is why we must make sure that the error is in our sources. This is all described extensively in our bug reporting guide, and mandating a minimal reproduction actually saves both of us time. Specifically here. I understand that it might be troublesome, but otherwise we'd be wasting a lot of time better invested in pushing the project forward. After all, it's economics.

[maximilienkohl]

Are you stupid?! You want something from the maintainers, then it's legitimate for them to want a reproduction from you. That way the maintainers can fix the problem faster and more efficiently

@maximilienkohl I must remind you to use inclusive language and be respectful, as noted in our code of conduct. Calling somebody stupid is not better than providing no reproduction. We will not accept such behavior.

Yes, of course. I noticed and edited my post. Sorry @SuperManito for calling you stupid! I wrote faster than I thought

[facelessuser]

As @squidfunk says, you do appear to be using some customizations. As an example, here I'm using complex nested tab scenario and rendering the result on a mobile layout. I am not experiencing any issues. And yes, I'm also using customizations.

[SuperManito]

I think you were specifically being pointed at the requirement to provide a minimal reproduction. There are a lot of things that could be going wrong, the first step is to provide a minimal reproduction so they can make sure you aren't introducing 3rd party plugins that are breaking thing, using odd syntax that breaks HTML construction, etc. An image is not sufficient due to all the places things could go wrong.

I understand that developers need minimal reproducibility. I am also a developer. But the reproducibility method of this project seems very troublesome and I am tired of creating it. It is the attitude of the developer that makes me feel a little disappointed. I don't want to say more to avoid causing some damage to the community ecology of this project.

As mentioned by @facelessuser, the error could be hiding in your customizations, which is why we must make sure that the error is in our sources. This is all described extensively in our bug reporting guide, and mandating a minimal reproduction actually saves both of us time. Specifically here. I understand that it might be troublesome, but otherwise we'd be wasting a lot of time better invested in pushing the project forward. After all, it's economics.

By the way, when submitting issues in other projects, developers will change the issue tag if they find that the issue author does not provide a reproduction link or does not meet the specifications. The issue will not necessarily be closed directly.