Skip to Main Content
Feature Request FR-3046
Product Area Page Components
Status ROADMAP

20 Voters

Capture the tab change event on RDS or in the Tabs template.

josepcoves Public · Mar 23 2023

Idea Summary
Provide a framework "event" to capture tab change, when the user changes from one tab to another when using Region Display Selector (RDS) or when using the "Tabs" region template to trigger dynamic actions.

Use Case
Sometimes you need to trigger certain events when the user changes the current tab. For instance, you can dynamically enable or disable buttons. 

Many other cases could be: to clear or initialize data when changing the tab, knowing which is the current tab, etc.

Preferred Solution (Optional)
1. Provide a new framework event to capture tab changes (by clicking a certain tab).

It would require adding an identifier to the DOM for each tab (right now, APEX renders the id associated with the region but not for the tab selector, and this makes it difficult to bind an event at the tab).

2. Specify the tab region at the affected elements "Select type" to capture the event when the user switches to that region. 

This implementation would enable specific events to be triggered for each tab.

This is currently on the roadmap for a future release of Oracle APEX.

Comments

Comments

  • gabriel.diaz.arias OP 2.3 years ago

    Yes, this is quite a big problem for being able to use tabs. I would also add the possibility for setting the current tab progmatically without hacks, with a simple dynamic action.

  • fac586 OP 2.2 years ago

    I'm sure that I am not alone in being more than a little annoyed that something as basic as a tab API with dynamic action support is still missing from APEX, despite this deficiency having long been recognised within Oracle.

    From my observation of forum questions, feature requests on the old app, and personal experience, I think this would have been of far more utility to developers than a number of features that have been delivered in the intervening period.

  • vincent morneau Admin OP 2.2 years ago

    Good point @fac586 , this idea is now marked to be reviewed by the team soon.

  • rob.henderson101 OP 1.7 years ago

    Consider option to refresh tab region only on initial selection, or on every selection. There are certain use cases whereby a region report may take a considerable time to execute, but once populated it does not need to be refreshed again should the user navigate away to a different tab and then return to the original (long-running) tab on the same tab container/RDS.

  • fac586 OP 9 months ago

    Consider option to refresh tab region only on initial selection, or on every selection. There are certain use cases whereby a region report may take a considerable time to execute, but once populated it does not need to be refreshed again should the user navigate away to a different tab and then return to the original (long-running) tab on the same tab container/RDS.

    That is already covered by the Dynamic Action Event Scope attribute:

    Event Scope

    Select the scope of the event, which determines when the event is evaluated a second or successive time.

    Available options include:

    Static

    Binds the event handler to the triggering element(s) for the lifetime of the current page, but is no longer bound if a triggering element is updated via Partial Page Refresh (PPR).

    Dynamic

    Binds the event handler to the triggering element(s) for the lifetime of the current page, irrespective of any triggering elements being recreated via Partial Page Refresh (PPR).

    Once

    Binds the event handler to the triggering element(s) only once. The dynamic action is not triggered again until after the page has been fully refreshed.