2009/2/11 Robert O'Callahan rob...@ocallahan.org:
So, how about adding an autobuffer attribute, which instructs the browser
that the user
will probably play the video and as much data as possible should be
pre-downloaded?
By default (when the attribute is not present) the browser would be
The discussion on spellcheck= focused on two ideas; using spellcheck=
mostly as specced here:
http://damowmow.com/playground/spellcheck.txt
...and doing something with lang=. The idea of using lang= had
problems that were pointed out by several people, most notably, the issue
that the
Regarding http://html5.org/tools/web-apps-tracker?from=2800to=2801, my
requests:
1. Change the literals true/false to on/off, leaving the DOM values
Boolean.
2. Check the spelling of the passage (asits!) :0)
3. Say that the default behavior for BODY is on and the default behavior
for
Kristof Zelechovski wrote on 2/12/2009 6:24 AM:
Stretching it a bit, a user's language always matches the site's,
otherwise the user would not be able to submit to the site anything
that makes sense, except when the site is a gateway for submissions
to an uninvolved third party in which
The server has two ways of knowing the user's preferred language: the user's
preferences and the browser settings, in that order.
Submitting in two languages usually needs two controls, one for English and
one for German, with appropriate markup. The server must be prepared to
handle this use
On Thu, Feb 12, 2009 at 8:57 AM, Kristof Zelechovski
giecr...@stegny.2a.pl wrote:
The server has two ways of knowing the user's preferred language: the user's
preferences and the browser settings, in that order.
Both of which are often wrong. Users may be multilingual, and
multiple users may
The language attribute can be changed at run time if needed. It requires an
additional event that can be called langmismatch. Of course, a more
traditional selector is also a solution. If the site is primary English,
with Hebrew fragments here and there, it is not much harm that the fragments
On Wed, 11 Feb 2009 15:03:01 -0800, Darin Adler da...@apple.com wrote:
On Feb 11, 2009, at 12:14 PM, Kartikaya Gupta wrote:
I updated to Safari 3.2 on Windows (which looks it also has WebKit
525.27.1) and you're right, it is now showing number instead of
object. I guess this was
On Thu, 12 Feb 2009 07:03:22 +0100, Simon Pieters sim...@opera.com wrote:
On Wed, 11 Feb 2009 21:14:44 +0100, Kartikaya Gupta
lists.weba...@stakface.com wrote:
I updated to Safari 3.2 on Windows (which looks it also has WebKit
525.27.1) and you're right, it is now showing number
On Thu, 12 Feb 2009 16:12:49 +0100, Kartikaya Gupta
lists.weba...@stakface.com wrote:
It seems to me the simplest approach would be to bind DOMTimeStamp to a
number for ECMAScript (the typedef should then make it unnecessary to
explicitly define in WebIDL), and create a new type to
2009/2/11 Ian Hickson i...@hixie.ch
[...]
2) you depend on css3-ui, in CR stage, instead of becss, a very
early WD
BECSS is actually probably more stable than CSS3 UI at this point.
Why do you say so? Will CSS3 UI go back to Last Call or BECSS process to
Last Call in the
Kristof Zelechovski wrote on 2/12/2009 9:05 AM:
Markup for German AND English submissions at the same time, as per your
request:
LABEL LANG=de Inhalt: TEXTAREA NAME=INHALT /TEXTAREA /LABEL
LABEL LANG=de Contents: TEXTAREA NAME=CONTENTS /TEXTAREA /LABEL
In my case, we have a single field,
Having interjected words marked as spelling errors is not a failure. The same
phenomenon occurs with proper names and you cannot help that.
The UI you described is inconsistent and it should be fixed. The control for
German should be labeled Fehlerbeſchreibung or whatever.
Best regards,
Chris
Either I am rather confused or there are some misunderstandings still.
Some observations:
Ian Hickson wrote:
Having them be orthogonal is far more useful to authors. For example,
imagine the following stylesheet:
And
I've made HTML5 say that :read-write doesn't apply to disabled
Garrett Smith wrote:
I would be fine with a way to flag scripts with that information, though
there is a catch-22: if you flag such a script and it DOES depend on style
information, then existing UAs will get it right and any UA implementing
the new spec will get it wrong.
If the page does
Křištof Želechovski wrote on 2/12/2009 10:15 AM:
The UI you described is inconsistent and it should be fixed.
Inconsistent with which UI standard?
- Bil
I do not know much about UI standards but the rule that the answer should be
formulated in the language of the question is rather straightforward. It is
just common sense. Exceptions are questions like How is that in German?.
Chris
On Feb 12, 2009, at 7:08 AM, Kartikaya Gupta wrote:
Latest version of Chrome is still giving me a Date object. I don't
know what version of WebKit it's using.
Chrome uses an entirely different JavaScript binding, not the standard
WebKit one, so I'm not surprised that it’s exhibiting
Kristof Zelechovski wrote on 2/12/2009 11:06 AM:
I do not know much about UI standards but the rule that the answer should be
formulated in the language of the question is rather straightforward. It is
just common sense. Exceptions are questions like How is that in German?.
No one can
2009/2/11 Ian Hickson i...@hixie.ch:
On Wed, 11 Feb 2009, David Gerard wrote:
Think of tag-soupness as a feature, not a bug. Shudder in horror at what
this implies.
I don't think that's a particularly controversial position here. People in
other mailing lists involved in the development of
The majority of users will answer the question in the language of the
question, this is the normal reaction. Of course there is no guarantee but
the odds of getting the expected result are high. Assuming that the user's
input will actually be read by somebody, providing proper markup will help
* Kartikaya Gupta wrote:
DOM 3 Core says this about DOMTimeStamp:
For Java, DOMTimeStamp is bound to the long type. For ECMAScript,
DOMTimeStamp
is bound to the Date type because the range of the integer type is too small.
The former WebAPI working group discussed this issue and found that
Ian Hickson wrote:
On Wed, 11 Feb 2009, fantasai wrote:
Given the state of current implementations and the fact that hidden input
elements do have distinct enabled and disabled states, I don't understand
the reasoning behind this change.
http://twitter.com/WHATWG/status/1198455588
The idea
On Thu, 12 Feb 2009 06:55:18 + (UTC), Ian Hickson i...@hixie.ch wrote:
Could you reannotate the above but with the script nesting level
explicitly given at each step?
Below is an updated annotation including all the script nesting level and
parser pause flag changes.
(Original
On Thu, Feb 12, 2009 at 10:13 PM, timeless timel...@gmail.com wrote:
2009/2/11 Robert O'Callahan rob...@ocallahan.org:
So, how about adding an autobuffer attribute, which instructs the
browser that the user
will probably play the video and as much data as possible should be
pre-downloaded?
On Fri, 23 Jan 2009, Mynthon wrote:
I have some questions about html. I really like new section / tag and
its possibility to have its own hx / structure. Dont like mixing hx
/ levels but thats BTW.
I have strange feeling that in next 5 years not only blogs will be
available on the web
On Thu, 29 Jan 2009, Michael Nordman wrote:
Note that the document-is-markup flag will likely go away, and be
replaced by just checking to see if there is a manifest (as it was
before).
The reason this particular thing might change is that I checked it in
yesterday and this
On Fri, 30 Jan 2009, Alexey Proskuryakov wrote:
I've noticed that swapCache() now raises an exception if the cache's
application cache group is marked as obsolete. Previously, this resulted
in the document being unassociated from the cache.
Why such a change? It seems arbitrary - the
On Sat, 31 Jan 2009, Boris Zbarsky wrote:
Ian Hickson wrote:
I haven't mentioned the 'this' behavior, so right now |this !===
window|, which breaks the invariant that there is no way to actually
get hold of a reference to the Window object itself (as opposed to the
outer WindowProxy
On Mon, 2 Feb 2009, Lachlan Hunt wrote:
The spec defines the semi-transparent content model, but this is no
longer used for any elements. Please remove this from the spec.
http://www.whatwg.org/specs/web-apps/current-work/#transparent-content-models
Done.
--
Ian Hickson
On Tue, 3 Feb 2009, Philipp Kempgen wrote:
---cut---
5.12.3.7 Link type help
The help keyword may be used with link, a, and area elements.
For link elements, it creates a hyperlink.
---cut---
Shouldn't that read For *a* elements, it creates a hyperlink.?
On Tue, 3 Feb 2009, Giovanni
On Wed, 4 Feb 2009, Lachlan Hunt wrote:
You can do this in HTML5, using figure and legend:
figure
legendA header for the list/legend
ul
liList item/li
liList item/li
liList item/li
/ul
/figure
Since figure is a sectioning root, a heading
On Thu, Feb 12, 2009 at 7:15 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 31 Jan 2009, Boris Zbarsky wrote:
Ian Hickson wrote:
I haven't mentioned the 'this' behavior, so right now |this !===
window|, which breaks the invariant that there is no way to actually
get hold of a reference to
33 matches
Mail list logo
