Closed
Bug 761939
Opened 12 years ago
Closed 12 years ago
Don't force-disable remote content on Windows
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cjones, Assigned: cjones)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
vingtetun
:
review+
bent.mozilla
:
feedback+
|
Details | Diff | Splinter Review |
bent fixed content process gfx for windows while working on cross-process IDB. We just need to remove the ifdef from b2g.js.
|
Assignee | |
Comment 1•12 years ago
|
||
bent should vouch for this, but it doesn't really matter who reviews.
Assignee: nobody → jones.chris.g
Attachment #630470 -
Flags: review?(bent.mozilla)
Attachment #630470 -
Flags: review?(21)
Attachment #630470 -
Flags: review?(21) → review+
|
|
Assignee | |
Comment 2•12 years ago
|
||
Comment on attachment 630470 [details] [diff] [review]
Don't force-disable content processes for windows, they work now
Will land tomorrow or before bent signs off, whichever is sooner.
Attachment #630470 -
Flags: review?(bent.mozilla) → feedback?(bent.mozilla)
|
|
Assignee | |
Comment 3•12 years ago
|
||
s/before/when/
Comment on attachment 630470 [details] [diff] [review]
Don't force-disable content processes for windows, they work now
Yep, they worked fine for me.
Attachment #630470 -
Flags: feedback?(bent.mozilla) → feedback+
|
||
Updated•12 years ago
|
Summary: Don't force-disable remote content for windows → Don't force-disable remote content on Windows
|
|
Assignee | |
Comment 5•12 years ago
|
||
|
||
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•