You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not urgent, just filling issue so we dont forget to clean this up
My understanding is that the hack in changeCssFontPath was introduced as a way of demoing how websites can load without having to set up proper origin isolation just for the iframe-based demo.
As part of productizing, we should remove hacks like this: only subdomain-based isolation is supported for web hosting of arbitrary sites and dapps.
The fact that some things do not work on path gateways is "a feature, not a bug",
and if anything, we should warn users who use path gateway for website hosting, as noted in #30.
The text was updated successfully, but these errors were encountered:
My understanding is that the hack in
changeCssFontPath
was introduced as a way of demoing how websites can load without having to set up proper origin isolation just for the iframe-based demo.As part of productizing, we should remove hacks like this: only subdomain-based isolation is supported for web hosting of arbitrary sites and dapps.
The fact that some things do not work on path gateways is "a feature, not a bug",
and if anything, we should warn users who use path gateway for website hosting, as noted in #30.
The text was updated successfully, but these errors were encountered: