RE: Can we land heycam's WebIDL tests as-is and address review comments following?
Travis, Great. Glad to hear that you are working on the tests. Perhaps you can try Simon' method to make your update in a new branch in w3c/web-platform-tests, so that others can make updates together. Thanks, Zhiqiang From: Travis Leithead [mailto:travis.leith...@microsoft.com] Sent: Monday, December 21, 2015 11:44 PM To: Simon Pieters ; public-webapps ; Zhang, Zhiqiang ; Yves Lafon Subject: RE: Can we land heycam's WebIDL tests as-is and address review comments following? Yves and I have been reviewing these tests and revising them according to recent WebIDL changes and we think they may be ready to be integrated. The updates are in a PR on heycams page. Let's not integrate heycam's original PR until our update is done first please... From: Simon Pieters<mailto:sim...@opera.com> Sent: Monday, December 21, 2015 1:13 AM To: public-webapps<mailto:public-webapps@w3.org>; Zhang, Zhiqiang<mailto:zhiqiang.zh...@intel.com> Subject: Re: Can we land heycam's WebIDL tests as-is and address review comments following? On Mon, 21 Dec 2015 07:34:12 +0100, Zhang, Zhiqiang mailto:zhiqiang.zh...@intel.com>> wrote: > Hi, > > 2+ years ago, heycam submitted WebIDL tests at > > https://github.com/w3c/web-platform-tests/pull/271 > > These tests have been reviewed by several guys but get no update ever > since. > > I wonder if we could land the tests as-is and address the review > comments in further pull requests? Then we can make a test suite to > advance the specification and for people to understand the specification. > > Thoughts? > > Thanks, > Zhiqiang Personally I don't object to that plan, but an alternative is to create a new branch in w3c/web-platform-tests with these changes, and anyone with push access to w3c/web-platform-tests can make changes to that branch, and then we can merge to master when it's ready. git fetch origin refs/pull/271/head:refs/remotes/origin/pr/271 --force git checkout -b webidl-tests origin/pr/271 git push -u origin webidl-tests -- Simon Pieters Opera Software
Can we land heycam's WebIDL tests as-is and address review comments following?
Hi, 2+ years ago, heycam submitted WebIDL tests at https://github.com/w3c/web-platform-tests/pull/271 These tests have been reviewed by several guys but get no update ever since. I wonder if we could land the tests as-is and address the review comments in further pull requests? Then we can make a test suite to advance the specification and for people to understand the specification. Thoughts? Thanks, Zhiqiang
RE: CfC: Moving webstorage to REC 2nd Edition; deadline May 21
> From: Kostiainen, Anssi [mailto:anssi.kostiai...@intel.com] > Sent: Thursday, May 14, 2015 21:16 > To: Arthur Barstow > Cc: public-webapps > Subject: Re: CfC: Moving webstorage to REC 2nd Edition; deadline May 21 > > > On 14 May 2015, at 14:30, Arthur Barstow wrote: > > > > 1. Publish a new WD of the spec and to seek wide review of the spec, per > process 2014. The new WD will be placed in w3.org/TR/webstorage/. > > This addresses the concern and clears the confusion around an outdated /TR. Yes, the spec looks good to me. > > If you have any comments or concerns about this CfC, please reply by May > 21 at the latest. Silence will be considered as agreeing with the proposal and > explicit responses are preferred. If no non-resolvable blocking issues are > raised, this CfC will be considered as passing and we will proceed with this > proposal. > > +1. Thanks for the swift turnaround. I also regenerated an implementation report at http://w3c.github.io/test-results/webstorage/all.html ... for your reference. BTW: I have sent out the above info yesterday, but seems the mailing list system didn't get it. Thanks, Zhiqiang
RE: [eventsource] ACTION-742: Re sse test results, followup on the timeouts with the 2 test facilitators (Web Applications Working Group)
Hi Art,
Sorry for missing this mail thus so late response.
> From: Arthur Barstow [mailto:art.bars...@gmail.com]
> Sent: Tuesday, October 28, 2014 23:26
> Would you please take a close look at following TIMEOUT failures:
>
> 1. eventsource/dedicated-worker/eventsource-constructor-non-same-
> origin.htm
Per the talk at [2], this test and 3rd one listed below failed the CORS check
for fetchFail("https://example.not/test";)
We may need to re-evaluate the tests, however, because the latest editor draft
[3] has removed this statement in the CR [4]:
[[
This constructor must be visible when the script's global object is either a
Window object or an object implementing the WorkerUtils interface.
]]
Thoughts, Simon & Odin?
> 2. eventsource/format-field-retry-bogus.htm
Latest Firefox Nightly gets PASS by manually running this test; so can revise
the test result.
The failure may be caused by short timeout setting for automatically running
the test. Will provide a fix after the test runner comes up to use [5].
> 3. eventsource/shared-worker/eventsource-constructor-non-same-
> origin.htm
>
> Perhaps these TIMEOUTs are caused by some factor other than an
> implementation bug (f.ex. the test case has a bug, the timeouts are
> caused by some "environmental" factor).
>
> -Thanks, Art
>
> [1]
[2]
http://lists.w3.org/Archives/Public/public-webapps-testsuite/2013Aug/0017.html
[3] http://dev.w3.org/html5/eventsource/
[4] http://www.w3.org/TR/2012/CR-eventsource-20121211/#dom-eventsource
[5] https://github.com/w3c/web-platform-tests/issues/1372
RE: where do tests for window.opener go?
> From: Hallvord R. M. Steen [mailto:hst...@mozilla.com] > Sent: Wednesday, May 21, 2014 4:22 AM > To: public-webapps > Subject: [web-platform-tests] where do tests for window.opener go? > > Hi, > we have a window.opener issue and would like to have some tests for it. I'm > planning to write some and thought I might as well add them to the web- > platform-tests suite. Where? Would this be a suitable location: > https://github.com/w3c/web-platform- > tests/tree/master/html/browsers/the-window-object/security-window ? > -HR For security, yes. For navigating auxiliary browsing contests in the DOM, better to https://github.com/w3c/web-platform-tests/tree/master/html/browsers/windows/auxiliary-browsing-contexts
RE: [April2014Meeting] Plans and expectations for specs in CR; deadline April 9
> From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Thursday, April 10, 2014 4:40 AM > To: Zhang, Zhiqiang > Cc: public-webapps; o...@pettay.fi > Subject: Re: [April2014Meeting] Plans and expectations for specs in CR; > deadline April 9 > > On 4/9/14 1:06 PM, ext Arthur Barstow wrote: > > On 4/9/14 11:19 AM, ext Olli Pettay wrote: > >> On 04/09/2014 09:10 PM, Arthur Barstow wrote: > >> > >>> My recollection is that during the TPAC2013 meeting, Jonas said that > >>> functionality was implemented so yes, it would be good if someone > >>> would please > >>> clarify the situation and plan. > >> > >> Gecko doesn't have EventSource in DedicatedWorker nor in > SharedWorker > > > > Olli - is there any plan or requirement to implement these interfaces > > or was there a decision to not implement them? > > Zhiqiang, FYI, Olli replied in IRC: > > [[ > <http://krijnhoetmer.nl/irc-logs/webapps/20140409> > > [22:03] smaug, do you know if Mozilla has any plans to implement > EventSource in Dedicated Work or SharedWorker? > # [22:04] not a high priority at least > # [22:04] EventSource is so rarely used > # [22:04] but yes, I'd like to support EventSource everywhere > # [22:05] (trying to find a list of things Gecko devs want to > put to workers) > # [22:06] so no open bug or any type of Intent to Implement? > # [22:06] there is a bug open > # [22:07] https://bugzilla.mozilla.org/show_bug.cgi?id=876498 > ]] > > (I updated the EventSource Implementation Report to include a link to > this bug.) Great, thanks. I refined the comment in the EventSource Implementation Report.
RE: [April2014Meeting] Plans and expectations for specs in CR; deadline April 9
Hi Art, > From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Wednesday, April 2, 2014 7:12 PM > To: Zhang, Zhiqiang; Travis Leithead; Alex Kuang; Kris Krueger; Vincent > Scheib; > Simon Pieters; Philippe Le Hégaret; Cameron McCormack > Cc: public-webapps > Subject: [April2014Meeting] Plans and expectations for specs in CR; deadline > April 9 > > [ Bcc: public-webapps-testsuite ] > > Hi All, > > WebApps currently has 7 specs in CR, and 4 of them have at least one > Draft implementation report [Interop]. In preparation for the upcoming > meeting, I would appreciate if by April 9 the Test Facilitators these > CRs would please provide a short status, plans, expectations and such > for their test suites [Tests]: > > * IDB: Zhiqiang; test suite status; plan to create an Implementation Report I've reviewed the open pull requests and moved all tests into https://github.com/w3c/web-platform-tests/tree/master/IndexedDB. And ran the tests on Chrome and Firefox in http://w3c-test.org/tools/runner/index.html (/IndexedDB/ as path), to get an initial implementation report http://zqzhang.github.io/IndexedDB-test/ Though we've gotten a test suite for IDB, it is not yet completed; at least we can do the following as I observed: - improve support.js as comment https://github.com/w3c/web-platform-tests/pull/516#issuecomment-39178659 - add more tests, for example, some of the checkpoints for exception are valuable in https://github.com/w3c/web-platform-tests/pull/292 - revisit the failed tests and provide fixing in need - add test results of IE11; is there someone can help on this? > * Pointer Lock: Vincent; implementation status; test suite status; plan > to "complete" test suite > > * Server-sent Events: Zhiqiang; is the implementation report current > <http://www.w3.org/wiki/Webapps/Interop/ServerSentEvents>; when do > you > expect the CR exit criteria to be met? Yes, with one update that request-credentials.htm passed on Chrome and Firefox with fixing https://github.com/w3c/web-platform-tests/pull/836 applied; however, this fixing is not so perfect. Another, I'd like to ask Mozilla experts to double check if the shared and dedicated worker are supported on Firefox as below tests or if there are bugs in the tests themselves; can someone help on this? - http://w3c-test.org/eventsource/dedicated-worker/ - http://w3c-test.org/eventsource/shared-worker/ Thanks, Zhiqiang > > * Web IDL: Travis; test suite status and plans; implementation status. > Cam - what is the plan and expectation to move v1 back to LCWD; what are > the high priority contentious issues/bugs? > > * Web Messaging; Alex; test suite status; is there a `newer` > implementation report > than<http://www.w3.org/wiki/Webapps/Interop/WebMessaging>; when do > you > expect the CR exit criteria to be met > > * Web Sockets; Kris; test suite status; is there a `newer` > implementation report than > <http://www.w3.org/wiki/Webapps/Interop/WebSockets>; when do you > expect > the CR exit criteria to be met > > * Web Workers; Simon; test suite status; is there a `newer` > implementation report than > <http://www.w3.org/wiki/Webapps/Interop/WebWorkers>; when do you > expect > the CR exit criteria to be met > > Also, if any of the [PubStatus] Testing data for these specs is wrong or > incomplete, please update the wiki directly or provide the updates that > need to be made. > > -Thanks, AB > > [Tests] <http://w3c-test.org/> > [Interop] <http://www.w3.org/wiki/Webapps/Interop/> > [PubStatus] <https://www.w3.org/2008/webapps/wiki/PubStatus> > > >
[IndexedDB] Duplicate double quotes
3.1.7 Transaction
enum IDBTransactionMode {
""readonly"",
""readwrite"",
"versionchange""
};
https://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html
Thanks,
Zhiqiang
RE: [testing] Seeking Test Facilitator(s) for Indexed Database API
> From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Saturday, November 23, 2013 2:58 AM > Please contact me if you can commit to helping with this effort and you > have `relevant` experience. After reconsidering your invitation at TPAC about this, I would like to take this role and to review the submissions from next week. BTW, I will backup Tina Zhao, the Test Facilitator for Server Sent Events, for about half a year during her maternity leave. Please contact me if you have any matters related to SSE. Thanks, Zhiqiang
