Hello all
Just one small question
Why Has HTML5 dropped the rev=[1] attribute?
[1] http://www.w3.org/TR/html5-diff/#absent-attributes
Thanks
--
Martin McEvoy
http://weborganics.co.uk/
On Mon, 2008-11-17 at 22:28 -0800, Sander van Zoest wrote:
Depending on how you want to accomplish you can do that with an enum
that defines how to handle the case:
1) do nothing.
2) disproportionately adjust
3) stretch follow by letter-,pillar-,windowbox appropriately.
4) complete fill
Ian Hickson wrote:
On Tue, 18 Nov 2008, Martin McEvoy wrote:
Just one small question
Why Has HTML5 dropped the rev=[1] attribute?
[1] http://www.w3.org/TR/html5-diff/#absent-attributes
We did some studies and found that the attribute was almost never used,
and most of the time, when it was
Thomas Broyer wrote:
On Mon, Nov 17, 2008 at 6:31 PM, [EMAIL PROTECTED] wrote:
Would the sender of that link necessarily know all the formats the URL
provides? Anyway, that's an unrealistic amount of typing -- typically
round here people just copy and paste a URL into an instant message
Hello Ian
Ian Hickson wrote:
On Tue, 18 Nov 2008, Martin McEvoy wrote:
Just one small question
Why Has HTML5 dropped the rev=[1] attribute?
[1] http://www.w3.org/TR/html5-diff/#absent-attributes
We did some studies and found that the attribute was almost never used,
and most of
On Mon, Nov 17, 2008 at 11:33 PM, Robert O'Callahan [EMAIL PROTECTED]wrote:
On Tue, Nov 18, 2008 at 7:28 PM, Sander van Zoest [EMAIL PROTECTED]wrote:
By the way, the pixel-aspect-ratio on video caps in the GStreamer
framework has precisely the same meaning as this attribute, overriding
it
Martin McEvoy writes:
o be precise, the most commonly used value was rev=made, which is
equivalent to rel=author and thus was not a convincing use case.
!! rel-author doesn't mean the same as rev-made eg:
In which cases doesn't it? If A is the author of B then B was made by
A, surely?
Smylers wrote:
Martin McEvoy writes:
o be precise, the most commonly used value was rev=made, which is
equivalent to rel=author and thus was not a convincing use case.
!! rel-author doesn't mean the same as rev-made eg:
In which cases doesn't it? If A is the author of B then B was made by
Smylers wrote:
[EMAIL PROTECTED] writes:
Would the sender of that link necessarily know all the formats the URL
provides? Anyway, that's an unrealistic amount of typing -- typically
round here people just copy and paste a URL into an instant message and
send it without any surrounding text.
Hello...
Smylers wrote:
Martin McEvoy writes:
o be precise, the most commonly used value was rev=made, which is
equivalent to rel=author and thus was not a convincing use case.
!! rel-author doesn't mean the same as rev-made eg:
In which cases doesn't it? If A is the
Hallvord R M Steen wrote:
Sorry, both as an author and as a user I'd prefer this:
a href=http://example.com/report;html report/a
a href=http://example.com/report.pdf;pdf report/a
a href=http://example.com/report.xhtml;xml report/a
- Keep It Simple. For me as an author it's less typing, and for
On Tue, Nov 18, 2008 at 11:52 AM, Mike [EMAIL PROTECTED] wrote:
Thomas Broyer wrote:
On Mon, Nov 17, 2008 at 6:31 PM, [EMAIL PROTECTED] wrote:
- The HTML version of that URL could provide the web page representation
*and* provide links to all the other content types available.
How about
On Tue, Nov 18, 2008 at 4:09 AM, timeless [EMAIL PROTECTED] wrote:
On Tue, Nov 18, 2008 at 3:15 AM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote:
Keep in mind what we're dealing with here.
dumb web authors. check.
This isn't some trivial Javascript timer firing off events at 60Hz.
This is a
Martin McEvoy wrote:
From the real world found here:
http://nfegen.wordpress.com/2008/03/28/micrordformats/
pI read an interesting post recently, a
href=http://internet-apps.blogspot.com/2008/03/so-how-about-using-rdfa-in-microformats.html;
title=Link to Mark Birbeck blog post‘So how about
Smylers wrote:
Dan Brickley writes:
Smylers wrote:
Martin McEvoy writes:
!! rel-author doesn't mean the same as rev-made eg:
In which cases doesn't it? If A is the author of B then B was made by
A, surely?
Then B contributed to the creation of A, yes. Perhaps not on their own.
But we
Dan Brickley wrote:
Without rev, content creators (in every language) will need to go
through this dance, hunting through dictionaries and debating
subtleties, to make sure that they've identified a suitable pair of
words such that { X word1 Y } is true if and only if { Y word1 X }.
Which is
Lachlan Hunt wrote:
Martin McEvoy wrote:
From the real world found here:
http://nfegen.wordpress.com/2008/03/28/micrordformats/
pI read an interesting post recently, a
href=http://internet-apps.blogspot.com/2008/03/so-how-about-using-rdfa-in-microformats.html;
title=Link to Mark Birbeck
Hallvord R M Steen wrote:
It's less typing - Is that serious or are you joking?!
Isn't it? :)
Well sure, but I still don't know if that was a joke or whether it was a
serious point!
A bit of both. It's not an important point by any means, though I
think less verbosity
Martin McEvoy wrote:
Lachlan Hunt wrote:
Martin McEvoy wrote:
From the real world found here:
http://nfegen.wordpress.com/2008/03/28/micrordformats/
a rev=reply
href=http://internet-apps.blogspot.com/2008/03/so-how-about-using-rdfa-in-microformats.html;
title=Link to Mark Birbeck blog
Mike wrote:
The benefits? Oh I don't know.. a markup language that supports the
transfer protocol it runs on?!
Who says you have to serve HTML over HTTP? I see it served via email
(and newsgroups), local filesystems, and FTP on a regular basis. Indeed,
making HTML depend on HTTP-specific
Joshua Cranmer wrote:
Mike wrote:
The benefits? Oh I don't know.. a markup language that supports the
transfer protocol it runs on?!
Who says you have to serve HTML over HTTP? I see it served via email
(and newsgroups), local filesystems, and FTP on a regular basis.
Indeed, making HTML depend
on 18.11.2008 06:43, Ian Hickson at [EMAIL PROTECTED] wrote:
I'd be more that happy with a separate interface if the objects actually
behaved differently. One example of a good reason to have separate
interfaces was recently proposed here: shared workers should outlive
their creators. This is
Robert O'Rourke wrote:
Martin McEvoy wrote:
Lachlan Hunt wrote:
Martin McEvoy wrote:
From the real world found here:
http://nfegen.wordpress.com/2008/03/28/micrordformats/
a rev=reply
href=http://internet-apps.blogspot.com/2008/03/so-how-about-using-rdfa-in-microformats.html;
title=Link
Martin McEvoy wrote:
Robert O'Rourke wrote:
Hi Martin, hope you're well :)
Hello Rob, nice to hear from you, yes I am well :-)
Glad to hear it!
I don't chirp up that often on this list but I have to agree that
@rev isn't much of a loss. Perhaps for the above example rel=source
or
On Tue, 18 Nov 2008, Martin McEvoy wrote:
We did some studies and found that the attribute was almost never
used, and most of the time, when it was used, it was a typo where
someone meant to write rel= but wrote rev=. To be precise, the
most commonly used value was rev=made, which is
On 18 Nov 2008, at 16:41, Joshua Cranmer wrote:
(and if you retort XMLHTTPRequest, let me point out that I
personally would have objected to injecting HTTP specifics into that
interface, had I been around during the design phases)
XMLHttpRequest doesn't need to be XML, it doesn't need to
On Nov 18, 2008, at 16:54, Dan Brickley wrote:
Yes, 'software' was a bad example. But Dublin Core certainly did
abandon the early term 'author' in favour of 'creator' after a
workshop looking at requirements around images, museum artifacts and
so on.
We can still define that the HTML
On Mon, Nov 17, 2008 at 8:05 PM, Ian Hickson [EMAIL PROTECTED] wrote:
Based on this and other offline feedback (no pun intended), I've changed
the spec to make iframes never inherit the manifest.
Seems workable... of course until app developers actually start trying to
use this system, the
Pages communicate with their workers (dedicated) via queue of
eventshttp://www.whatwg.org/specs/web-workers/current-work/#the-queue
.
What happens if the queue gets more and more events queued (as a result of
postMessage or timer callbacks) and the worker thread does not consume them
fast enough?
On Wed, Nov 19, 2008 at 2:08 PM, Dmitry Titov [EMAIL PROTECTED] wrote:
Pages communicate with their workers (dedicated) via queue of
eventshttp://www.whatwg.org/specs/web-workers/current-work/#the-queue .
What happens if the queue gets more and more events queued (as a result of
postMessage
On Fri, Oct 17, 2008 at 5:36 PM, Ian Hickson [EMAIL PROTECTED] wrote:
- I know you added the behavior of failing loads when a URL is not in
the manifest based on something I said, but now that I read it, it feels
a bit draconian. I wish that developers could somehow easily control the
It does seem like OOM indeed but it may be different because with multiple
threads it's much easier to get into effects like this, you don't need to
allocate a lot of objects.For example, lets say there is something like
this:
function computeStuff() { ... } // takes 100ms to compute stuff
On Wed, Nov 19, 2008 at 4:44 PM, Dmitry Titov [EMAIL PROTECTED] wrote:
It does seem like OOM indeed but it may be different because with multiple
threads it's much easier to get into effects like this, you don't need to
allocate a lot of objects.
You're not allocating JS objects but you are
Ok, it makes sense for OOM to treat it as other OOM cases.
If I may ask your opinion about related thing: SharedWorkers potentially
would run cross-process. IPC can stop/stuck for many reasons, taret process
can die in the midflight (killed by the user from TaskManager for example).
I guess in
On Tue, Nov 18, 2008 at 10:09 PM, Dmitry Titov [EMAIL PROTECTED] wrote:
Ok, it makes sense for OOM to treat it as other OOM cases.
If I may ask your opinion about related thing: SharedWorkers potentially
would run cross-process. IPC can stop/stuck for many reasons, taret process
can die in the
Aaron Boodman wrote:
On Tue, Nov 18, 2008 at 10:09 PM, Dmitry Titov [EMAIL PROTECTED] wrote:
Ok, it makes sense for OOM to treat it as other OOM cases.
If I may ask your opinion about related thing: SharedWorkers potentially
would run cross-process. IPC can stop/stuck for many reasons, taret
36 matches
Mail list logo