If I create a Webform 'select' component and choose to allow the 'Other..." option (select_or_other module) and choose to display 'Description above field" then the description actually appears before the title and gets confused with the previous component.

It seems to be because the 'select_or_other' takes over the #title field and leaves the outer element without a #title. So Webform's `theme_form_element` has to output the description first, then allow the 'select_or_other' component, with its #title to be drawn afterwards.

CommentFileSizeAuthor
#3 Test Drupal standard.png23.38 KBj_s

Comments

ellesborough created an issue. See original summary.

danchadwick’s picture

danchadwick commented
Status: Active » Closed (duplicate)

Update to latest.

j_s’s picture

j_s commented
StatusFileSize
new Test Drupal standard.png23.38 KB

Hello, I still get this issue on the latest webform version 7.x-4.18 with select or other version 7.x-2.24.

I tested with simplytest.me (as seen in the attached screenshot).

szt’s picture

szt commented
Version: 7.x-4.12 » 7.x-4.19-rc1
Status: Closed (duplicate) » Active

I still get this issue on the latest RC.
(I don't see any duplicate issuu)
select_or_other: 7.x-2.24

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Version: 7.x-4.19-rc1 » 7.x-4.x-dev
bramvandenbulcke’s picture

bramvandenbulcke commented

I see the same behaviour with Webform 4.23 and Select or Other 2.24.

We disabled the checkbox 'Description above field': then the description is positioned under the label and checkboxes.

nicxvan’s picture

nicxvan commented
Version: 7.x-4.x-dev » 6.2.x-dev

This is still an issue on the latest version.

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Version: 6.2.x-dev » 7.x-4.x-dev

Drupal 7 and Drupal 8+ are totally different code bases. Please open a new issue instead of moving issues between them.

nicxvan’s picture

nicxvan commented

I mean there is no patch or fork here, is there no reason to just create the issue fork here?

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented

If the bug exists in both places, both will need to be fixed and the fixes will not be the same.

nicxvan’s picture

nicxvan commented

You can have separate forks for each branch on the same issue too though, that's how core usually does it.

I can create a new issue if you really want me to, but I don't want to split effort if it's not necessary.

danchadwick’s picture

danchadwick commented

@nicxvan: Do as the project maintainer asks.

nicxvan’s picture

nicxvan commented

Ah of course, I didn't realize Liam was a maintainer. I'll create a new issue, sorry for the back and forth.

nicxvan’s picture

nicxvan commented

Here is the new issue: https://www.drupal.org/project/webform/issues/3470566

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Status: Active » Closed (outdated)

Drupal 7 is no longer supported. If this applies to a supported version, please re-open.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.