On 4/29/07, Brian Campbell [EMAIL PROTECTED] wrote:
For the sort of content that we produce, cue points are incredibly
important. Most of our content consists of a video or voiceover
playing while bullet points appear, animations play, and graphics are
revealed, all in sync with the video. We
On 3/6/07, Matthew Raymond [EMAIL PROTECTED] wrote:
To me, the only advantage of a global |href| is that you can use it
on block-level elements, and I don't see why a block-level version of
a couldn't fill the same use case.
Indeed. IMO, global |href| gives nothing but more confusion. If
On 3/10/06, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 9 Mar 2006, Henri Sivonen wrote:
It seems to me that the WA 1.0 spec presents requirements on document
conformance that are very different from each other in spirit in a
seemingly arbitrary way.
On one hand, some elements are
On 1/25/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
I'm not saying it won't break anything, but every single change we make
to the parsing could possibly break any number of the billions of pages
on the web in any number of browsers.
But using your method (swapping inline node and block node)
On 1/25/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Billy Wong wrote:
On 1/25/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
I'm not saying it won't break anything, but every single change we make
to the parsing could possibly break any number of the billions of pages
on the web in any number
On 1/26/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Alexey Feldgendler wrote:
On Thu, 26 Jan 2006 08:34:38 +0600, Lachlan Hunt
[EMAIL PROTECTED] wrote:
Semantically, it makes no sense at all to put a block level element
within an inline element.
Because CSS lets you redefine what's
On 1/26/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Billy Wong wrote:
On 1/26/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
No, you just need to use the a element and set
a { display: block; height: Y; width: X; }
You may not even need to set the width or height or you may need to set
