tScripts in an attempt to load the Yaffle polyfill
doesn't work.
Advice on how to proceed with these issues (filing bugs on the spec
and/or one or more implementations, perhaps?) would be greatly appreciated.
Thanks!
- Sam Ruby
On 12/02/2014 02:22 AM, Jonas Sicking wrote:
On Mon, Dec 1, 2014 at 7:58 PM, Sam Ruby wrote:
On 12/01/2014 10:22 PM, Jonas Sicking wrote:
On Mon, Dec 1, 2014 at 7:11 PM, Domenic Denicola wrote:
What we really need to do is get some popular library or website to take
a
dependency on mobile
On 11/25/2014 03:52 PM, David Walp wrote:
Apologies for being a late comer to the discussion, but here is some feedback
in our implementation. We're looking forward to engaging on these interactions
more proactively in the future.
On Wednesday, October 29, 2014 6:55 PM, Sam Ruby
y analogy, the parsing of http: absolute URLs is solid and unlikely to
change, but determining the origin of file: URLs isn't. Clearly
identifying what parts are widely deployed and unlikely to change vs
those that aren't may be a path forward.
-Boris
- Sam Ruby
On 12/03/2014 10:57 AM, Arthur Barstow wrote:
On 12/3/14 10:42 AM, Sam Ruby wrote:
On 12/02/2014 06:54 PM, cha...@yandex-team.ru wrote:
I'm new to being a W3C Editor, but I did manage to find:
http://www.w3.org/2005/07/pubrules
Besides the above, the following which includes links t
t the pubrules etc sorted in time.
I've left the 2005 process link for now; will update once the CfC completes.
cheers
Chaals
-- Charles McCathie Nevile - web standards - CTO Office, Yandex
cha...@yandex-team.ru - - - Find more at http://yandex.com
- Sam Ruby
/url/webspecs/develop/ isn't
ready yet.
Once it is ready, I plan to sync all documents.
- Sam Ruby
On 12/02/2014 04:37 PM, Sam Ruby wrote:
[offlist]
Oopsie. Note to self: double check cc list before sending emails.
In any case, the suggestion for pull requests applies to everyone.
- Sam Ruby
I notice that you are on GitHub. One thing I encourage you to do is to
directly edit:
https
I'm making the same suggestion to Wendy. I'd love for the end result to
be a truly joint proposal.
- Sam Ruby
On 12/02/2014 10:28 AM, Sam Ruby wrote:
On 12/02/2014 09:23 AM, cha...@yandex-team.ru wrote:
TL;DR: The administrative hold-ups are now all my fault, so I'm sorry
if
es McCathie Nevile - web standards - CTO Office, Yandex
cha...@yandex-team.ru - - - Find more at http://yandex.com
- Sam Ruby
.2014, 04:19, "Sam Ruby" :
On 11/18/2014 03:18 PM, Sam Ruby wrote:
Meanwhile, I'm working to integrate the following first into the
WHATWG version of the spec, and then through the WebApps
process:
http://intertwingly.net/projects/pegurl/url.html
Integration is proceeding, cu
s appropriate.
/ Jo
- Sam Ruby
P.S. Bug reports and/or a github issue opened on this topic would be
appreciated. A pull request would be even better.
From: Jonas Sicking
Sent: 2014-12-01 22:07
To: Sam Ruby
Cc: Webapps WG
Subject: Re: URL Spec WorkMode (was:
On 11/18/2014 03:18 PM, Sam Ruby wrote:
Meanwhile, I'm working to integrate the following first into the WHATWG
version of the spec, and then through the WebApps process:
http://intertwingly.net/projects/pegurl/url.html
Integration is proceeding, current results can be seen here:
://intertwingly.net/projects/pegurl/url.html#discuss
And by all means, don't stop there!
- Sam Ruby
On Wednesday, October 29, 2014 6:55 PM, Sam Ruby
wrote:
Now to get to what I personally am most interested in: identifying
changes to the expected test results, and therefore to the URL
specifi
On 11/18/2014 03:08 PM, Arthur Barstow wrote:
On 11/18/14 3:02 PM, Sam Ruby wrote:
On 11/18/2014 09:51 AM, Arthur Barstow wrote:
Given URL is a joint deliverable between WebApps and TAG, perhaps it
would be helpful if you were a co-Editor. Are you interested in that
role?
Yes.
OK
On 11/18/2014 09:51 AM, Arthur Barstow wrote:
On 10/29/14 9:54 PM, Sam Ruby wrote:
I am willing to help with this effort.
Thanks for this information [1] and sorry for the delayed reply.
Given URL is a joint deliverable between WebApps and TAG, perhaps it
would be helpful if you were a co
On 11/18/2014 09:51 AM, Arthur Barstow wrote:
On 10/29/14 9:54 PM, Sam Ruby wrote:
I am willing to help with this effort.
Thanks for this information [1] and sorry for the delayed reply.
Given URL is a joint deliverable between WebApps and TAG, perhaps it
would be helpful if you were a co
thing along these lines I describe above were
done, the IETF would be open to the idea of errata to RFC3987 and
updating specs to reference URLs.
- Sam Ruby
[1] http://intertwingly.net/projects/pegurl/url.html
[2] https://www.ietf.org/meeting/91/index.html
[3] https://url.spec.whatwg.org/#relative-scheme
caught my eye. Feel free to comment on these, or
any others, or even to propose new tests.
- Sam Ruby
On Fri, Sep 25, 2009 at 5:57 AM, Anne van Kesteren wrote:
> On Fri, 25 Sep 2009 11:38:08 +0200, Sam Ruby wrote:
>>
>> Meanwhile, what we need is concrete bug reports of specific instances
>> where the existing WebIDL description of key interfaces is done in a way
>
ay
that precludes a pure ECMAScript implementation of the function.
- Sam Ruby
Maciej Stachowiak wrote:
On Sep 24, 2009, at 2:16 PM, Sam Ruby wrote:
On Sep 24, 2009, at 11:53 AM, Maciej Stachowiak wrote:
Any TC39 members whose employers can't join could perhaps become Invited
Experts to the W3C Web Applications Working Group, if that facilitates
r
l circumstances, ones that are not likely to
apply in this situation.
- Sam Ruby
hat the this keyword in the global scope
return the global object, but this is not compatible with the security
design prevalent in implementations as specified herein. [ECMA262]
- Sam Ruby
24 matches
Mail list logo
