You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently sandboxing the CSS by namespacing it with the name of the pagelet. The JavaScript sandboxing will be done a future release when we enable our fortress module. The only thing left to sandbox is the DOM. And DOM sandboxing is hard, but due to recent brainfarts I came up with the idea of re-using the virtual DOM idea of react and implement a similar process in bigpipe.
It would solve the sandboxing issues as you would not be modifying the actual dom but a virual dom. In addition to sandboxing it would also introduce high performance as only a diff of the DOM will be updated instead of a complete update of each pagelet.
The text was updated successfully, but these errors were encountered:
@3rd-Eden we should think about how we can make it possible to interop with something like react or other modules that handle this type of role. A way to make these types of solutions plugin to bigpipe well could be quite powerful.
We're currently sandboxing the CSS by namespacing it with the name of the pagelet. The JavaScript sandboxing will be done a future release when we enable our fortress module. The only thing left to sandbox is the DOM. And DOM sandboxing is hard, but due to recent brainfarts I came up with the idea of re-using the virtual DOM idea of react and implement a similar process in bigpipe.
It would solve the sandboxing issues as you would not be modifying the actual dom but a virual dom. In addition to sandboxing it would also introduce high performance as only a diff of the DOM will be updated instead of a complete update of each pagelet.
The text was updated successfully, but these errors were encountered: