fix(drawer): allow custom width/height and resolve nested dropdown positioning

[michaelmkraus]

Proposed changes

Allow custom width/height and resolve nested dropdown positioning

resolves #4660

Types of changes

• Bugfix (non-breaking change that fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improvements to existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

🔭🐙🐈 Test this branch here: https://design-system.deutschebahn.com/core-web/review/fix-drawer-customselect-dropdown-position

[changeset-bot]

🦋 Changeset detected

Latest commit: f787cb7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 10 packages

Name	Type
@db-ux/core-components	Patch
@db-ux/ngx-core-components	Patch
@db-ux/react-core-components	Patch
@db-ux/wc-core-components	Patch
@db-ux/v-core-components	Patch
@db-ux/core-foundations	Patch
@db-ux/core-stylelint	Patch
@db-ux/core-migration	Patch
@db-ux/agent-cli	Patch
@db-ux/core-eslint-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mfranzke]

the default value of min-block-size is 0 – why do we need to set it to auto instead? Are we overwriting some other declaration? Or could we remove that fallback declaration?

[michaelmkraus]

If we remove the declaration entirely, the users can't set their own minimums via --db-drawer-min-height / -width.
If we set the fallback to 0, the drawer could collapse to 0 px and hide the content. By explicitly using auto as fallback, we force the browser to respect the content size (min-content) when no specific CSS variable is provided.
So using auto is in my view the correct way to make the component more robust in flexible layouts.