On Tue, 30 Nov 2004, Matthew Raymond wrote:
Olav Junker Kjær wrote:
It would be a useful feature if arbitrary HTML was allowed in option
elements. E.g. items in a dropdown could have different icons.
Yeah, personally, I think we should look at adding the |icon| attribute
to the option
On Fri, 17 Dec 2004, Anne van Kesteren wrote:
I don't really follow what you are proposing here. Could you give
more details?
Think of a SELECT element which has a table formatted dropdown list. This
enables you to do thinks like:
Name Tel
A. van Kesteren 000434
On Mon, 2 May 2005, Anne van Kesteren wrote:
I would like the specification to say more explicitly which value of the
TABINDEX attribute is the default value.
Is the spec clear enough now?
As TABINDEX is likely to affect if elements will match :enabled and
:disabled that should be stated
This is similar to the SSH model; the first time you connect,
you're expected to manually check by some means that you're
connecting to the right server. On subsequent connections, you
won't be bothered unless the key changes.
I'll concede that in most cases no-one actually verifies the
On Sun, 12 Jun 2005, Charles McCathieNevile wrote:
One of the difficulties is that many content providers don't want to
clutter their page with help links
Actually, given the way many sites actually do have help links, or ?
icons, or the like, I don't see content providers being
On Sun, 28 Aug 2005, Matthew Raymond wrote:
The altinput element is intended to be a possible alternative to my
earlier dataentry element.
[...]
I studied these proposals in depth.
To summarise for people who weren't there 3 years ago or who have
forgotten, the context is providing
Level of trust affects your decisions about whether you post, what
information you post, and whether you feel you have to encrypt it yourself.
Chris
-Original Message-
From: WeBMartians [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 2:29 AM
To: 'Eduard Pascual'; 'Kristof
On Mon, 30 Jan 2006, Ric Hardacre wrote:
hello, i'm an asp developer in the uk and have a couple of suggestions... no
doubt selfishly to make my life easier one day :-) these could probably do
with their own threads if they're deemed worthy of discussion but let's just
throw them out there:
Internet Explorer will continue to display warnings about unencrypted
submissions until you explicitly instruct it not to. I find this feature
useful per se, it works as Do you really want to submit this information?
Sometimes I do not, e.g. when I press something accidentally, and it allows
me
A LINK element cannot have a LABEL ancestor so Ian's answer seems to answer
a different request.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Wednesday, October 22, 2008 9:43 AM
To: Charles McCathieNevile
Cc: [EMAIL PROTECTED]
On Wed, 22 Oct 2008, Kristof Zelechovski wrote:
rel=help is now defined to apply to the link element's parent and its
children.
A LINK element cannot have a LABEL ancestor so Ian's answer seems to answer
a different request.
By link element I meant whatever element was creating the link
On Mon, 27 Feb 2006, laos wrote:
minlength attribute.
This attribute applies to
texthttp://whatwg.org/specs/web-forms/current-work/#text,
password http://whatwg.org/specs/web-forms/current-work/#password,
urlhttp://whatwg.org/specs/web-forms/current-work/#url,
and email
On Tue, Oct 21, 2008 at 10:04 PM, timeless [EMAIL PROTECTED] wrote:
Technically in gecko today CAPS should be able to squish canvas
methods per domain (not tested, but ask mao about offering a feature
in noscript for it).
The goal would not be to completely forbid canvas but to block it by
On Tue, Oct 21, 2008 at 10:14 PM, Aaron Swartz [EMAIL PROTECTED] wrote:
You're thinking of SNI:
http://en.wikipedia.org/wiki/Server_Name_Indication
which doesn't work in IE6, IE6, or Safari, making it less than useful
for anything serious.
anything proposed today to be added would appear
On Wed, 22 Oct 2008 09:15:32 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 2 May 2005, Anne van Kesteren wrote:
As TABINDEX is likely to affect if elements will match :enabled and
:disabled that should be stated as well.
Not sure I follow this.
I'm not sure either anymore :-)
I was
On Wed, Oct 22, 2008 at 2:07 PM, Fabien Meghazi [EMAIL PROTECTED] wrote:
The goal would not be to completely forbid canvas but to block it by
default while allowing the user to activate it when he wants to.
This is a nice feature to have, but the problem is, would it work in
reality? It works
On Mon, 3 Apr 2006, Henri Sivonen wrote:
On Apr 3, 2006, at 09:47, Ian Hickson wrote:
On Sat, 1 Apr 2006, Henri Sivonen wrote:
Should fieldset count as an interactive element for the purpose of
nesting rules?
No, since as you say:
A fieldset in a context where interactive
On Mon, 17 Apr 2006, Henri Sivonen wrote:
The multiple attribute, if present, must be either empty or have the
literal value multiple. Similarly, the disabled attribute, if present,
must be either empty or have the literal value disabled. (The actual
values do not have any effect on how
On Fri, 24 Mar 2006, Henri Sivonen wrote:
The spec says:
Certain elements in HTML can be activated, for instance a elements, button
elements, or input elements when their type attribute is set to radio.
When is an input element non-interactive? type='hidden' seems
non-interactive. The
Fabien Meghazi wrote:
Will it be possible for the browsers to allow an extension such as
canvas block ?
My understanding is that it won't be possible (please correct me if
I'm wrong, I'm not an expert) as the initialization of a canvas
context is done as follow :
var canvas =
On Wed, 22 Oct 2008, Jonas Sicking wrote:
Ian Hickson wrote:
Great! Thanks. I think your idea of making rel=help be relative to the
nearest parent label is a good one. We could also say it is relative
to
the nearest parent label, body, section, form, fieldset, or
other such
Ian Hickson wrote:
Great! Thanks. I think your idea of making rel=help be relative to the
nearest parent label is a good one. We could also say it is relative to
the nearest parent label, body, section, form, fieldset, or
other such grouping element. I'll look at this in more detail when
On Sun, 2 Jul 2006, Shadow2531 wrote:
On 7/1/06, dolphinling [EMAIL PROTECTED] wrote:
Can you even have an image map on an input type=image ?
Yes
This is no longer allowed in the spec, actually. Is that a problem?
--
Ian Hickson U+1047E)\._.,--,'``.
Hello,
I'd like to throw a question out here, please don't shoot me if it's been
already answered, I'm a full-time coder and don't have an internet at home
so I can't make any deep researches in your archives.
Q: Is it possible that hidden inputs don't have to be in a semantic tag?
That
On Fri, 18 Aug 2006, Gervase Markham wrote:
Henri Sivonen wrote:
Could you elaborate on the use cases? Are there a lot of use cases on
the Web now that force site author to hack awkward JavaScript widgets
themselves? Can't they continue using those hacks for uses cases that
are not
On Wed, Oct 22, 2008 at 10:41 AM, Oldřich Vetešník [EMAIL PROTECTED]wrote:
Hello,
I'd like to throw a question out here, please don't shoot me if it's been
already answered, I'm a full-time coder and don't have an internet at home
so I can't make any deep researches in your archives.
Q: Is
Dne Wed, 22 Oct 2008 17:40:55 +0200 Tab Atkins Jr. [EMAIL PROTECTED]
napsal/-a:
On Wed, Oct 22, 2008 at 10:41 AM, Oldřich Vetešník
[EMAIL PROTECTED]wrote:
Hello,
I'd like to throw a question out here, please don't shoot me if it's
been
already answered, I'm a full-time coder and don't
On Wed, 22 Oct 2008 17:41:37 +0200, Oldřich Vetešník [EMAIL PROTECTED]
wrote:
I'd like to throw a question out here, please don't shoot me if it's
been already answered, I'm a full-time coder and don't have an internet
at home so I can't make any deep researches in your archives.
Q: Is it
On Wed, 22 Oct 2008, Oldřich Vetešník wrote:
Q: Is it possible that hidden inputs don't have to be in a semantic tag?
That is it passes the validation test without showing this error up:
line 20 column 32 - Error: document type does not allow element input
here; missing one of p, h1, h2,
Ian Hickson wrote:
2. select tag:
selectedindex=[num]
implicitly set the selected index, instead of having to parse all the option
tags and insert a selected string, much easier to bind to server side data,
an invalid value (such as -1 or greater than the number of option tags) would
mean
I do not find the other code significantly simpler than the present one.
I would rather say:
Sub printOption(value, selected, text)
Dim Opt
Set Opt = Option. Create(value, text)
Opt. selected = (value = selected)
Response.Write Opt.outerHTML
End Sub
I suggested the same thing a week ago:
http://www.nabble.com/input-type%3Dhidden-outside-phrasing-content-td275
4.html#a2754
with replies here:
http://www.nabble.com/Re:-input-type%3Dhidden-outside-phrasing-content-td200
00847.html#a20023298
The short answer is that for some elements
Ian Hickson wrote:
I believe in HTML5 that we've allowed input in most places,
which should
satisfy your needs. Let us know if it does not. :-)
We discussed this last week
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-October/016655.html
and HTML5 is certainly a step forward in
On Wed, 22 Oct 2008, Mike Wilson wrote:
- allowing hidden input:s to actually live anywhere (this is
probably hard to do dtd/validation-wise)
It's easy to specify, the problem is that it makes it easy for authors to
get in trouble if they change the type attribute on the fly (e.g. in an
On 22/10/2008 19:58, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 22 Oct 2008, Mike Wilson wrote:
- allowing hidden input:s to actually live anywhere (this is
probably hard to do dtd/validation-wise)
It's easy to specify, the problem is that it makes it easy for authors to
get in trouble
I haven't reviewed the new draft yet just a preliminary comment for now.
* intercept namespaces [new]
This form of namespace is not in the spec at present. This is a proposal to
add it. It is a heavily used feature of the Gears LocalServer. The basic
idea is to intercept requests into this
Ian Hickson wrote:
On Wed, 22 Oct 2008, Mike Wilson wrote:
- allowing hidden input:s to actually live anywhere (this is
probably hard to do dtd/validation-wise)
It's easy to specify, the problem is that it makes it easy
for authors to
get in trouble if they change the type
You're doing dom work, the code jonas wrote reminds me of perl which
typically doesn't generate a dom and then serialize it to send out
over the wire. Among other things serializing often requires the
entire document which means you can't build and incrementally send the
document over the wire.
38 matches
Mail list logo
