On May 18, 2007, at 12:43 PM, Lachlan Hunt wrote:
...
* class=search
The aim of this one was to be able to indicate the form specifically
used for searching. This would then allow UAs, especially assistive
technology, to implement keyboard shortcuts or other mechanisms for
taking the user
If input type=search were to be standardized, Apple would need this
done in a way that would be backwards-compatible with our current
syntax. Otherwise we'd be forced to require an opt-in mode for HTML5
(and that is really not something we want to have to do).
dave
([EMAIL PROTECTED])
On
On Fri, 22 Apr 2005, Jon Udell wrote:
OK. Then I do propose an easy way to issue a non-interactive HTTP POST.
There are two ways to do it today; XMLHttpRequest and dynamic form
creation. The former allows for behind-the-scenes stuff and the latter
is needed when you want to replace the
On Fri, 22 Apr 2005, Brad Neuberg wrote:
Here's a possible API for GET and POST semantics without XmlHttpRequest:
window.location.href = base URL + URL parameters already appended
window.location.method = GET or POST, nothing else supported
If the method is a POST method, the internal
On May 18, 2007, at 3:40 PM, Ian Hickson wrote:
On Wed, 20 Apr 2005, Dean Edwards wrote:
1) Mozilla's DOMContentLoaded event is very handy. It fires when a
node's content has been loaded and parsed (the DOM has been
constructed). This is much better than the standard onload event as
it
On May 18, 2007, at 4:19 PM, Ian Hickson wrote:
On Fri, 22 Apr 2005, Brad Neuberg wrote:
Here's a possible API for GET and POST semantics without
XmlHttpRequest:
window.location.href = base URL + URL parameters already appended
window.location.method = GET or POST, nothing else supported
On Fri, 18 May 2007, Maciej Stachowiak wrote:
1) Mozilla's DOMContentLoaded event is very handy. It fires when a
node's content has been loaded and parsed (the DOM has been
constructed). This is much better than the standard onload event as
it doesn't wait for binary content to
On 19/05/07, Ian Hickson [EMAIL PROTECTED] wrote:
3) I find myself using Microsoft's uniqueID property quite often. Although the
ID attribute is supposed to provide a unique identifier, it often doesn't. We
would probably need a complementary DOM method to retrieve an element by
uniqueID (IE
