webbrowser-app currently doesn’t handle the empty mesage case. We could make it handle it, of course, but I think your proposal of exposing the stock message to the existing Oxide API makes sense, as it would mean no API/behaviour changes.
webbrowser-app currently doesn’t handle the empty mesage case. We could make it handle it, of course, but I think your proposal of exposing the stock message to the existing Oxide API makes sense, as it would mean no API/behaviour changes.