Hi Ian,
Thank you for taking the time to follow up. Some of my comments do seem a
little immature in hindsight and I tend to agree now that adding a lot of these
suggestions to the HTML spec. would make little difference.
I am exploring options to reduce the potential for UA state leaks
On Thu, Oct 18, 2012 at 4:16 PM, Glenn Maynard gl...@zewt.org wrote:
On Thu, Oct 18, 2012 at 3:54 AM, Anne van Kesteren ann...@annevk.nl wrote:
* TextDecoder.decode()'s view argument is no longer optional. Why should
it be?
It buffers the EOF byte when in streaming mode, eg. when the last
If it is really necessary to support this case then perhaps both the image
width and the
the native pixel breakpoints could be specified in the srcset.
Then srcset=low.jpg 10w 20w, hi.jpg 20w 40w, huge.jpg 30w would mean:
low.jpg is 10 pixels wide and use it if the native pixel width of the
Hi Mat,
have taken your advice and made an initial draft of a use case/rationale
document:
http://www.w3.org/html/wg/wiki/User:Sfaulkne/main-usecases#Introduction
feedback welcome!
regards
SteveF
On 18 October 2012 22:27, Mathew Marquis m...@matmarquis.com wrote:
On Oct 18, 2012, at 2:36
On Fri, Oct 19, 2012 at 1:50 PM, A. Rauschenbach rauschenb...@annuo.de wrote:
I'm sick of coping the checksum of important files by hand or QR-code to the
download manager or console.
To solve the problem I suggest a checksum attribute in the a href tag.
example: a
A. Rauschenbach rauschenb...@annuo.de schrieb am Fri, 19 Oct 2012
13:50:04 +0200:
I'm sick of coping the checksum of important files by hand or QR-code
to the download manager or console.
To solve the problem I suggest a checksum attribute in the a href
tag.
It seems that problem is
Am 2012-10-19 14:01, schrieb Nils Dagsson Moskopp:
It seems that problem is solved at the HTTP level with RFC 1864:
http://tools.ietf.org/html/rfc1864
If I get it right this works fine if you serve it from your server, but
not if you link to foreign server.
Another advantage is that your
If you serve important files over HTTP without TLS I don't think a
checksum is going to help anyone much.
With important I meant the file as to work right here and right now not
any security issues.
On Thu, Oct 18, 2012 at 1:49 AM, Anne van Kesteren ann...@annevk.nl wrote:
I added the API to the Encoding Standard:
http://encoding.spec.whatwg.org/#api
Feedback welcome. I suppose we might want to write an introduction for it
too.
Thanks, Anne! Excellent cleanup, too.
On Thu, Oct
On Fri, 19 Oct 2012, Jukka K. Korpela wrote:
Are there any situations that this doesn't handle where it would be
legitimate to omit a title element?
Perhaps the simplest case is an HTML document that is only meant to be
displayed inside an inline frame and containing, say, just a
On Fri, 19 Oct 2012, A. Rauschenbach wrote:
I'm sick of coping the checksum of important files by hand or QR-code to
the download manager or console.
To solve the problem I suggest a checksum attribute in the a href tag.
example: a href=http://example.com/important.file;
2012-10-19 19:33, Ian Hickson wrote:
On Fri, 19 Oct 2012, Jukka K. Korpela wrote:
Are there any situations that this doesn't handle where it would be
legitimate to omit a title element?
Perhaps the simplest case is an HTML document that is only meant to be
displayed inside an inline frame
On Fri, 19 Oct 2012, Jukka K. Korpela wrote:
2012-10-19 19:33, Ian Hickson wrote:
On Fri, 19 Oct 2012, Jukka K. Korpela wrote:
Are there any situations that this doesn't handle where it would
be legitimate to omit a title element?
Perhaps the simplest case is an HTML
Am 2012-10-19 18:49, schrieb Ian Hickson:
What is the attack scenario you are trying to avoid?
Without a discussion of what problem you're trying to solve, it's
unclear
how to evaluate the proposal.
The idea of a hash= or checksum= attribute on a href has come
up
before -- about once a
On Fri, Oct 19, 2012 at 11:46 AM, A. Rauschenbach rauschenb...@annuo.de wrote:
Am 2012-10-19 18:49, schrieb Ian Hickson:
What is the attack scenario you are trying to avoid?
Without a discussion of what problem you're trying to solve, it's unclear
how to evaluate the proposal.
The idea of a
On Fri, 19 Oct 2012, A. Rauschenbach wrote:
If I write an article and link to other documents I want a solution that
the visitor can be sure that the document he opens is the document I
originally linked to. (And if its not he gets informed. So he knows that
the information maybe differ
A. Rauschenbach rauschenb...@annuo.de schrieb am Fri, 19 Oct 2012
20:46:24 +0200:
[…]
If I write an article and link to other documents I want a solution
that the visitor can be sure that the document he opens is the
document I originally linked to.
Mirror the information.
--
Nils
Jukka K. Korpela jkorp...@cs.tut.fi schrieb am Fri, 19 Oct 2012
20:49:16 +0300:
Anyone who bookmarks a document that was not meant to be bookmarked
should accept the consequences.
What makes the web – and collaboration between entities in general –
tremendously useful is that information can
I was working on a bug [1][2] recently where authors had complained
about WebKit's behavior where clicking a scrollbar unfocuses the
activeElement. What's particularly quirky is that the window scrollbar
never moves focus in any browser I tried, but overflow scrollbars
inside the page *do* move
On Fri, 19 Oct 2012, Elliott Sprehn wrote:
I was working on a bug recently where authors had complained about
WebKit's behavior where clicking a scrollbar unfocuses the
activeElement. What's particularly quirky is that the window scrollbar
never moves focus in any browser I tried, but
On Fri, Oct 19, 2012 at 3:34 PM, Elliott Sprehn espr...@gmail.com wrote:
I was working on a bug [1][2] recently where authors had complained
about WebKit's behavior where clicking a scrollbar unfocuses the
activeElement. What's particularly quirky is that the window scrollbar
never moves focus
Hi folk,
Proposal: new table Boolean attribute named hassum.
It was bring to my attention of a possible backward compatibility
issue in regards of the interpretation of having multiple subsequent
group in a table.
The issue:
Sometime the subsequent row grouping under the same data level and the
22 matches
Mail list logo
