lies an interesting update regarding a technique mentioned in Dean's blog. It seems that the said technique may not work well in Safari based on comments received. Therefore, there is a query about its compatibility with modern browsers, especially Safari.
A recent blog post mentions support for sandboxed natives in various browsers, including Safari 2.0+. However, it also states that the iframe technique is not supported by Safari, leading to some unconventional methods involving faked constructors and __proto__. This raises questions about the shared nature of prototypes between different windows, particularly in cross-domain iframe scenarios.
The discussion delves into modifying prototypes in one frame without impacting those in another, addressing security concerns surrounding potential vulnerabilities. The term "work" here refers to the ability to modify prototypes independently in separate windows.
In the original post, the focus was on extending native types in JavaScript without altering the types themselves directly. Various solutions were considered, ultimately leading to a strategy involving creating a separate window to add functionality to prototypes of native constructs.
An example showcases the extension of Array as My.Array with an each function and String as My.String with an alert function. There are queries about the precedent of this approach, its naming conventions, availability of additional information, potential pitfalls, and alternative methods to obtain a distinct global scope.
Subsequent updates mention this method being referred to as an iframe sandbox, distinct from the HTML5 iframe sandbox attribute. Relevant links to further explore these topics are provided at the end of the text.