You know, that statement makes even less sense in that case.vannilla wrote:I was recalling incorrectly about Mozilla: it wasn't about multithread but multiprocess (Electrolysis).
Of course XUL being a UI language will always be in the main process that governs the UI. It doesn't matter what language you use to build the UI, it will ALWAYS be a single process. Extensions dealing with content would of course have to be e10s compatible in their scripting/how they communicate back to the UI process, but that has no bearing on XUL or the XUL parser's parallelism or lack thereof.