Custom Input Blocked content BUG after update (Bugreport)

Help
9

Hi @ali_fath

There is a workaround found. The warning will be suppressed if you add this at the beginning of your HTML file:
<!-- saved from url=(0014)about:internet -->

The problem seems to be the this child process runs with different permissions. The thing is, this is the correct behavior. A warning SHOULD be displayed when loading dubious HTML files from disk.

If instead of a file a legitimate HTTP/S URL is used, this warning will not be shown.

Very late EDIT with som more options:
<meta http-equiv="X-UA-Compatible" content="IE=Edge"/> - this is forcing to use Edge engine (allows for HTML5 features)
<!-- saved from url=(0016)http://localhost --> - this enables automatic sandbox mode which additionally skips the security

13 Likes