Re: [whatwg] Author control over media preloading/buffering

On Tue, Feb 24, 2009 at 12:16 AM, Ian Hickson wrote: > On Wed, 11 Feb 2009, Robert O'Callahan wrote:> 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

Re: [whatwg] Dates and coordinates in HTML5

I think the problem with ISO-8601(:2004?) is that while it is precise, total support requires a large code footprint and effort (durations, intervals, compressed formats and so on). I seem to remember that there is some kind of conflict with something in Javascript regarding years that are repres

Re: [whatwg] Dates and coordinates in HTML5

On Tue, Feb 24, 2009 at 6:01 PM, Andy Mabbett wrote: > What's the expected end-of-life date for HTML5? Do we really want to > hamstring ourselves 'til then, by considering only current, as-of-2009, > capabilities? HTML5 is not supposed to have an end-of-life. It's meant to be forward-compatible,

[whatwg] Media load algorithm feedback

I'm updating the new load algorithm for Firefox's implementation, I've got some feedback on the recent changes to the load algorithm. I think the changes are sensible. It wasn't immediately obvious at first, but after thinking through them, I see the logic behind them. We now have three thin

Re: [whatwg] Dates and coordinates in HTML5

In message <619d9f095a7941eebcbb05fd4b03f...@pirate>, WeBMartians writes Although it can be argued that a standard should not consider the work required for implementation, many of the trade-offs in reference to times and dates do indeed take the present state of code into consideration. W

Re: [whatwg] Dates and coordinates in HTML5

At 13:59 -0500 24/02/09, WeBMartians wrote: It's back! It won't die! :-) Although it can be argued that a standard should not consider the work required for implementation, many of the trade-offs in reference to times and dates do indeed take the present state of code into consideration. O

Re: [whatwg] Dates and coordinates in HTML5

It's back! It won't die! :-) Although it can be argued that a standard should not consider the work required for implementation, many of the trade-offs in reference to times and dates do indeed take the present state of code into consideration. One reason for not supporting BCE is a disagreemen

Re: [whatwg] Dates and coordinates in HTML5

In message <49a3e9b9.4090...@lachy.id.au>, Lachlan Hunt writes >Andy Mabbett wrote: >> It seems to me that there are several outstanding, and overlapping, >>issues for in HTML5, which include use-cases, imprecise dates, >>Gregorian vs. non-Gregorian dates and BCE (aka “BC“) dates. > >The time el

Re: [whatwg] Dates and coordinates in HTML5

Andy Mabbett wrote: It seems to me that there are several outstanding, and overlapping, issues for in HTML5, which include use-cases, imprecise dates, Gregorian vs. non-Gregorian dates and BCE (aka “BC“) dates. The time element was primarily designed to address use cases involving contempora

Re: [whatwg] form markup

Well, suppose a personal information fillout form, i.e.: first name, last name, initials, street, number, postal code, city fields. Things that belong to a "set" (personal information), which is usually an argument to use a list (being ol, ul or dl) for markup. While I value your personal pref

Re: [whatwg] legacy charset support for XML

On Tue, 24 Feb 2009, Křištof Želechovski wrote: > > The sniffing draft > in > sufficiently prescribes what happens if MIME content type is specified as > text/xml; charset=ISO-8859-2. MSIE 7 refuses to render documents like >

Re: [whatwg] form markup

On Tue, 24 Feb 2009, Rikkert Koppes wrote: > > There are various ways to forms are beining marked up, to name a few > 1. use a table, put labels and inputs in cells > 2. use a dl, put labels in dt, put inputs in dd > 3. use p elements to surround label and input pairs > 4. use an ol element, let li

[whatwg] legacy charset support for XML

The sniffing draft in sufficiently prescribes what happens if MIME content type is specified as text/xml; charset=ISO-8859-2. MSIE 7 refuses to render documents like unless the encoding is spe

[whatwg] form markup

There are various ways to forms are beining marked up, to name a few 1. use a table, put labels and inputs in cells 2. use a dl, put labels in dt, put inputs in dd 3. use p elements to surround label and input pairs 4. use an ol element, let li surround label and input pairs 5. use an ul element,