On Wed, 12 Aug 2009, Sebastian Markb�ge wrote:
The spec should explicitly specify which MouseEvent properties are
available during the various drag events to avoid assumptions.
The spec requires them to all be set on all drag events, currently.
I thought that this was clear too
On Wed, 12 Aug 2009, Aryeh Gregor wrote:
On Wed, Aug 12, 2009 at 3:08 AM, Ian Hicksoni...@hixie.ch wrote:
In 4.2.4:
If the attribute is present, then the user agent must assume that
the resource is of the given type. If the attribute is omitted, but
the external resource link type has
On Wed, 12 Aug 2009, Erik Vorhes wrote:
On Wed, Aug 12, 2009 at 6:21 PM, Ian Hicksoni...@hixie.ch wrote:
On Mon, 3 Aug 2009, Erik Vorhes wrote:
On Mon, Aug 3, 2009 at 6:29 AM, Ian Hickson i...@hixie.ch wrote:
Not all titles are citations, actually. For example, I've heard of
the
On Thu, 13 Aug 2009, Philip Jägenstedt wrote:
We would like to request that addCueRange/removeCueRanges be dropped
from the spec before going into Last Call. We are not satisfied with it
and want to see it replaced with a solution that includes (scriptless)
timed text (a.k.a
On Sun, Aug 16, 2009 at 6:52 AM, Ian Hicksoni...@hixie.ch wrote:
They can follow the links (not following the links is a should not, not
a must not). Once they follow the links, they must ignore the type=
attribute and only take into account the MIME type provided by the server.
I was assuming
On 16/08/2009 12:21, Ian Hickson wrote:
Italics is the right format for almost all titles of works.
How are you measuring that?
For example, chapters in collections and articles are works and have
titles, and those titles aren't typically distinguished with italics, at
least in English.
That suggestion has also been floating around in some internal discussions.
I'd have to objections to this approach either, although I'm not familiar
enough with URL semantics to know if this is a valid use of URL fragments.
-atw
On Sat, Aug 15, 2009 at 5:29 PM, Jim Jewett jimjjew...@gmail.com
Drew Wilson wrote:
Per section 4.8.3 of the SharedWorkers spec, if a
page loads a shared worker with a url and name,
it is illegal for any other page under the same
origin to load a worker with the same name but a
different URL -- the SharedWorker name becomes
essentially a shared
Tim Berners-Lee seems to think this could be a valid use of URI references.
http://www.w3.org/DesignIssues/Fragment.htmlThe significance of the
fragment identifier is a function of the MIME type of the object
Are there any existing semantics defined for fragments on text/java-script
objects?
//
On Sun, Aug 16, 2009 at 12:51 PM, Michael Nordman micha...@google.comwrote:
I'd have to objections to this
Did you mean to say i'd have no objectsion to this?
Yes, I have *no* objections to either approach. Apparently the coffee hadn't
quite hit my fingers yet.
-atw
... Additionally, a typo in one page (i.e. invoking
SharedWorker(mypagescript?, name) instead of
SharedWorker(mypagescript, name) will keep all subsequent pages in that
domain from loading a worker under that name so long as the original page
resides in the page cache.
In this case, if typo one
11 matches
Mail list logo
