Closed
Bug 910797
Opened 12 years ago
Closed 12 years ago
Fix Event.isTrusted handling for workers
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla26
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(2 files)
|
8.73 KB,
patch
|
khuey
:
review+
|
Details | Diff | Splinter Review |
|
10.61 KB,
patch
|
Details | Diff | Splinter Review |
"IsCaller" is a bit wrong. Should be something like "IsInChromeContext"
but that doesn't mean JSContext but the broader concept. So IsCaller for now.
Attachment #797353 -
Flags: review?(khuey)
Comment on attachment 797353 [details] [diff] [review]
patch
Review of attachment 797353 [details] [diff] [review]:
-----------------------------------------------------------------
::: content/base/src/nsContentUtils.cpp
@@ +1771,5 @@
> +nsContentUtils::ThreadsafeIsCallerChrome()
> +{
> + return NS_IsMainThread() ?
> + IsCallerChrome() :
> + mozilla::dom::workers::IsCurrentThreadRunningChromeWorker();
Please put a big fat assertion in IsCallerChrome.
::: xpcom/base/CycleCollectedJSRuntime.h
@@ +205,5 @@
> + JSRuntime* Runtime() const
> + {
> + MOZ_ASSERT(mJSRuntime);
> + return mJSRuntime;
> + }
You should get rid of the Runtime() methods in XPCJSRuntime and WorkerJSRuntime then.
Attachment #797353 -
Flags: review?(khuey) → review+
| Assignee | ||
Comment 2•12 years ago
|
||
| Assignee | ||
Comment 3•12 years ago
|
||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•