_______               __                   _______
       |   |   |.---.-..----.|  |--..-----..----. |    |  |.-----..--.--.--..-----.
       |       ||  _  ||  __||    < |  -__||   _| |       ||  -__||  |  |  ||__ --|
       |___|___||___._||____||__|__||_____||__|   |__|____||_____||________||_____|
                                                             on Gopher (inofficial)
   URI Visit Hacker News on the Web
       
       
       COMMENT PAGE FOR:
   URI   What Is Popover=Hint?
       
       
        pentium166 wrote 18 min ago:
        I've been trying to use HTML's native popover and dialog recently. The
        promise of not having to write/import focus traps, better integration
        with standard platform "cancel" UX, the top layer concept, etc made
        them sound great, but in reality it's been kind of painful.
        
        Stacking order when you have multiple modal dialogs and popovers in the
        top layer is based on most recently revealed element, so that toast
        that just opened is now hidden under a dialog. Anchoring is currently
        only supported in Chrome, so popover tooltips show up in the corner.
        Firefox supports transition animations when opening a dialog but not
        closing it. The web platform feature needed to tie the mobile back
        button to closing a dialog isn't actually implemented yet. Frameworks
        that patch the DOM might clobber modal dialog state because it's a
        function of both the "open" attribute and the result of showModal().
        
        Some of these will improve but I think the display order problem is
        here for the long haul.
       
        mirkodrummer wrote 57 min ago:
        I have whys not whats. Why we waited so much(years!) for such api as a
        browser built in? Why I feel it overwhelming/not well thought off for
        such simple use case? I still feel like including a 3rd party library
        and instantiating a tooltip to be more straight forward, if anything
        these libraries are built upon years of know how and we don't need to
        wait for a browser vendor to add a new attribute on his own for a
        marginal improvement. Marginal improvement one would understand
        immediately right? No "hint" is a not a simple tooltip. And why the
        heck we would ever need a table grid to explain a feature that should
        be simple? I'm so sick of the web platform and its inefficiencies
       
        vintagedave wrote 3 hours 10 min ago:
        This is confusing. In the screen recording, I see two popovers, _both_
        of which appear when clicking.
        
        Yet I would view a hint as one that appears simply on hover: a tooltip.
        
        The article jumps ahead "But wait, didn’t clicking on the hint
        popover close the auto one? ... Because you’re inducing an action
        (click), it activates the light-dismiss of the auto popover. This is
        almost certainly not what you want when you’re creating a hint
        popover." but completely omits what a hint is supposed to be in the
        first place and whether this actually is a hint. As far as I can tell,
        this hint type of popover is not actually behaving like a desktop-style
        tooltip hint.
       
          cwillu wrote 2 hours 52 min ago:
          Scroll down to the last example:
          
   URI    [1]: https://una.im/popover-hint/#lets-see-it-in-action
       
       
   DIR <- back to front page