Toast plus auto hide minus the countdown progress bar

[kentqin-cve]

It would be nice to have an option to hide the countdown progress bar without losing the auto-hide functionality. Currently my hacky workaround (below) is to pre-schedule a later::later() to teardown of the toast. If there's a clean way through the API, that would be most appreciated.

observeEvent(input$trigger, {
  # 1. Define a unique tracking tag for the notification
  my_toast_id <- "server_timed_toast"
  
  # 2. Show the toast with duration_s = NULL to guarantee NO progress line elements 
  show_toast(
    toast(
      "This notification has no countdown bar and is closed by the server.",
      header = "No countdown bar",
      id = my_toast_id,    # Explicit handle tag
      duration_s = NULL    # Skip the timer
    )
  )
  
  # 3. Schedule the server to hide this specific toast after exactly 3 seconds
  later::later(\() {
    hide_toast(id = my_toast_id,session=session) 
  }, delay = 3)
  
})

[gadenbuie]

It would be nice to have an option to hide the countdown progress bar without losing the auto-hide functionality.

Thanks for the feature request. Can you please provide a little more context about why it would be nice to hide the progress bar?

[kentqin-cve]

I use toast as a modernized shiny::showNotification(), which provides operational updates to user in a non-attention-grabbing way. "Operations" being "saving data", "saving data successful", "job sent to queue", and etc. The presence of a progress bar creates visual distraction and confusion. For long mirai tasks, it gives the false impression that the task is progressing at the speed of the progress bar (when I only want it to be shown to the user that the task is queued, not executing instantaneously and live). For plain simple notification like "save is successful", the movement draws people's attention to it because it has moving parts, versus a mostly static web interface (progress bar is the source of distraction), and it gives the false sense that a simple "saving" operation takes 5 seconds, when only the success message lasts 5 seconds on the page.

[gadenbuie]

That makes sense, I think we could add an option to turn off the border.

Relatedly, I recently had an idea: would you be interested in an API for toasts that provides a withProgress() style progress bar for use with toasts that would reuse the progress bar border?

[kentqin-cve]

Thanks for considering the suggestion. Regarding the withProgressUpdate() idea, I am envisioning a decorator to be used in something similar this use case:

# inside server function, init the toast skeleton
notification_toast<-toast(id='nt', ... ) |> 
    withProgressUpdate()  # returns a function with setter args (i.e. new_pct=NULL, increment_pct=NULL, new_message=NULL)

et<-ExtendedTask$new(\(){
  notification_toast(new_message='task starting.', new_pct=0) |> show_toast()
  mirai::mirai({
    # some long task
    }) |> promises::finally(\(){
      notification_toast(new_pct=1.0, new_message="task resolved.") |> update_toast()
    })
  }) |> bind_task_button('start')

observeEvent(input$start,{
  et$invoke()
})