I am able to make the lightning for gmail plugin work in Brave with "shields down" but I can't change browsers organization-wide to make a plug-in work. I need to resolve this for my users who want to use the lightning for gmail plugin, which is only available for Chrome. Refused to display ' in a frame because it set 'X-Frame-Options' to 'deny'. On March 27, 1981, a building under construction in Cocoa Beach. The error message I see in the javascript console after trying to load the lightning email application in Gmail is as follows: Florida lawmakers passed the threshold inspection law in the wake of another building collapse a little more than 40 years ago. I'm using a Developer org API Version 44.0. Both Enable clickjack protection for customer Visualforce pages with standard headers and Enable clickjack protection for customer Visualforce pages with headers disabled are unchecked. I'm currently having this issue with the Lightning Email Application for Gmail/Outlook in Chrome 71.
When loading the resources in my index.html, my paths were missing the first dot '.' and looked like that '/static/js/.' instead of './static/js/.' I have edited my medium article. I've also noticed that I had a silly error that was caused by my webpack build script. I don't know if it is going to cause my issues that I don't see : My application now works well. The directive has been applied, and the value ignored.ĭo you know if it's possible to remove these errors ? I run into these error with every application I try to load within a lightning container. The Content Security Policy directive 'upgrade-insecure-requests' should be empty, but was delivered with a value of 'frame-ancestors."Invalid 'X-Frame-Options' header encountered when loading.
However I have to CSP errors when loading it : : I have successfully imported and displayed your application within a lightning container.
0 kommentar(er)
