- From: Bjartur Thorlacius <svartman95@gmail.com>
- Date: Tue, 1 Mar 2011 17:39:59 +0000
On 3/1/11, Ben Rimmington <benrimmington at me.com> wrote: > On 28 Feb 2011, at 17:52, Bjartur Thorlacius wrote: > >> Can't we extend the existing window.status? >> It's supported by some older UAs (and ignored by others, because of >> confusing UI), but if the UI distinguishes page messages from browser >> and system messages, it's usable (aside from a historical API, but if >> browsers ignore setting the window.status to the empty string). > > The window.status property [1] doesn't seem to be in the WHATWG HTML spec, I > could only find the window.statusbar.visible property [2]. > > But I doubt that any mobile UAs have a status bar, and it's also hidden by > default on Mac OS X Safari (and possibly other desktop UAs as well). > > However, some mobile platforms have a local notification service [3] [4] [5] > [6]. A new window.notify() function might be useful, so that a background > card/tab/window can display a message to the user. > > (Unfortunately, iOS currently uses a modal dialog for its > UILocalNotification service. A better implementation might be to put a > Notification Center icon in the multitasking UI, similar to the Print Center > [7] used by AirPrint.) I meant to suggest displaying strings assigned to (the unstardandized property) window.status, supported by some browsers, using e.g. methods described in your post.
Received on Tuesday, 1 March 2011 09:39:59 UTC