Safari Browser Architecture for Web Extension

A general question regarding the architecture of the web extensions in Safari 14.

Does it follow a similar strategy used by chrome ?

Do content scripts reside in a separate process or are they part of the same process as the webpage?
Safari Browser Architecture for Web Extension
 
 
Q