Skip to main content

APEX - Tip: Fix Floating Label Issue

Oracle APEX's Universal Theme provides a modern and clean user experience through features like floating (above) labels for page items. 

These floating labels work seamlessly when users manually enter data, automatically moving the label above the field on focus or input. 

However, a common UI issue appears when page item values are set Dynamically the label and the value overlap, resulting in a broken and confusing user interface.

once the user focuses the affected item even once, the label immediately corrects itself and displays properly.

When an issue is reported, several values are populated based on a single user input, causing the UI to appear misaligned and confusing for the end user.



Here, I'll share a few tips to fix this issue.

For example, employee details are populated based on the Employee name.

In this case, the first True Action is used to set the values, and in the second True Action, paste the following code

setTimeout(function () {

  $("#P29_EMAIL,#P29_ADDRESS,#P29_PHONE,#P29_DEPT,#P29_DOB_input").each(function () { // Page item names / P29_DOB_input = date picker static ID

    if ($(this).val()) {  // Add the CSS class only if the value is set

      $(this).closest(".apex-item-wrapper").addClass("js-show-label");

    }

  });

}, 1000); // 1-second delay because Popup LOV takes time to render


Instead of calling the above code in a True Action, you can also place similar logic in a Page Load Dynamic Action


setTimeout(function () {

  $("#P29_EMAIL,#P29_ADDRESS,#P29_PHONE,#P29_DEPT,#P29_DOB").each(function () {

    $(this).closest(".apex-item-wrapper").addClass("js-show-label");

  });

}, 1000);


This code runs when the page loads and applies the CSS class without any condition



Comments

Post a Comment

Popular posts from this blog

Building a Custom Debug Package for Oracle APEX Using PL/SQL

While developing Oracle APEX applications, debugging page processes and backend PL/SQL logic can be challenging—especially when values are lost between processes or execution flow is unclear.  Although DBMS_OUTPUT is useful, it doesn’t work well inside APEX runtime. To solve this, I built a custom PL/SQL debug Package that logs execution flow and variable values into a database table.  This approach helps trace exactly where the code reached, what values were passed, and whether a block executed or not - even inside page-level processes and packaged procedures Why a Custom Debug Package? Works seamlessly inside Oracle APEX page processes Persists debug information even after session ends Helps trace execution flow Captures runtime values Can be turned ON/OFF dynamically Does not interrupt business logic The Package consists of:- Debug Table                         -  Stores debug messages Sequence ...
Post a Comment
Read more

Conditional Cell Editing in Oracle APEX IG

While browsing the Oracle APEX forum, I noticed a question from a user asking how to disable all other cells in an Interactive Grid row until the first cell has a value. In this blog, we will explore how to disable all other cells in an Interactive Grid row until the first cell contains a value. This approach helps enforce proper data flow, avoids incomplete or invalid records, and improves overall data integrity.  By implementing a simple client-side logic using JavaScript and Dynamic Actions, we can gain fine-grained control over row-level editing behavior in Oracle APEX. Step1: Create IG with static ID of EMP. Step2: Paste the following code in function global declaration. function setCellsToReadOnly()  { var grid = apex.region("EMP").widget().interactiveGrid("getViews", "grid"); if (!grid || !grid.model) { return; } var model = grid.model; model.forEach(function (record, index, id) { var meta = model.getRecordMetadata(id); var fields ...
Post a Comment
Read more