diff options
| author | bors-servo <metajack+bors@gmail.com> | 2014-10-16 14:15:21 -0600 |
|---|---|---|
| committer | bors-servo <metajack+bors@gmail.com> | 2014-10-16 14:15:21 -0600 |
| commit | 8d3b107568ab965b518b8003b702a5db993fa7d0 (patch) | |
| tree | b89d2323002625864bcb5c942d6ec00b97afa404 /components/script/html | |
| parent | 5be4f40bef05c749bdb5353541abae21a826f6b6 (diff) | |
| parent | c9b7d1f8dfed86c10bca55ae7bba7d8831066e73 (diff) | |
| download | servo-8d3b107568ab965b518b8003b702a5db993fa7d0.tar.gz servo-8d3b107568ab965b518b8003b702a5db993fa7d0.zip | |
auto merge of #3670 : kmcallister/servo/h5e-take2, r=jdm
r? @Ms2ger, @jdm
The parser is now a JS-managed object and we use hooks in html5ever to trace its internal state. This should be memory-safe even if arbitrary JavaScript can run during a parse. Please let me know if you think of a reason it wouldn't be!
I think the likely outcome of a garbage collection during parsing is a dynamic `RefCell` borrow failure, but I'm going to look into that after this lands. It should be safe to trace the parser while it's mutably borrowed, as long as it's not shared between threads, so we can probably switch to `UnsafeCell`.
Diffstat (limited to 'components/script/html')
0 files changed, 0 insertions, 0 deletions