[Scout 6.1] BrowserField [message #1751355] |
Mon, 09 January 2017 10:30 |
|
Hello there,
yesterday I tried to display a URL-String in a BrowserField. But the field remained empty.
I know that browserField.setLocation(URLString) is invoked but the field stays empty.
Any ideas why?
Thanks
Peter
|
|
|
Re: [Scout 6.1] BrowserField [message #1751384 is a reply to message #1751355] |
Mon, 09 January 2017 15:54 |
|
Peter Pfeifer wrote on Mon, 09 January 2017 05:30yesterday I tried to display a URL-String in a BrowserField. But the field remained empty.
I know that browserField.setLocation(URLString) is invoked but the field stays empty.
It is possible that your URL is simply blocked by the browser. Scout's browser field is implemented using <iframe> elements, so all restrictions for iframes apply.
For example, it is not possible to include a http URL inside a https page for security reasons. It is also possible that the target location refuses to be shown inside another page ("X-Frame-Options"). Browser usually report blocked page access with an error message on the developer console (try f12 or ctrl-shift-i). Unfortunately, there is nothing you can do about. It's just the way browsers work nowadays. The only thing you can configure are the sandbox attributes (see the corresponding getConfigured... methods on the AbstractBrowserField).
Regards,
Beat
|
|
|
|
Powered by
FUDForum. Page generated in 0.02322 seconds