Hi all,
I really like this idea, how would this be handled from a presentational point
of view? I guess it will be a CSS style issue but, will browsers implement some
standard way of displaying these cite elements if it has the uri attribute?
Schalk Neethling
From:
The way I see it is that instead of browsers traversing the DOM looking
for
an input field of either id=username or name=username or even
class=username, they now only have to look for an input of type username.
Makes it a lot easier for both developers and browser vendors as they now
only
Your suggestion sounds really interesting Thomas, I will have a read over it. I
agree that if your username field will be in the form of an email address, then
simply use type=username with a pattern to facilitate email validation. Not
sure if that is really even needed at that point anyway
meta=encrypt pubkey=ABABAEFEF2626EFEFEF
pubtool=EC256-AES|RSA2048-AES passsalt=no|domainname
auth=verisign
Please try to fully decrypt the above meta-encrypt tag and *see* how
the browser-server communication could utilize it. (HINT: browser
submits a (session specific) 256bit elliptic
On Thu, May 6, 2010 at 12:12 PM, Mounir Lamouri wrote:
On 05/06/2010 12:09 PM, Thomas Broyer wrote:
On Thu, May 6, 2010 at 11:51 AM, Markus Ernst derer...@gmx.ch wrote:
Am 05.05.2010 23:06 schrieb Schalk Neethling:
The way I see it is that instead of browsers traversing the DOM looking
for
On Thu, 2010-05-06 at 14:54 +0200, Thomas Broyer wrote:
On Thu, May 6, 2010 at 12:12 PM, Mounir Lamouri wrote:
On 05/06/2010 12:09 PM, Thomas Broyer wrote:
On Thu, May 6, 2010 at 11:51 AM, Markus Ernst derer...@gmx.ch wrote:
Am 05.05.2010 23:06 schrieb Schalk Neethling:
The way I see
Schalk Neethling writes:
if your username field will be in the form of an email address, then
simply use type=username with a pattern to facilitate email
validation.
Surely a major reason for having standard validation types is so web
developers don't need to come up with patterns for these
On May 6, 2010, at 3:19 AM, Anne van Kesteren wrote:
On Wed, 05 May 2010 13:47:13 +0900, Ian Hickson i...@hixie.ch wrote:
On Tue, 4 May 2010, Perry Smith wrote:
It would be wonderful if an element had an event that would fire when
that particular element is shown on the page. This might be
Smylers,
I understand what you mean but, then I have to agree with Thomas that you
can then use an input of type username and use the pattern to validate the
email address.
Schalk
-Original Message-
From: whatwg-boun...@lists.whatwg.org
[mailto:whatwg-boun...@lists.whatwg.org] On Behalf
Is there any value in adding an href or uri or similar attribute
to the cite element to indicate a location for a work (or
information about the work) or, in the case of a URI, an indicator
that can be used as a reference programmatically?
cite uri has a much worse fallback story than simply
On Tue, 20 Apr 2010 16:00:36 +0200, Simon Pieters sim...@opera.com wrote:
[[
WebSocket object with an open connection must not be garbage collected
if there are any event listeners registered for message events.
]]
Shouldn't it also not be garbage collected if there are listeners for
input type=text pattern=email
input type=username pattern=email
What if for some strange reason I wanted to only allow the text
e-m-a-i-l ? There would have to be some way to differentiate between a
keyword and a normal pattern.
On Thu, May 6, 2010 at 5:44 AM, juuso_ht...@tele3d.net wrote:
meta=encrypt pubkey=ABABAEFEF2626EFEFEF pubtool=EC256-AES|RSA2048-AES
passsalt=no|domainname auth=verisign
Please try to fully decrypt the above meta-encrypt tag and *see* how the
browser-server communication could utilize it.
Might be a wrong assumption but, if you place those values into an HTML
element, it is visible by simply doing a view source. I am jumping in the
middle of the conversation here but, this strikes me as opening another problem.
Schalk
-Original Message-
From:
On Thu, May 6, 2010 at 8:44 AM, juuso_ht...@tele3d.net wrote:
meta=encrypt pubkey=ABABAEFEF2626EFEFEF pubtool=EC256-AES|RSA2048-AES
passsalt=no|domainname auth=verisign
Please try to fully decrypt the above meta-encrypt tag and *see* how the
browser-server communication could utilize it.
Just to rectify any misunderstanding, I love the date picker that Opera
provides and others will hopefully do in turn but, my question is that
currently using type=date only provides the option of selecting a date using
the date picker. In a recent talk I gave on HTML 5 the question arose that
On Thu, May 6, 2010 at 3:30 PM, Schalk Neethling
sch...@ossreleasefeed.com wrote:
Just to rectify any misunderstanding, I love the date picker that Opera
provides and others will hopefully do in turn but, my question is that
currently using type=date only provides the option of selecting a
On Fri, May 7, 2010 at 06:41, Garrett Smith dhtmlkitc...@gmail.com wrote:
Opera has native support that mostly works but failed with dates prior
to 1582, last I checked.
This seems reasonable. Gregorian calendar started in 1582.
--
TAMURA Kent
Software Engineer, Google
On Fri, 07 May 2010 10:52:15 +0900, Garrett Smith dhtmlkitc...@gmail.com
wrote:
On Thu, May 6, 2010 at 6:50 PM, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Disregard that: Proleptic Gregorian is not required, but optional for
ISO 8601. Regardless:-
That specification in this case is HTML 5
On Thu, May 6, 2010 at 7:30 PM, Anne van Kesteren ann...@opera.com wrote:
On Fri, 07 May 2010 10:52:15 +0900, Garrett Smith dhtmlkitc...@gmail.com
wrote:
On Thu, May 6, 2010 at 6:50 PM, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Disregard that: Proleptic Gregorian is not required, but
On 5/4/10 12:08 AM, Eitan Adler wrote:
3) Currently autofill for usernames looks for something like
id=username or name=username. However on certain websites this
fails. Furthermore some websites offer a find other members feature
where you could type in a username. I've often seen these fields
21 matches
Mail list logo
