Bug 170689
| Summary: | [WK2][iOS] Move away from UIKit runloop | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brent Fulgham <bfulgham> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ap, cdumez, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=170688 | ||
Brent Fulgham
The various WebKit2 processes were created using the full UIKit runloop. Since UIKit is designed to support full applications, it has features that are not needed for our focused lower-level WebKit processes.
We should move to a lower-level runloop concept so that we can tighten the sandboxes on WebProcess, NetworkProcess, etc., even further.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
<rdar://problem/31539225>
Chris Dumez
From the plist:
```
<key>RunLoopType</key>
<string>NSRunLoop</string>
```
Seems like this was already done.