On Sat, 4 Apr 2009, Innovimax SARL wrote:
In 2.3 Case-sensitivity and string comparison
Please replace
Converting a string to uppercase
and
Converting a string to lowercase
by respectively
Converting a string to uppercase ASCII
and
Converting a string to lowercase ASCII
Done.
On Fri, 3 Apr 2009, Ojan Vafai wrote:
I'm suggesting an addition to cross-domain (i)frames that allows
scrolling specific content into view. The use case is sites that
aggregate data from many sites (e.g. search engines) and want to display
that data in an iframe. They can load the page in
On Wed, Jun 3, 2009 at 3:28 PM, Daniel Berlin dan...@google.com wrote:
On Tue, Jun 2, 2009 at 11:51 PM, Gregory Maxwell gmaxw...@gmail.com wrote:
On Tue, Jun 2, 2009 at 10:18 PM, Daniel Berlin dan...@google.com wrote:
On Tue, Jun 2, 2009 at 9:50 PM, Gregory Maxwell gmaxw...@gmail.com wrote:
On
Thanks, Ian !
On Wed, Jun 3, 2009 at 8:45 AM, Ian Hickson i...@hixie.ch wrote:
On Sat, 4 Apr 2009, Innovimax SARL wrote:
In 2.3 Case-sensitivity and string comparison
Please replace
Converting a string to uppercase
and
Converting a string to lowercase
by respectively
The HTML element cannot have a FIELDSET element as a child. It can,
however, have a FRAMESET element as a child.
Chris
On Wed, 3 Jun 2009, Kristof Zelechovski wrote:
The HTML element cannot have a FIELDSET element as a child. It can,
however, have a FRAMESET element as a child.
Yes, this is indeed the case. Is there a particular reason you bring this up?
--
Ian Hickson U+1047E
On Sat, 4 Apr 2009, Kristof Zelechovski wrote:
It seems that getting the element name is not covered at all, it is a core
interface, so definitions in the HTML specification do not apply.
I don't know what this is in reference to. Could you elaborate on what
change to the spec you would like?
On Jun 3, 2009, at 09:45, Ian Hickson wrote:
On Sat, 4 Apr 2009, Innovimax SARL wrote:
In 2.3 Case-sensitivity and string comparison
Please replace
Converting a string to uppercase
and
Converting a string to lowercase
by respectively
Converting a string to uppercase ASCII
and
Converting a
On Sat, 4 Apr 2009, João Eiras wrote:
On , Jeremy Orlow jor...@google.com wrote:
I think this also applies: NOTE: The lifetime of a browsing context
can be unrelated to the lifetime of the actual user agent process
itself, as the user agent may support resuming sessions after a
Yeah, this is really pretty difficult stuff. The lgpl is probably the
least understood and most complicated free software licenses.
Chris
On Wed, Jun 3, 2009 at 2:49 PM, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Jun 3, 2009 at 3:28 PM, Daniel Berlin dan...@google.com wrote:
On
On Wed, 03 Jun 2009 09:34:08 +0200, Chris DiBona cdib...@gmail.com wrote:
Yeah, this is really pretty difficult stuff. The lgpl is probably the
least understood and most complicated free software licenses.
Thanks for taking the time to explain it!
--
Anne van Kesteren
I mostly wanted to explain our position on the use of the library and
the LGPLs. Danny keeps it all straight for us.
Happy hacking, everyone!
Chris
On Wed, Jun 3, 2009 at 3:40 PM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 03 Jun 2009 09:34:08 +0200, Chris DiBona cdib...@gmail.com
On Wed, Jun 3, 2009 at 12:36 AM, Philip Taylor excors+wha...@gmail.com wrote:
http://blogs.msdn.com/ie/archive/2008/09/02/ie8-security-part-vi-beta-2-update.aspx
- it's X-Content-Type-Options: nosniff now (and is used a bit in
practice - it's on about 0.1% of pages from
The definition of uppercasing in HTML does not apply to element names
because getting them is covered by the DOM specification and not by the HTML
specification. This is all right with me; I only think that saying to
uppercase ASCII explicitly is not necessary.
Chris
On Sun, 5 Apr 2009, Giovanni Campagna wrote:
A few comments, as requested by Ian Hickson.
- End of 2.2.1, a typo: JavsScript instead of Javascript
Fixed.
- From section 2.4.2 I don't understand if boolean attributes with
invalid values represent true or false. In addition, I don't
On Sun, 5 Apr 2009, Kristof Zelechovski wrote:
Now that classid is gone, what will be the workaround for ActiveX
objects where they are needed?
ActiveX controls are a vendor-specific technology, and thus not
appropriate for explicit support in HTML5 (just like we dropped applet).
The real
On Sun, 5 Apr 2009, João Eiras wrote:
The spec does not forbid to use non supported attributes and elements.
Actually, it does. I've just made the spec even clearer about this,
though.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
On Sun, 5 Apr 2009, Christoph Päper wrote:
Giovanni Campagna:
- The second paragraph in 2.4.5.6 is hard to understand because the
verb is at the end. I would rewrite as
A week-year with a number *yr* has 53 weeks if corresponds to a year *yr*
in the proleptic Gregorian calendar that has a
The validator generates an error for the classid attribute (in line with
what the specification says, I think). An error, unlike a warning, breaks
any complex process that depends on successful validation of the components.
I think the specification text should be rephrased so that the validator
On Tue, Jun 2, 2009 at 12:05 PM, James Graham jgra...@opera.com wrote:
Bruce D'Arcus wrote:
So exactly what is the process by which this gets resolved? Is there one?
Hixie will respond to substantive emails sent to this list at some point.
However there are some hundreds of outstanding
Hi,
I have a question about the Application Caches update process:
http://dev.w3.org/html5/spec/Overview.html#application-cache-update-process
In the event of a failure during the update process (e.g. some error
reported when attempting to save the downloaded resources to stable
storage), the
Regarding
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.
html#weeks:
A week begins on Sunday, not on Monday.
However, under the present assumption:
Better:
A week-year has 53 weeks if the first day of the year (January 1st)
in the proleptic Gregorian calendar
Kristof Zelechovski wrote:
Regarding
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.
html#weeks:
A week begins on Sunday, not on Monday.
Not according to ISO [1]
[1] http://en.wikipedia.org/wiki/ISO_week_date
On Sun, Apr 5, 2009 at 9:04 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
A few comments, as requested by Ian Hickson.
[...]
- In section 3.3.3.7, instead of defining the syntax of style
attributes, reference http://www.w3.org/TR/css-style-attr
The style property has been part of
It is possible to create no-script fallback without a NOSCRIPT element. You
can put it into d...@class=noscript] and remove the DIV at run time.
It is worth noting that XHTML 1.0, along with deprecating MAP/@name, still
has the unrealistic assumption about usemap containing an arbitrary URI. I
On Tue, 7 Apr 2009, Jeff Creamer wrote:
Hi. Since March of '06, Opera 9 has supported a custom extension to the
canvas context called opera-2dgame. Importantly, their extension adds
these methods:
getPixel(x, y)
Returns the pixel value (colour, opacity) at (x, y). Returned in the
form
On Wed, 8 Apr 2009, Charles Pritchard wrote:
Legacy clients may have terrible support for extensibility. With some
HTML consumers, base 64 encoded images are not usable in the global
scope. To get around this, we proposed using toTempURL(), to save an
image to the local temporary files
On Thu, 9 Apr 2009, Randy Drielinger wrote:
Currently (HTML4.01) and in the near-future HTML5 spec optgroup elements
are used to group options (hence the name :-) and amongst others allow
us to disable a group of option elements at once.
Personally, I think it would make sense to add the
On Thu, 9 Apr 2009, Honza Bambas wrote:
In the W3C spec for localStorage
http://dev.w3.org/html5/webstorage/#the-localstorage-attribute is said
to present it (the persistent storage) the same way as cookies.
There were suggestion to throw DOM_QUOTA_ERROR exception when storing to
On Wed, Jun 3, 2009 at 1:15 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 9 Apr 2009, Honza Bambas wrote:
In the W3C spec for localStorage
http://dev.w3.org/html5/webstorage/#the-localstorage-attribute is said
to present it (the persistent storage) the same way as cookies.
There were
*Please, keep this on topic. There's no point to rehashing
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-April/019238.htmlor
any of the other similar debates on private browsing and
localStorage's
persistence guarantees.*
When in private browsing mode, WebKit should not write any data
In HTML5, HTML elements in text/html are put in the XHTML namespace and
text/html might contain SVG or MathML elements, so you probably want to
conditionally call getElementsByTagNameNS based on e.g. the root element's
namespaceURI rather than the document's HTMLness.
I think the major
I haven't made any changes to the spec based on the feedback below. Let me
know if there's anything I missed. I'm not aware of any specific problems
at this time.
On Sat, 11 Apr 2009, Øistein E. Andersen wrote:
On 22 May 2008, at 12:40, Ian Hickson wrote:
Do you have input on the EUC-JP
On Sun, 12 Apr 2009, Øistein E. Andersen wrote:
On 2 Sep 2008, at 06:06, Ian Hickson wrote:
On Wed, 30 Jul 2008, Øistein E. Andersen wrote:
1. Opera, Firefox and Safari all handle US-ASCII as Windows-1252.
IE7, on the other hand, simply ignores the high bit (as it does for
On Tue, 14 Apr 2009, Øistein E. Andersen wrote:
This e-mail is an attempt to give a relatively concise yet reasonably complete
overview of non-Unicode character sets and encodings for `Chinese characters',
excluding those which are not supported by at least one of the four browsers
IE,
On Sun, 12 Apr 2009, Nelson B Bolyard wrote:
Yngve Nysaeter Pettersen wrote:
The default format, introduced by Netscape, is the SPKAC format, see
the above link, and includes the public key and the Keygen challenge
attribute, and is signed by the private key.
The actual standardized
On Mon, 13 Apr 2009, Markus Ernst wrote:
I found a message in the list archives from July 2004, where Ian
announced to put nested optgroups back into the spec:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2004-July/001200.html
Anyway in the current spec, the optgroup element is not
The ImageData APIs already provide the ability to do this and are
already supported by Firefox, Opera and Safari.
Given the ImageData APIs, and given that they are generally more efficient
at the typical use cases for getPixel/setPixel, I haven't added getPixel/
setPixel to the spec.
Cheers,
On Tue, 14 Apr 2009, Patrick Mueller wrote:
The last paragraph in section 4.6 of the Web Storage draft (10 April
2009), mentions a native ordered dictionary data type. The URL to the
section in the draft is here:
http://dev.w3.org/html5/webstorage/#database-query-results
This is the
On Thu, 4 Jun 2009, João Eiras wrote:
The opera-2dgame context also has APIs for collision detection and control
painting
http://my.opera.com/WebApplications/blog/show.dml/200788
I'm not familiar with the current canvas spec, but are these features
supported somehow? Or would they have the
On Wed, 15 Apr 2009, Anders Rundgren wrote:
Now to the really problematic stuff: keygen is not really an HTML
tag, it is actually 2 phases of a 3-phase key provisioning protocol.
I don't see why a protocol should be plugged into a page GUI. The
alternatives all use APIs or specific
On Thu, 16 Apr 2009, �istein E. Andersen wrote:
Currently, only a limited set of vulgar fractions can be expressed in
HTML, viz, those that exist as pre-composed characters in Unicode.
(For example, 16ths and 32nds, which are often used with imperial units,
are not included.) This can be
On Fri, 17 Apr 2009, Nils Dagsson Moskopp wrote:
I am unsure on what scope the current document should have in
subsection 5.11.3.9 (Link type license) of the spec and how it
functions (or should play) together with sectioning.
Let us consider this example, a creative-commons-licensed
João Eiras wrote:
I think the major advantage of document.contentType is to know the value
of the Content-Type header (without charset) sent by the server.
That's not what document.contentType returns in Gecko, though...
(especially if the server-sent value was empty, or didn't parse as a
Ian Hickson wrote:
On Mon, 13 Apr 2009, Markus Ernst wrote:
I found a message in the list archives from July 2004, where Ian
announced to put nested optgroups back into the spec:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2004-July/001200.html
Anyway in the current spec, the
On Wed, Jun 3, 2009 at 3:53 PM, Ian Hickson i...@hixie.ch wrote:
Since HTML5 supports MathML natively now, it seems that MathML is the
solution to use here.
Actually, it seems to me that the best solution is for browsers to
support the unicode fraction slash [U+2044], unless that has too bad
In current-work, section 4.6.6, there is this explanation of the small
element:
Small print is typically legalese describing disclaimers, caveats,
legal restrictions, or copyrights. Small print is also sometimes used
for attribution.
This paragraph should be removed. Please do not advocate,
The cite element should be slightly changed. Under this proposal, the
cite element should be used only for titles of works, but may be used
for other things that web authors may wish to cite. This conforms with
how the cite element is used in practice.
In the current HTML 5 specification, the
48 matches
Mail list logo
