fix(Dropdown): disable the trigger element if the dropdown have disable="true"

[Cata1989]

The purpose of this PR is to address the issue related to the disabled state management in the dropdown component. Previously, the disabled state of the dropdown was not properly synchronized with the associated button's disabled state. This PR fixes that issue by implementing a mechanism to correctly update the button's disabled state based on the dropdown's disabled property. As a result, the dropdown component now ensures consistent behavior when managing its disabled state, enhancing overall accessibility and user experience.

Before	After

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 9b99c79. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 7 targets

• nx affected -t e2e --exclude=*,!tag:core --output-style=stream-without-prefixes --base=02926ca1121ff891972844bb5dd5a194b4a4ba98 --head=9b99c7954bc91af370898412725bed67f9e1004a -- --ci --code-coverage --runInBand
• nx run beeq:storybook-build --output-style=stream-without-prefixes
• nx run-many -t build -p tag:wrapper --output-style=stream-without-prefixes
• nx run beeq:build --output-style=stream-without-prefixes
• nx affected -t test --exclude=*,!tag:publishable --output-style=stream-without-prefixes --base=02926ca1121ff891972844bb5dd5a194b4a4ba98 --head=9b99c7954bc91af370898412725bed67f9e1004a -- --ci --code-coverage --runInBand
• nx affected -t lint --exclude=*,!tag:publishable --output-style=stream-without-prefixes --base=02926ca1121ff891972844bb5dd5a194b4a4ba98 --head=9b99c7954bc91af370898412725bed67f9e1004a -- --ci --code-coverage --runInBand
• nx run beeq-tailwindcss:build --base=02926ca1121ff891972844bb5dd5a194b4a4ba98 --head=9b99c7954bc91af370898412725bed67f9e1004a --output-style=stream-without-prefixes

---

Sent with 💌 from NxCloud.

[endv-bogdanb]

Not sure if this the right approach. I could use something else to trigger the dropdown. If we want this behaviour I would suggest to query by trigger slot and set disabled it's children.

[dgonzalezr]

Not sure if this is the right approach. I could use something else to trigger the dropdown. If we want this behavior I would suggest querying by trigger slot and setting disabled it's children.

We have discussed it, and your concern is right, but in this case, we would like only to cover the use case when the trigger is a bq-button. We could still set the disable attribute to whatever the trigger element is, I don't see any major issue if the attribute is set to an element that doesn't support disable as an attribute.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud