Skip to Main Content
Feature Request FR-1601
Product Area Application Builder
Status DELIVERED

98 Voters

Align buttons and text items by default.

phil_xxx Public
· Jan 22 2021

in Apex 20.2 improve no code:

I create a text item in a region. I create a button next to it. In this example a search bar having search text and the search button.

By default the button floats higher than the text item. To resolve this I will have to write css to change the height of the button.

This has been delivered in Oracle APEX 22.2!

Comments

Comments

  • shakeeb.rahman Admin OP 3.9 years ago

    Thanks for this feedback, Phil! This is a great idea and something that we discussed a few times within the Development team.  I've marked this item as being in the backlog for a future release of APEX as this is certainly something we wish to address.

  • paulo künzel OP 3.9 years ago

    Usually I put some top margin, but it would be great if it was align by default

  • fac586 OP 3.2 years ago

    Please ensure that when this change is introduced that it is cognizant of the existing workarounds discussed in the links above using the t-Form-inputContainer column class or button spacing template options, e.g. offering Upgrade Utility options to remove or modify them as required.

  • vincent morneau Admin OP 2.3 years ago

    Hi @phil_xxx ,

    Just catching up to this. This was delivered in APEX 22.2 with the new Item Container region template.

    There's a number of alignment options on the region template options, but the default should work as you expected.

  • philwinfield OP 2.3 years ago

    Yes I've seen that. Many thanks 👍

  • andreas wismann / when others OP 9 months ago

    Please let us know where the documentation of the new “Item Container” feature can be found.
    I'd expect it here:
    Components - Universal Theme (oracle.com)
    Or in the “App Builder User's Guide”. No results.

  • andreas wismann / when others OP 9 months ago

    Having no documentation, it's pure Trial&Error (I've spent two hours without success) on how to use more than one Item/Button-pair in a single Item Container, or otherwise align item labels vertically (there seems to be no “Label Column Span” attribute in an Item Container Region) when using multiple Item Containers for that purpose.

  • fac586 OP 9 months ago

    Having no documentation, it's pure Trial&Error (I've spent two hours without success) on how to use more than one Item/Button-pair in a single Item Container, or otherwise align item labels vertically (there seems to be no “Label Column Span” attribute in an Item Container Region) when using multiple Item Containers for that purpose.

    Indeed. What was delivered in APEX 22.2 can in no way be considered a solution to real world form layout scenarios.

  • fac586 OP 8 months ago

    Please let us know where the documentation of the new “Item Container” feature can be found.
    I'd expect it here:
    Components - Universal Theme (oracle.com)

    It was included in the UT 22.2 Reference (without including any additional information) but has since disappeared. 

    Having no documentation, it's pure Trial&Error (I've spent two hours without success) on how to use more than one Item/Button-pair in a single Item Container, or otherwise align item labels vertically (there seems to be no “Label Column Span” attribute in an Item Container Region) when using multiple Item Containers for that purpose.

    I've been engaged in similar futile activity, and reached the conclusion that it's only intended to be used with one item.

    Looking back at the timing of the comments above, I now suspect that the Item Container region was created purely as a solution to the specific use case mentioned in the OP:

    I create a text item in a region. I create a button next to it. In this example a search bar having search text and the search button.

    There would be enough time to develop that in the 1-2 months before the posting of the follow-up links to forum threads about the general problem of sizing and aligning form items and buttons. It would then make sense that it doesn't address those concerns at all, and they still need to be raised in a separate request.

  • phillip.grimshaw OP 2 months ago

    awesome its gonna be in 22.2