ISSUE-120
Current Status [1,2] :
We a single change proposal to simplify the HTML+RDFa specification
by removing prefixes.
- We have another change proposal to clarify how prefixes work and
explain that they are optional.
I'd like to propose that HTML/HTML5 uses RDFa as found in the
On 4 February 2011 01:25, Aryeh Gregor simetrical+...@gmail.com wrote:
On Thu, Feb 3, 2011 at 4:41 PM, Boris Zbarsky bzbar...@mit.edu wrote:
And all I'm saying is that there are at least three pieces of data here:
1) innerText return value
2) Selection.toString() return value
3) What the
This must have been brought up before as e.g. http://pukupi.com/post/2070/
is from June 2010, but I could not find anything quickly. Apparently
people are using IDNs and cannot get them validated with email controls
because the specification prohibits this. We should probably change that.
See below for a revised proposal, based on the discussion here. To
move this forward, I understand I must get some people to implement
it. I'll probably eventually get to submitting a Firefox patch. If
anyone reading this list knows the people who'd be able to make this
happen on other browsers,
On 02/04/11 11:55, Anne van Kesteren wrote:
This must have been brought up before as e.g.
http://pukupi.com/post/2070/ is from June 2010, but I could not find
anything quickly. Apparently people are using IDNs and cannot get them
validated with email controls because the specification
On 4 February 2011 11:07, Marijn Haverbeke mari...@gmail.com wrote:
See below for a revised proposal, based on the discussion here. To
move this forward, I understand I must get some people to implement
it. I'll probably eventually get to submitting a Firefox patch. If
anyone reading this list
On Thu, 03 Feb 2011 19:55:21 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
It looks like CSS rgba colors with an alpha value of 0 are serialized as
rgba() with 0 as the alpha value. in at least Gecko, Webkit, and
Presto.
It also looks like canvas style color with an alpha value of 0 are
On 2/3/11 8:25 PM, Aryeh Gregor wrote:
innerText seems like a reasonable place to put such an API, if only
because WebKit already does it. It's not ideal a priori, but by the
consistency standards of the web platform it's not noticeably bad. I
should particularly point out that your typical
On 2/4/11 11:37 AM, Jorge wrote:
Wrt to the note some base64 encoders add newlines or other whitespace to their
output. atob() throws an exception if its input contains characters other than
+/=0-9A-Za-z, so other characters need to be removed before atob() is used for
decoding in
On Fri, Feb 4, 2011 at 11:49 AM, Boris Zbarsky bzbar...@mit.edu wrote:
The problem is that at least some current browsers (which ones?) throw. So
you wouldn't be able to rely on the non-throwing behavior anyway :(
Everyone except Opera throws on invalid characters in atob() input,
and
On Fri, Feb 4, 2011 at 8:37 AM, Jorge jo...@jorgechamorro.com wrote:
Hi,
Wrt to the note some base64 encoders add newlines or other whitespace to
their output. atob() throws an exception if its input contains characters
other than +/=0-9A-Za-z, so other characters need to be removed before
On 04/02/2011, at 17:49, Boris Zbarsky wrote:
On 2/4/11 11:37 AM, Jorge wrote:
Wrt to the note some base64 encoders add newlines or other whitespace to
their output. atob() throws an exception if its input contains characters
other than +/=0-9A-Za-z, so other characters need to be removed
On 04/02/2011, at 18:58, Jonas Sicking wrote:
On Fri, Feb 4, 2011 at 8:37 AM, Jorge jo...@jorgechamorro.com wrote:
Hi,
Wrt to the note some base64 encoders add newlines or other whitespace to
their output. atob() throws an exception if its input contains characters
other than
On Fri, Feb 4, 2011 at 1:19 PM, Jorge jo...@jorgechamorro.com wrote:
On the other hand, it will be so forever
Correct, it will be.
unless the spec says *not* to throw but to skip over instead, so that in a
few years the cleanup can be ~safely skipped.
Nope. The spec isn't going to change
On Fri, 4 Feb 2011, Danny Ayers wrote:
I'd like to propose that HTML/HTML5 uses RDFa as found in the RDFa
specification. This includes the use of namespace prefixes.
To propose ideas for addition to HTML, the starting point here at the
WHATWG is use cases and problem descriptions, not
On 2/4/11 2:59 PM, Aryeh Gregor wrote:
On Fri, Feb 4, 2011 at 10:32 AM, Boris Zbarskybzbar...@mit.edu wrote:
Until they try to use it on a disconnected subtree and it does something
weird, right?
Well, it shouldn't do weird stuff on a disconnected subree. :) It
doesn't in IE.
I thought
On 4 February 2011 20:52, Ian Hickson i...@hixie.ch wrote:
On Fri, 4 Feb 2011, Danny Ayers wrote:
I'd like to propose that HTML/HTML5 uses RDFa as found in the RDFa
specification. This includes the use of namespace prefixes.
To propose ideas for addition to HTML, the starting point here at
On Fri, Feb 4, 2011 at 3:15 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Well, it shouldn't do weird stuff on a disconnected subree. :) It
doesn't in IE.
I thought you said Webkit would refuse to implement that sort of behavior?
I don't think I said that -- I can't speak for WebKit at all.
Hi again,
Just want to wake this thread up and say that I still see CORS as a
good fit for this use case, and I'm curious Jonas about what you think
in light of my previous post?
-Michael
On Mon, Jan 31, 2011 at 6:27 PM, Michael Nordman micha...@google.com wrote:
But... the risk you outline is
Anne van Kesteren:
ImageData.data you mean? I wonder if we can still remove
CanvasPixelArray.
Tab Atkins Jr.:
Only if the out-of-bounds behavior for entries in Typed Arrays matches
the current clamping behavior for CanvasPixelArray. I don't see any
explicit indication of what should be
On Sat, 16 Oct 2010, Samuel Ytterbrink wrote:
*What is the problem you are trying to solve?*
To create sophisticated single file webpages.
That's maybe a bit vaguer than I was hoping for when asking the question. :-)
Why does it have to be a single file? Would multipart MIME be acceptable?
A
On 04/02/2011, at 19:54, Aryeh Gregor wrote:
On Fri, Feb 4, 2011 at 1:19 PM, Jorge jo...@jorgechamorro.com wrote:
unless the spec says *not* to throw but to skip over instead, so that in a
few years the cleanup can be ~safely skipped.
Nope. The spec isn't going to change browser behavior
On Fri, 04 Feb 2011 19:54:56 +0100, Aryeh Gregor
simetrical+...@gmail.com wrote:
On Fri, Feb 4, 2011 at 1:19 PM, Jorge jo...@jorgechamorro.com wrote:
On the other hand, it will be so forever
Correct, it will be.
unless the spec says *not* to throw but to skip over instead, so that
in a
Several folks have asked for a cryptographically strong random number
generator in WebKit. Our first approach was to make Math.random
cryptographically strong, but that approach has two major
disadvantages:
1) It's difficult for a web page to detect whether math.random is
actually
On Fri, Feb 4, 2011 at 6:43 PM, Ian Hickson i...@hixie.ch wrote:
My point is from a black-box perspective, one can never firmly say that
it's not just the browser being slow to start the thread. And we can't
disallow the browser from being slow.
I don't think a black-box test suite can ever
On 2/4/11 7:42 PM, Adam Barth wrote:
interface Crypto {
Float32Array getRandomFloat32Array(in long length);
Uint8Array getRandomUint8Array(in long length);
};
The Uint8Array version is good; let's do that.
For the other, what does it mean to return a random 32-bit float? Is
NaN
On Fri, Feb 4, 2011 at 7:39 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/4/11 7:42 PM, Adam Barth wrote:
interface Crypto {
Float32Array getRandomFloat32Array(in long length);
Uint8Array getRandomUint8Array(in long length);
};
The Uint8Array version is good; let's do that.
For the
Most operating systems provide strong sources of randomness that can
be used to seed cryptographic PRNGs. I'd be inclined to recommend
that folks use that sort of truly random seed.
That sounds good to me.
Given this feedback, we'll probably start off with the Uint8Array version.
Sounds
On Fri, Feb 4, 2011 at 8:01 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Most operating systems provide strong sources of randomness that can
be used to seed cryptographic PRNGs. I'd be inclined to recommend
that folks use that sort of truly random seed.
That sounds good to me.
Given this
On 2/4/11 11:01 PM, Boris Zbarsky wrote:
Sounds like a plan. I'll see about getting this to happen in Gecko too.
One other thing. If we hang this off Crypto, we should expose Crypto in
workers, right?
-Boris
On Fri, Feb 4, 2011 at 8:18 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/4/11 11:01 PM, Boris Zbarsky wrote:
Sounds like a plan. I'll see about getting this to happen in Gecko too.
One other thing. If we hang this off Crypto, we should expose Crypto in
workers, right?
I'm not sure what
Hi,
On Sat, Feb 5, 2011 at 08:42, Adam Barth w...@adambarth.com wrote:
interface Crypto {
Float32Array getRandomFloat32Array(in long length);
Uint8Array getRandomUint8Array(in long length);
};
I think the API would be more flexible and more future-proof defined as :
interface Crypto {
On Fri, Feb 4, 2011 at 9:00 PM, Cedric Vivier cedr...@neonux.com wrote:
Hi,
On Sat, Feb 5, 2011 at 08:42, Adam Barth w...@adambarth.com wrote:
interface Crypto {
Float32Array getRandomFloat32Array(in long length);
Uint8Array getRandomUint8Array(in long length);
};
I think the API would
On 2011-02-05 04:39, Boris Zbarsky wrote:
On 2/4/11 7:42 PM, Adam Barth wrote:
interface Crypto {
Float32Array getRandomFloat32Array(in long length);
Uint8Array getRandomUint8Array(in long length);
};
The Uint8Array version is good; let's do that.
For the other, what does it mean to
34 matches
Mail list logo
