On Wed, 23 Jan 2008, Jeff Walden wrote:
>
> The spec as currently written says that document.domain in a document
> located at a URI with no domain is null:
>
> data:text/html,alert(document.domain);
>
> Safari and Opera both alert the empty string for this; Firefox alerts
> null.
I've changed
Křištof Želechovski wrote:
If the server infers the MIME type from content and sends it over HTTP as it
should, you can have both.
Changing servers (including getting existing installs updated) is even more
painful than changing browsers, though.
It would be very nice if servers had better M
On Wed, 23 Jan 2008, Jeff Walden wrote:
>
> The current verbiage describing open() says nothing about the document's
> origin reflecting that of the mutator, which is an oversight which
> should eventually be corrected. This came up when considering the
> values of the domain/uri properties on
On Mon, 28 Apr 2008 23:14:03 +0200, Brady Eidson <[EMAIL PROTECTED]> wrote:
I would like to make sure that my understanding is correct here, since
you expressed doubt.
Anne was asserting that since the interface for setItem() specifies a
DOMString as the input, anything you pass it will be s
On Mon, Apr 28, 2008 at 2:04 PM, Křištof Želechovski <[EMAIL PROTECTED]>
wrote:
> What is the advantage of cutting an image to parts
> and having the browser show them as one by putting them aside?
> I would rather use one big image in the first place.
> Chris
>
On my company's web site, our heade
Ian Hickson wrote:
On Mon, 29 Aug 2005, Henri Sivonen wrote:
On Aug 28, 2005, at 09:56, Henri Sivonen wrote:
How should the lowercasing be performed? Using the locale-insensitive
Unicode case data or for ASCII only treating non-ASCII as an error?
On further reflection, it seems to me the latte
On Apr 27, 2008, at 5:32 PM, Ian Hickson wrote:
On Thu, 10 Apr 2008, Brady Eidson wrote:
In 4.10.5, the description of the properties on the StorageEvent
object
mentions "...its newValue attribute set to the new value of the key
in
question, or null if the key was removed..."
So a web a
If the server infers the MIME type from content and sends it over HTTP as it
should, you can have both.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Boris Zbarsky
Sent: Saturday, April 19, 2008 6:10 AM
To: William F Hammond
Cc: [EMAIL PROTECTED];
ALTGROUP is a dirty trick; if you insist on having the images separate,
which you really should not do, you can have
This extension would be closer to the meaning IMHO.
Otherwise, what happens if the images that belong to the same ALTGROUP of
yours are not contiguous?
Chris
-Original Message-
Křištof Želechovski wrote:
How about target="_guide" instead?
A reference is usually lengthy and unreadable;
the designer should know better
than to treat the poor user with a reference.
Or _notification. Most of what Matthew wants to use it for seems to be
notifications.
How are you suppos
Or even
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Mason
Sent: Saturday, April 19, 2008 10:14 PM
To: Simon Pieters
Cc: [EMAIL PROTECTED]
Subject: Re: [whatwg] ALT and equivalent representation
Simon Pieters wrote:
> For instance it would be rea
Jeff Walden wrote:
Ian Hickson wrote:
I haven't changed the target of the event, it's still the Document
object. This is a little odd, though, would people rather I made it
the element with an auto-forward to the Window object, like the
'load' event and so forth? That would allow onmessage=""
I am sorry to hear that cross-references are gone. The replacement you
suggest does not catch the difference between navigational and informational
hyperlinks. The difference is essential e.g. for GNU info: navigational
links are "near jumps" to child nodes; informational links can transport the
What is the advantage of cutting an image to parts
and having the browser show them as one by putting them aside?
I would rather use one big image in the first place.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shannon
Sent: Monday, April 21,
Although providing the footnote as a tool-tip
seems appealing at the first glance,
it is not exactly how it should be done.
Footnotes are commonly used for bibliographic references;
using the title attribute seems to be a non-solution in this case.
Text of such "footnotes" cannot be copied
an
Samuel Santos wrote:
When writing technical HTML documents, I often feel a need for an element to
represent a path or a file in the file system. But I couldn't find any
semantically correct element to do this.
I usually use C:\foo\bar but it just feels
wrong...
Is it worthy to have another HTML
When writing technical HTML documents, I often feel a need for an element to
represent a path or a file in the file system. But I couldn't find any
semantically correct element to do this.
I usually use C:\foo\bar but it just feels
wrong...
Is it worthy to have another HTML element like (I'm not
This issue is not limited to PRE, nor is PRE the main application.
There are numerous community Web sites
that allow the users to submit hypertext content.
You often get italic bold after you submit
unless you use a zero-width non-joiner between them.
While this is not strictly a HTML problem
18 matches
Mail list logo
