Closed
Bug 1006562
Opened 11 years ago
Closed 11 years ago
WorkerDataStoreCursor.store should be equal to the WorkerDataStore which owns the cursor
Categories
(Core :: DOM: Workers, defect)
Core
DOM: Workers
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: airpingu, Assigned: airpingu)
References
Details
Attachments
(2 files, 2 obsolete files)
(deleted),
patch
|
baku
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
baku
:
review+
|
Details | Diff | Splinter Review |
This is a follow-up for bug 949325. We need to fix the test of:
is(cursor.store, gStore, "Cursor.store is the store");
in the file_sync_worker.js.
The tricky part is cursor.store will return a newly created WorkerDataStore shell which proxie to the real DataStore. However, we shouldn't create a new WorkerDataStore to return. Instead, we should return the WorkerDataStore which owns the WorkerDataStoreCursor.
I already had a patch for this. Will upload it tomorrow.
Assignee | ||
Comment 1•11 years ago
|
||
Forgot to clean up the CC list when cloning. Sorry for the noise.
Keywords: dev-doc-needed
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gene.lian
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #8418492 -
Flags: review?(amarchesini)
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8418493 -
Flags: review?(amarchesini)
Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 8418492 [details] [diff] [review]
Part 1, minor code clean-up
Review of attachment 8418492 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/workers/DataStore.cpp
@@ +360,5 @@
> }
> };
>
> +// A DataStoreRunnable to run DataStore::Clear(...) on the main thread.
> +class DataStoreClearRunnable MOZ_FINAL : public DataStoreRunnable
I just move DataStoreClearRunnable to a better place which collects all the runnables, so that the real API implementations can be listed consecutively and to be viewed easily.
Assignee | ||
Updated•11 years ago
|
Flags: in-testsuite+
Updated•11 years ago
|
Attachment #8418493 -
Flags: review?(amarchesini) → review+
Comment 5•11 years ago
|
||
Comment on attachment 8418492 [details] [diff] [review]
Part 1, minor code clean-up
Review of attachment 8418492 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/workers/DataStore.cpp
@@ +36,5 @@
> {
> JSContext* cx = aGlobal.GetContext();
> WorkerPrivate* workerPrivate = GetWorkerPrivateFromContext(cx);
> MOZ_ASSERT(workerPrivate);
> workerPrivate->AssertIsOnWorkerThread();
Why all of this if you want to call NS_NOTREACHED immediately after?
Assignee | ||
Comment 6•11 years ago
|
||
(In reply to Andrea Marchesini (:baku) from comment #5)
> Comment on attachment 8418492 [details] [diff] [review]
> Part 1, minor code clean-up
>
> Review of attachment 8418492 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> ::: dom/workers/DataStore.cpp
> @@ +36,5 @@
> > {
> > JSContext* cx = aGlobal.GetContext();
> > WorkerPrivate* workerPrivate = GetWorkerPrivateFromContext(cx);
> > MOZ_ASSERT(workerPrivate);
> > workerPrivate->AssertIsOnWorkerThread();
>
> Why all of this if you want to call NS_NOTREACHED immediately after?
Yeap, we can remove these.
Assignee | ||
Comment 7•11 years ago
|
||
Attachment #8418492 -
Attachment is obsolete: true
Attachment #8418492 -
Flags: review?(amarchesini)
Attachment #8418553 -
Flags: review?(amarchesini)
Assignee | ||
Comment 8•11 years ago
|
||
Sorry, wrong patch. This one is correct.
Attachment #8418553 -
Attachment is obsolete: true
Attachment #8418553 -
Flags: review?(amarchesini)
Attachment #8418555 -
Flags: review?(amarchesini)
Assignee | ||
Comment 9•11 years ago
|
||
Updated•11 years ago
|
Attachment #8418555 -
Flags: review?(amarchesini) → review+
Assignee | ||
Comment 10•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/65ba102d73b2
https://hg.mozilla.org/mozilla-central/rev/729515d1cfff
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in
before you can comment on or make changes to this bug.
Description
•