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

35 Voters

Declarative tooltips for buttons and other elements, with default value as button label.

gabriel.diaz.arias Public · Nov 19 2021

Idea Summary
It would be nice having a declarative way for adding declarative tooltips for buttons. When you have icon-only buttons is something pretty useful, as it describes crearly what the button does the first time you are using an app.

Use Case
Simplify creation of tooltips for buttons and other elements, as if it could be done declaratively without custom html, the universal theme could modify its look and feel in the future without any additional actions required. The default value of the tooltip should be the label of the button.

Preferred Solution (Optional)
Add “Tooltip” attribute for buttons at least, with default as button label.

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

Known Duplicates

Known duplicates

FR-3023
FR-3023 Declarative Tooltip for Report Column

Comments

Comments

  • bshumway OP 3.3 years ago

    This is honestly a big improvement! Almost a game changer for many user's apps. I'm not sure about the tooltip having a default value (like the button label). But it's a reasonable ask.

    So many apps suffer from buttons where the user is thinking “uh-oh, what's going to happen if I click this thing”. Since APEX is low-code… a lot of developers I know just aren't savvy enough to use HTML/JavaScript… or find a plugin online and figure it out…. so something like this would be a Huge win for them.

    I would categorize this as “low-hanging" fruit of high value for the APEX team.

    My two cents….

  • jayson hanes Admin OP 3.3 years ago

    I agree that this would be nice!

  • fac586 OP 3.3 years ago

    The elephant in the room is that basic tooltips defined using the title attribute are not universally accessible. They are not available to users accessing the app using screen readers, refreshable Braille displays, or touch screen devices. They are unlikely to be accessed by users with limited movement who are less able to go scrubbing around the screen with the mouse.

    Tooltips that simply repeat the component label are completely pointless and very annoying for users of non-visual browsers.

    The default behaviour requested is already implemented for iconic buttons:

    <button class="t-Button t-Button--noLabel t-Button--icon t-Button--pill"
    onclick="void(0);" type="button" id="B2650094224182669758" title="Rewind"
    aria-label="Rewind">
  <span class="t-Icon fa fa-backward" aria-hidden="true"></span>
</button>

    Having a separate component property would help by enabling APEX to generate ARIA-compliant tooltip mark-up, but as it says there:

    If the information is important enough for a tooltip, isn't it important enough to always be visible?

    If the UI pathway isn't intuitive then instead of hiding instructions in tooltips, the best way to improve usability and accessibility is to provide the required information through the existing help features, or by including them as permanent boilerplate content in the page flow.

  • mahage OP 2.3 years ago

    It would be very helpful if the tooltip content could be html formatted