On Mon, 04 Sep 2006 19:37:30 +0200, Keryx webb [EMAIL PROTECTED] wrote:
To make the whole LI-element clickable I have to resort to CSS
( ul#nav li a { display: block } ) which does not work in all browsers
or JavaScript, which also is a hassle.
Yeah, li href=test/li does work in all browsers
Keryx webb wrote:
Will it break backwards compatibility? Yes, if todays browsers are
supposed to be able to render WHATWG-pages. But there are lots of other
things in WHATWG that they do not understand either. It's only the very
latest browsers that can handle canvas. No browser fully
Sorry for starting a thread and then being away for quite a while. I've been
exceptionally busy!
Let's clarify some of my wishes:
Do I wish that the href-attribute is available on exactly *every* element? No,
but on many *more* than today.
A. I do find myself writing a lot of:
abbr
Kornel Lesinski wrote:
My current solution is:
tr onclick=this.getElementsByTagName('a')[0].click()
This can be accomplished by having a elements in each individual
cell...
Of course it can, but it bloats code a lot. You have to add several
redundant links, add tabindex=-1 to avoid
Andrew Fedoniouk wrote:
Ian Hickson wrote:
a href=
h2.../h2
p.../p
/a
If we will change model of A from
!ELEMENT A - - (%inline;)* -(A) -- anchor --
to something else then it will create implications for parser.
What implications? Changing the formal content model of an
- Original Message -
From: Lachlan Hunt [EMAIL PROTECTED]
To: Andrew Fedoniouk [EMAIL PROTECTED]
Cc: Ian Hickson [EMAIL PROTECTED]; Anne van Kesteren
[EMAIL PROTECTED]; WHATWG [EMAIL PROTECTED]
Sent: Monday, August 28, 2006 11:05 PM
Subject: Re: [whatwg] href on any element
Andrew
Andrew Fedoniouk wrote:
Lachlan Hunt wrote:
Andrew Fedoniouk wrote:
Ian Hickson wrote:
a href=
h2.../h2
p.../p
/a
If we will change model of A from
!ELEMENT A - - (%inline;)* -(A) -- anchor --
to something else then it will create implications for parser.
What
Ian Hickson wrote:
On Mon, 28 Aug 2006, Anne van Kesteren wrote:
On Mon, 28 Aug 2006 11:33:43 +0200, Lachlan Hunt [EMAIL PROTECTED]
wrote:
It's arguably a very minor improvement,
The only benefit I'm aware of is the convenience it provides to authors for
hand coding, but that benefit is
Lachlan Hunt wrote:
Andrew Fedoniouk wrote:
If yes then let it be just :
section href=...
h2...
p...
/section
But that isn't backwards compatible.
data:text/html,tabletra hef=www.google.comtdlink to
google/td/atdplain text/td/tr/table
Neither is a around table cells or list items.
What practical use has this for Mr Joe Public?
Give me a really useful example in very simple wording!
Francisco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dolphinling
Sent: 29 August 2006 16:46
To: WHAT WG List
Subject: Re: [whatwg] href on any
On Tue, 29 Aug 2006 17:02:22 +0100, Francisco Monteiro
[EMAIL PROTECTED] wrote:
What practical use has this for Mr Joe Public?
Give me a really useful example in very simple wording!
Having data table representing list of items where large clickable area is
useful - i.e. inbox in a
Kornel Lesinski wrote:
On Tue, 29 Aug 2006 17:02:22 +0100, Francisco Monteiro
Having data table representing list of items where large clickable area is
useful - i.e. inbox in a webmail, list of contacts, forum threads listing,
etc.
I've ran into this problem many times and seen many
On Tue, 29 Aug 2006 22:55:01 +0100, Matthew Raymond
[EMAIL PROTECTED] wrote:
Having data table representing list of items where large clickable area
is useful - i.e. inbox in a webmail, list of contacts, forum threads
listing, etc.
I've ran into this problem many times and seen many
On Sat, 26 Aug 2006, Keryx webb wrote:
Shut me up and give me a link if this has been discussed before, but I
can't find it on Google. Has there been any discussion of allowing the
href-attribute in (almost) any element, as in XHTML 2.0?
It's been mentioned, mostly in passing.
The biggest
Keryx webb wrote:
Shut me up and give me a link if this has been discussed before, but I
can't find it on Google. Has there been any discussion of allowing the
href-attribute in (almost) any element, as in XHTML 2.0?
Personally I think this is the one killer feature of XHTML 2 and I would
Ian Hickson wrote:
It isn't always clear what it would mean, either (consider col href=,
or optgroup href=).
If the feature were to be added to Web Apps 2.0 (or other future spec) I
think it would be sensible to limit it to inline, non-interactive,
non-empty elements (e.g. abbr, em, strong,
On Mon, 28 Aug 2006 11:33:43 +0200, Lachlan Hunt
[EMAIL PROTECTED] wrote:
It's arguably a very minor improvement,
The only benefit I'm aware of is the convenience it provides to authors
for hand coding, but that benefit is negligible when you consider the
abilities of many authoring tools
On Mon, 28 Aug 2006, Anne van Kesteren wrote:
On Mon, 28 Aug 2006 11:33:43 +0200, Lachlan Hunt [EMAIL PROTECTED]
wrote:
It's arguably a very minor improvement,
The only benefit I'm aware of is the convenience it provides to authors for
hand coding, but that benefit is negligible when
Hi all
Shut me up and give me a link if this has been discussed before, but I can't
find it on Google. Has there been any discussion of allowing the href-attribute
in (almost) any element, as in XHTML 2.0?
Personally I think this is the one killer feature of XHTML 2 and I would soo
much
Hi,
From: Keryx webb [EMAIL PROTECTED]
Shut me up and give me a link if this has been discussed before, but I
can't find it on Google. Has there been any discussion of allowing the
href-attribute in (almost) any element, as in XHTML 2.0?
20 matches
Mail list logo
