On Mon, Jul 13, 2009 at 7:21 AM, Ian Hickson wrote:
On Tue, 16 Jun 2009, Thomas Broyer wrote:
Though, now that HTML5 introduces video and audio, I wonder if
object couldn't be equivalent to those when type of the resource is
some video or sound...
object doesn't expose the video or audio
On Wed, 15 Jul 2009, Thomas Broyer wrote:
On Mon, Jul 13, 2009 at 7:21 AM, Ian Hickson wrote:
On Tue, 16 Jun 2009, Thomas Broyer wrote:
Though, now that HTML5 introduces video and audio, I wonder if
object couldn't be equivalent to those when type of the resource is
some video or
On Wed, 24 Jun 2009, Aryeh Gregor wrote:
On Wed, Jun 24, 2009 at 3:15 AM, Ian Hicksoni...@hixie.ch wrote:
I don't think alternative style sheets are evil; in fact, they seem to be
quite within the architecture of the Web. Surely you don't think that,
e.g., GMail is evil for having the same
On Wed, 15 Jul 2009 10:51:52 +0200, wha...@whatwg.org wrote:
Author: ianh
Date: 2009-07-15 01:51:50 -0700 (Wed, 15 Jul 2009)
New Revision: 3416
Modified:
index
source
Log:
[] (0) Define that document.bgcolor et al don't reflect for frameset.
Modified: source
Seems to be a listing element in 11.2.2 Display types
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#the-css-user-agent-style-sheet-and-presentational-hints
What's that?
--
Hang loose and stay groovy,
Bruce Lawson
Web Evangelist
www.opera.com (work)
Seems to be a listing element in 11.2.2 Display types
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#the-css-user-agent-style-sheet-and-presentational-hints
What's that?
It's an historical element that you shouldn't use.
See
What does IE do in these two examples?
It appears that IE8 has the following behavior:
ol start=+4
start = 4
ol start=H2SO4
start = 1
Test at http://stanford.edu/~jlebar/moz/list.html
-Justin
On Tue, Jul 14, 2009 at 12:43 AM, Jonas Sickingjo...@sicking.cc wrote:
On Thu, Jun 18, 2009
Hi,
I've been running quite a few tests with the Drag and Drop API, and
more recently I was looking at creating an accessible demo of DnD.
Plugging ARIA support wasn't a problem, but keyboard support was a no
goer.
I tried triggering the dragstart event from the keyboard - which was
It seems like an oversight that Javascript can read response headers
off of XHR but not for the current document. So in order to find out
the headers for the current document you would need to make another
request, refetching the current page, to find that out [1].
Use Cases:
Any that
James Ide wrote on 7/13/2009 10:05 PM:
Currently rel=canonical (
http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html)
is not in the allowed set of link types listed at
http://www.whatwg.org/specs/web-apps/current-work/#linkTypes . Looking back
through archived
Jeremy Keith wrote on 7/7/2009 5:32 AM:
Meanwhile, back on the Rel values wiki page...
http://wiki.whatwg.org/wiki/RelExtensions
Can anyone help with either of my questions:
1. Should I change all of the values derived from XFN from proposal
to accepted as they seem to fit this criteria?
Is it possible that the usage of HTTP to obtain a document for rendering and
to obtain a document for XHR would differ sufficiently that the HTTP headers
would differ?
On Wed, Jul 15, 2009 at 12:07 PM, Joseph Pecoraro joepec...@gmail.comwrote:
It seems like an oversight that Javascript can read
Am Dienstag, den 14.07.2009, 08:35 +0200 schrieb Oldřich Vetešník:
Dne Tue, 14 Jul 2009 02:52:22 +0200 Aryeh Gregor
simetrical+...@gmail.com napsal/-a:
Indeed, unless browsers let us style legend any way we want (let's say
like span element), people won't use it (in figures) because it
On Wed, Jul 15, 2009 at 6:07 PM, Nils Dagsson
Moskoppnils-dagsson-mosk...@dieweltistgarnichtso.net wrote:
Where is legend element styling lacking currently ?
The element can't be styled in either Firefox 3.5 or recent WebKit
because, according to my testing, it simply doesn't exist in the DOM.
In 2.4.4.1:
If position is not past the end of input, return to the top of the
step labeled loop in the overall algorithm (that's the step within
which these substeps find themselves).
Why not just go to step 9? In any event this is inconsistent with
2.4.4.2, which says
If position is not past
On Wed, Jul 15, 2009 at 5:13 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
On Wed, Jul 15, 2009 at 6:07 PM, Nils Dagsson
Moskoppnils-dagsson-mosk...@dieweltistgarnichtso.net wrote:
Where is legend element styling lacking currently ?
The element can't be styled in either Firefox 3.5 or
On Wed, Jul 15, 2009 at 6:31 PM, Tab Atkins Jr.jackalm...@gmail.com wrote:
I'm confused by this - what exact FF build did you test in? When I
try it in the current public 3.5, I get legend autowrapping itself
in a fieldset.
On Wed, 15 Jul 2009, Remy Sharp wrote:
I've been running quite a few tests with the Drag and Drop API, and more
recently I was looking at creating an accessible demo of DnD.
Plugging ARIA support wasn't a problem, but keyboard support was a no
goer.
I tried triggering the dragstart
On Sat, 27 Dec 2008, Calogero Alex Baldacchino wrote:
A flying thought: why not thinking also to a further option for
embedding everything in a sort of all-in-one html page generated on
the fly when downloading, making of it a global container for video and
text to be consumed by UAs
On Sat, 27 Dec 2008, Silvia Pfeiffer wrote:
6. Timed text stored in a separate file, which is then fetched and
parsed by the Web page, and which is then rendered by the Web page.
For case 6, while it works for deaf people, we actually create an
accessibility nightmare for blind people
I have a couple questions regarding error handling in HTML 5 workers.
In the spec, it says Whenever a runtime script error occurs in one of the
worker's scripts, if the error did not occur while handling a previous
script error, the user agent must report the error using the
WorkerGlobalScope
A few years ago, Vorbis as a baseline codec for audio was dismissed,
because it was expected that the audio codec agreed upon to be used
with video would also be used with audio. Now that agreement on a
codec for video is out of the question, Vorbis can again be
considered as a baseline codec for
On Wed, Jul 15, 2009 at 7:14 PM, Remco remc...@gmail.com wrote:
A few years ago, Vorbis as a baseline codec for audio was dismissed,
because it was expected that the audio codec agreed upon to be used
with video would also be used with audio. Now that agreement on a
codec for video is out of
On Wed, 15 Jul 2009, Jian Li wrote:
I have a couple questions regarding error handling in HTML 5 workers. In
the spec, it says Whenever a runtime script error occurs in one of the
worker's scripts, if the error did not occur while handling a previous
script error, the user agent must
On Thu, 16 Jul 2009, Remco wrote:
A few years ago, Vorbis as a baseline codec for audio was dismissed,
because it was expected that the audio codec agreed upon to be used with
video would also be used with audio. Now that agreement on a codec
for video is out of the question, Vorbis can
2009/7/16 Adam Shannon ashannon1...@gmail.com:
It has been tried but Apple will not implement it due to hardware
limitations.
Hardware limitations or patent limitations? Either seems ill-matched
to evidence-based reasoning.
What was Apple's issue with Vorbis audio? I'd like to hear from
On Thu, Jul 16, 2009 at 2:16 AM, Adam Shannonashannon1...@gmail.com wrote:
On Wed, Jul 15, 2009 at 7:14 PM, Remco remc...@gmail.com wrote:
A few years ago, Vorbis as a baseline codec for audio was dismissed,
because it was expected that the audio codec agreed upon to be used
with video
There have been a number of discussions about clickjacking,
X-Frame-Options, and other proposals.
Nobody I've spoken to seems especially happy with X-Frame-Options, and
none of the other proposals have yet gotten serious traction.
I have therefore not added anything of this nature to the
On Thu, Jul 16, 2009 at 7:31 AM, Tab Atkins Jr.jackalm...@gmail.com wrote:
On Wed, Jul 15, 2009 at 5:13 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
I'm confused by this - what exact FF build did you test in? When I
try it in the current public 3.5, I get legend autowrapping itself
in a
On Thu, 16 Jul 2009, Remco wrote:
On Thu, Jul 16, 2009 at 2:18 AM, Ian Hicksoni...@hixie.ch wrote:
Given the problem we had with the video codec, I would like to request
that those of you interested in getting a standard audio codec do so
by directly working with the browser vendors to
Vorbis is the best lossy audio codec - Do you have data to back up this
assertion? I am not an expert here, I had the naïve assumption that AAC was
better given that major devices (e.g. iPod) use this format over Vorbis. I
would love to see some data (other than some studies from 2005 on some
On Wed, Jul 15, 2009 at 8:27 PM, Adam Shannonashannon1...@gmail.com wrote:
This was from an email that Ian posted, I do not know if it is directly from
Apple. I am just posting it as reference, you will have to ask Ian to the
source/creditability of the statement.
Apple refuses to implement
2009/7/16 Ian Fette (イアンフェッティ) ife...@google.com:
Vorbis is the best lossy audio codec - Do you have data to back up this
assertion? I am not an expert here, I had the naïve assumption that AAC was
better given that major devices (e.g. iPod) use this format over Vorbis. I
would love to see
2009/7/16 Ian Fette (イアンフェッティ) ife...@google.com:
Widely adopted ... in portable media players? Really? iPod? Zune?
Almost every media player I've purchased from the local electronics
store here in NZ has Vorbis support. Many of them even support Flac.
The notable exception is Apple products.
2009/7/16 Remco remc...@gmail.com:
Cowon/iAudio, iRiver, LG, Samsung, SanDisk, Creative, Google. Those
are a few of the companies that support Vorbis:
http://wiki.xiph.org/PortablePlayers
Also everything using the Actions S1 MP3 chipset - almost *all*
Chinese MP3/MP4 players.
Basically,
On Thu, 19 Feb 2009, Greg Millam wrote:
Here is my proposal: [...]
I think this proposal is a good direction to go in. However, I think it is
still too early to put this in HTML5, and based on the quality of
implementations so far, it will probably still be too early by the time
HTML5 goes
Am Mittwoch, den 03.06.2009, 22:56 + schrieb Ian Hickson:
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
Am Mittwoch, den 15.07.2009, 19:16 -0500 schrieb Adam Shannon:
It has been tried but Apple will not implement it due to hardware
limitations.
As if. I somehow recall that a few years ago, a Linux Distribution on
Ipod did Vorbis (and Doom, incidentally - that was the original reason
for me to
On Wed, Jul 15, 2009 at 5:26 PM, Ian Hicksoni...@hixie.ch wrote:
There have been a number of discussions about clickjacking,
X-Frame-Options, and other proposals.
Nobody I've spoken to seems especially happy with X-Frame-Options, and
none of the other proposals have yet gotten serious
On Thu, 16 Jul 2009, Nils Dagsson Moskopp wrote:
Am Mittwoch, den 03.06.2009, 22:56 + schrieb Ian Hickson:
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
Am Dienstag, den 14.07.2009, 14:46 +0200 schrieb Simon Pieters:
Gecko, WebKit and Opera return true for XHTML/2.0.
Who in the real world actually checks for that ? Wasn't XHTML 2.0 dead
in the snow for some time now ?
Cheers
--
Nils Dagsson Moskopp
http://dieweltistgarnichtso.net
On Wed, Jul 15, 2009 at 9:24 PM, Jonas Sickingjo...@sicking.cc wrote:
Note that Content Security Policies[1] can be used to deal with
clickjacking. So far we've gotten a lot of positive feedback to CSP
and are in progress of implementing it in firefox. So it's a possible
solution to this.
Is
On Wed, Jul 15, 2009 at 9:53 PM, Jeremy Orlowjor...@chromium.org wrote:
Didn't Ian, 2 messages back, suggest that vendors experiment and bring their
results back to the table at a later date? Or has CSP never been discussed
here?
I haven't seen it discussed here, but maybe it has been and I
Am Donnerstag, den 16.07.2009, 01:36 + schrieb Ian Hickson:
On Thu, 16 Jul 2009, Nils Dagsson Moskopp wrote:
Creative Commons suggests using 'about=' in RDFa with 'rel=license'
http://wiki.creativecommons.org/RDFa#Content_discovery
It is an example of RDFa and HTML semantics clashing
On Thu, 16 Jul 2009, Nils Dagsson Moskopp wrote:
http://daten.dieweltistgarnichtso.net/src/cc-license-markup/generator2.xhtml
Wow, sweet!
Aside from english language support, have I missed something obvious
building this license thingy ?
The first image I tried was this one:
On Wed, Jul 15, 2009 at 8:58 PM, Maciej Stachowiakm...@apple.com wrote:
On Jul 14, 2009, at 3:43 AM, Robert O'Callahan wrote:
On Tue, Jul 14, 2009 at 10:42 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Tue, Jul 14, 2009 at 10:34 PM, Jonas Sicking jo...@sicking.cc wrote:
We can do
Am Donnerstag, den 16.07.2009, 04:17 + schrieb Ian Hickson:
The first image I tried was this one:
http://hixie.ch/resources/images/astrophy/200
...which didn't work, but I see now that it is because I was lacking an
extension on the filename.
Well, checking the MIME type seemed
Masataka Yakura wrote:
I'm confused by this - what exact FF build did you test in? When I
try it in the current public 3.5, I get legend autowrapping itself
in a fieldset.
Tab Atkins Jr. wrote:
On the note of legend styling, currently a legend-in-fieldset isn't
handled by the standard CSS renderer *at all* in FF, last I heard
More precisely it's handled as having a special position value that
you can't override, more or less, and that position value forces
Hi Ian,
Great to see the new efforts to move the subtitle/caption/karaoke
issues forward!
I actually have a contract with Mozilla starting this month to help
solve this, so I am more than grateful that you have proposed some
ideas in this space.
On Thu, Jul 16, 2009 at 9:38 AM, Ian
50 matches
Mail list logo
