diff --git a/files/en-us/web/api/indexeddb_api/checking_when_a_deadline_is_due/index.html b/files/en-us/web/api/indexeddb_api/checking_when_a_deadline_is_due/index.html index fcfe1ec1c4d160a..0370b713678ed95 100644 --- a/files/en-us/web/api/indexeddb_api/checking_when_a_deadline_is_due/index.html +++ b/files/en-us/web/api/indexeddb_api/checking_when_a_deadline_is_due/index.html @@ -13,9 +13,9 @@
In this article we look at a complex example involving checking the current time and date against a deadline stored via IndexedDB. The main complication here is checking the stored deadline info (month, hour, day, etc.) against the current time and date taken from a Date object.
- + -The main example application we will be referring to in this article is To-do list notifications, a simple to-do list application that stores task titles and deadline times and dates via IndexedDB, and then provides users with notifications when deadline dates are reached, via the Notification, and Vibration APIs. You can download the To-do list notifications app from github and play around with the source code, or view the app running live.
+The main example application we will be referring to in this article is To-do list notifications, a simple to-do list application that stores task titles and deadline times and dates via IndexedDB, and then provides users with notifications when deadline dates are reached, via the Notification, and Vibration APIs. You can download the To-do list notifications app from github and play around with the source code, or view the app running live.
To provide a reasonable user experience on mobile devices, and to cut down on ambiguities, I decided to create an HTML form with:
- +Setting up a web application as a protocol handler is not a difficult process. Basically, the web application uses registerProtocolHandler()
to register itself with the browser as a potential handler for a given protocol. For example:
Setting up a web application as a protocol handler is not a difficult process. Basically, the web application uses registerProtocolHandler()
to register itself with the browser as a potential handler for a given protocol. For example:
navigator.registerProtocolHandler("web+burger", "http://www.google.co.uk/?uri=%s", @@ -38,7 +38,7 @@Registering
When a browser executes this code, it should display a prompt to the user, asking permission to allow the web application to register as a handler for the protocol. Firefox displays a prompt in the notification bar area:
- +Note:The URL template supplied when registering must be of the same domain as the webpage attempting to perform the registration or the registration will fail. For example,@@ -124,7 +124,7 @@http://example.com/homepage.html
can register a protocol handler forhttp://example.com/handle_mailto/%s
, but not forhttp://example.org/handle_mailto/%s
.References
See also
A PannerNode
always has exactly one input and one output: the input can be mono or stereo but the output is always stereo (2 channels); you can't have panning effects without at least two audio channels!