Jeremy Orlow wrote:
Btw, I thought I'd just point out that the proposal mentions this case:
"From the proposal text: "All pages connected to the same Global Script
should run on the same thread, in the same process. Since this is not
always technically possible, it should be legal (and not break
Justin Lebar wrote:
> [...]
> Notably unsupported by this API is support for pages altering their
> saved state. For instance, a page might want to save a text box's
> edit history to implement a fancy undo.
> [...]
> We'd probably want to fire PopState on all loads and history
> navigations, sinc
Max wrote:
Having used the web for the past 15 years I've always felt that it's
a shame when you run into a page with a set of measurements and
those can't be interpreted automatically in a sensible fashion.
Especially with the fact that there are both imperial and metric
units still aroun
This looks interesting.
Dmitry Titov wrote:
A web page will be able to create a Global Script and connect to it, as in
this example:
var context = new GlobalScript(); // perhaps 'webkitGlobalScript' as
experimental feature?
context.onload = function () {...}
context.onerror = function () {...
Jeremy Keith wrote:
> Unit-measures differ from locale to locale (e.g. Fahrenheit vs. Celsius,
> pound versus Kilogram), making comparison and matching of offerings
> difficult.
There's more variation than that: (imperial) gallon v. (US) gallon.
Cases like that really make it hard to deal with.
I'm drifting into writing code for the pattern attribute on text
fields again, and I wondered: if text inputs can have pattern
attribute for regular expression matching, why not text area elements?
The HTML 5 spec says: "The textarea element represents a multiline
plain text edit control for the
Alex Vincent wrote:
I'm drifting into writing code for the pattern attribute on text
fields again, and I wondered: if text inputs can have pattern
attribute for regular expression matching, why not text area elements?
What's the use-case for it? Textareas are almost always for such large
amou
On Wed, Aug 19, 2009 at 11:32 AM, Geoffrey Sneddon wrote:
> What's the use-case for it? Textareas are almost always for such large
> amounts of input that they are almost always free-form text. Why allow the
> pattern attribute?
You could impose a minimum character length for posts -- that's commo
On Wed, Aug 19, 2009 at 7:37 AM, Patrick Mueller wrote:
> var context = new GlobalScript(); // perhaps 'webkitGlobalScript' as
>> experimental feature?
>> context.onload = function () {...}
>> context.onerror = function () {...}
>> context.load('foo.js');
>>
>
> Presumably this script is being lo
On Wed, Aug 19, 2009 at 10:48 AM, Dmitry Titov wrote:
> On Wed, Aug 19, 2009 at 7:37 AM, Patrick Mueller
> wrote:
>
>> var context = new GlobalScript(); // perhaps 'webkitGlobalScript' as
>>> experimental feature?
>>> context.onload = function () {...}
>>> context.onerror = function () {...}
>>
On Tue, Aug 18, 2009 at 8:26 PM, Jonas Sicking wrote:
> On Tue, Aug 18, 2009 at 7:53 PM, Drew Wilson wrote:
> > An alternative would be to make the "name" parameter optional, where
> > omitting the name would create an unnamed worker that is
> identified/shared
> > only by its url.
> > So pages w
On Wed, Aug 19, 2009 at 8:32 AM, Geoffrey Sneddon wrote:
> Alex Vincent wrote:
>>
>> I'm drifting into writing code for the pattern attribute on text
>> fields again, and I wondered: if text inputs can have pattern
>> attribute for regular expression matching, why not text area elements?
>
> What'
Patrick Mueller wrote:
> Or perhaps these GlobalScripts - should really be called
> GlobalObjects or GlobalContexts maybe; SharedScope?
I like "Shared" as this is the term used in SharedWorkers
to identify something that can be shared between multiple
pages. SharedContext?
Best regards
Mike
2009/8/19 Jonas Sicking :
> So for the pattern attribute, a use case would be on a site that
> accepts US addresses (for example a store that only ships within the
> US), the site could use a textarea together with a pattern that
> matches US addresses.
That would be a most unusual scenario IMO:
On Wed, Aug 19, 2009 at 2:38 PM, Jonas Sicking wrote:
> So for the pattern attribute, a use case would be on a site that
> accepts US addresses (for example a store that only ships within the
> US), the site could use a textarea together with a pattern that
> matches US addresses.
It's also pretty
Michael Nordman wrote:
I understand the desire for early warning that a page *may* want to utilized
a GlobalScript. A 'hint' could be useful to a multi-process UA. It's not
clear to me that this is what Patrick was referring to... Patrick?
I wasn't thinking as a hint for the browser, but that'
Dmitry Titov wrote:
The return value from a constructor is the Global Script's "global scope
object". It can be used to directly access functions and variables defined
in global scope of the Global Script. While this global scope does not have
'window' or 'document' and does not have visual page
Today every browser implements their own encoding label matching algorithm,
supports their own list of encodings, their own list of encoding label aliases,
and everything sort of works, but not really.
HTML5 solves part of this problem by defining exactly how to identify an
encoding label alias
On Wed, Aug 19, 2009 at 1:34 PM, Patrick Mueller wrote:
> Dmitry Titov wrote:
>
> The return value from a constructor is the Global Script's "global scope
>> object". It can be used to directly access functions and variables defined
>> in global scope of the Global Script. While this global scope
On Wed, 19 Aug 2009 22:47:57 +0200, Anne van Kesteren wrote:
> Today every browser implements their own encoding label matching
> algorithm, supports their own list of encodings, their own list of
> encoding label aliases, and everything sort of works, but not really.
>
> HTML5 solves part of
I just ran into a short but sweet document that I found helpful but that I
had never seen mentioned on this list:
http://wiki.whatwg.org/wiki/How_to_write_a_spec I figured there was enough
of a chance that someone else would find it helpful or others would have
information to contribute that it wa
On Tue, Aug 18, 2009 at 5:04 PM, Justin Lebar wrote:
> I'm in the process of implementing the HTML5 History API
> (History.pushState(), History.clearState(), and the PopState event) in
> Firefox. I'd like to discuss whether the API might benefit from some
> changes. To my knowledge, no other bro
On Tue, Aug 18, 2009 at 5:04 PM, Justin Lebar wrote:
> I'm in the process of implementing the HTML5 History API
> (History.pushState(), History.clearState(), and the PopState event) in
> Firefox. I'd like to discuss whether the API might benefit from some
> changes. To my knowledge, no other brow
Hi,
as per http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-35 ,
in web socket handshake, a client omits the port number if it is 80/443
while
a server omits it if it is 81/815.
Isn't this confusing?
I guess the client side behavior mimics HTTP and hence hard
to be changed. How about
Michael Nordman wrote:
On Wed, Aug 19, 2009 at 1:34 PM, Patrick Mueller wrote:
Can I create additional GlobalScript's from within an existing
GlobalScript?
That's a good question...
(just having fun... oh the tangled web we weave;)
I'm not sure any has thought thru the implications of that,
25 matches
Mail list logo