{"id":44394,"date":"2019-04-02T03:01:43","date_gmt":"2019-04-01T17:01:43","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=44394"},"modified":"2019-04-02T05:40:13","modified_gmt":"2019-04-01T19:40:13","slug":"html-iframe-functionality-restrictor-follow-up-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/html-iframe-functionality-restrictor-follow-up-tutorial\/","title":{"rendered":"HTML Iframe Functionality Restrictor Follow Up Tutorial"},"content":{"rendered":"
\"HTML<\/a>

HTML Iframe Functionality Restrictor Follow Up Tutorial<\/p><\/div>\n

The recent HTML Iframe Functionality Restrictor Primer Tutorial<\/a> “proof of concept” asked a lot of the user in terms of imagination, to the extent that it was mainly helpful for people who didn’t know of the existence of the HTML iframe element had available to it the sandbox<\/a> attribute in the first place.<\/p>\n

But what about drilling down on this with those suboptions allowing back in various “functionality sets” we’ll not repeat here, as you can read it at HTML Iframe Functionality Restrictor Primer Tutorial<\/a>, because we found the exercise of allowing the user to refine their HTML iframe element sandbox attribute dynamically was quite intriguing, and served the purpose, at least for us, of seeing where things fit, more than somewhat<\/a>.<\/p>\n

So feel free to try the changed<\/a> sandbox_iframe_attribute.html<\/a> live run<\/a> below, trying out the new dropdown options to see whether it teaches you a thing or two too …<\/p>\n