Skip to content

Comments

chore: update package dependencies#666

Open
garethbowen wants to merge 3 commits intomainfrom
update-dependencies-2026-02
Open

chore: update package dependencies#666
garethbowen wants to merge 3 commits intomainfrom
update-dependencies-2026-02

Conversation

@garethbowen
Copy link
Collaborator

Updating primevue changes the behaviour of: #467

It's now a completely different bug but I think it's slightly better - let me know if you disagree!

I have verified this PR works in these browsers (latest versions):

  • Chrome
  • Firefox
  • Safari (macOS)
  • Safari (iOS)
  • Chrome for Android
  • Not applicable

What else has been done to verify that this works as intended?

Why is this the best possible solution? Were any other approaches considered?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Do we need any specific form for testing your changes? If so, please attach one.

What's changed

@changeset-bot
Copy link

changeset-bot bot commented Feb 20, 2026

⚠️ No Changeset found

Latest commit: 29f42df

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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


<style scoped lang="scss">
.table-layout {
width: max-content;
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

With this specified the "List group" section in the "All question types" form was forced too wide to fit within the form. I couldn't see any regression from removing it so I assume it's simply no longer required...

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.

1 participant