Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
Currently, there is no tools to enable CORS support for web font file types. This becomes an issue if you want to reference assets (such as CSS files) through a CDN like AWS Cloudfront, but your CSS file references a web font file, such as WOFF, WOFF2, EOT, TTF... In that case, because the page is loaded on our domain, but the CSS is referenced on a Cloudfront domain, although that CSS file is approved with CORS, any reference to a web font within that CSS file is attempted on the Cloudfront domain and therefore denied access because the web font files do not have CORS support. This prevents the use of web font files referenced within a CSS file referenced on a CDN domain that is different from the main site domain. With server access, one can update CORS support to allow all domains to access the web fonts - but with Luminate Online we do not have that access to update CORS support. It would be great either web fonts were set to allow CORS support on all domains, or to enable a whitelist feature, similar to the Site Options in Luminate to then define which domains have CORS support for web fonts. More information on how to support this is in Support case #017008414.
|Area of the Product