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
When you 'save entire page' in google chrome for a page using the build service (e.g. wanting to share a page with somebody who does not have access, or does not see the same customised view you do) build service bundles get saved as css and js with no file extension.
On opening these pages the content of the CSS file (and possibly js - I've not checked) fails to get processed as a stylesheet. Going into the source code and changing the file name to origami.css forces it to be treated as a stylesheet and the styles apply.
I'm not sure if this is
a) a bug in chrome
b) something that origami can/want to do anything about
But reporting anyway as it's an annoyance
Bikeshedding, perhaps the build service could start supporting /origami.css and mark the old /css as deprecated, eventually maybe 301-ing
The text was updated successfully, but these errors were encountered:
When you 'save entire page' in google chrome for a page using the build service (e.g. wanting to share a page with somebody who does not have access, or does not see the same customised view you do) build service bundles get saved as
css
andjs
with no file extension.On opening these pages the content of the CSS file (and possibly js - I've not checked) fails to get processed as a stylesheet. Going into the source code and changing the file name to
origami.css
forces it to be treated as a stylesheet and the styles apply.I'm not sure if this is
a) a bug in chrome
b) something that origami can/want to do anything about
But reporting anyway as it's an annoyance
Bikeshedding, perhaps the build service could start supporting
/origami.css
and mark the old/css
as deprecated, eventually maybe 301-ingThe text was updated successfully, but these errors were encountered: