{"id":2707,"date":"2015-04-10T12:00:54","date_gmt":"2015-04-10T17:00:54","guid":{"rendered":"http:\/\/mikeconley.ca\/blog\/?p=2707"},"modified":"2023-12-20T16:25:11","modified_gmt":"2023-12-20T21:25:11","slug":"the-joy-of-coding-ep-9-more-view-source-hacking","status":"publish","type":"post","link":"https:\/\/mikeconley.ca\/blog\/2015\/04\/10\/the-joy-of-coding-ep-9-more-view-source-hacking\/","title":{"rendered":"The Joy of Coding (Ep. 9): More View Source Hacking!"},"content":{"rendered":"

In this episode1<\/a><\/sup>, I continued the work we had started in Episode 8, by trying to make it so that we don’t hit the network when viewing the source of a page in multi-process Firefox.<\/p>\n

It was a little bit of a slog – after some thinking, I decided to undo some of the work we had done in the previous episode, and then I set up the messaging infrastructure for talking to the remote browser in the view source window.<\/p>\n

I also rebased and landed a patch that we had written in the previous episode, after fixing up some nits2<\/a><\/sup>.<\/p>\n

Then, I (re)-learned that flipping the “remote” attribute of a browser is not enough in order for it to run out-of-process; I have to remove it from the DOM, and then re-add it. And once it’s been re-added, I have to reload any frame scripts that I had loaded in the previous incarnation of the browser.<\/p>\n

Anyhow, by the end of the episode, we were able to view the source from a remote browser inside a remote view source browser!3<\/a><\/sup> That’s a pretty big deal!<\/p>\n

Episode Agenda<\/a><\/p>\n

References<\/h2>\n

Bug 1025146 – [e10s] Never load the source off of the network when viewing source<\/a> – Notes<\/a><\/p>\n