Make relativeURLs work for urls inside css file or <style>

[apporc]

Currenctly, relativeURLs only process those urls specified as href, for urls inside a style tag, it doesn't work.

For example

<style>
  @font-face {
    font-family: 'Icon';
    src: url('{{ "./fonts/icon.eot"}}');
  }
</style>

This tag is coded like that in an html file, which will be included in many other htmls.
Now in every html file, it is always './fonts/icon.eot', but there are cases it should be '../fonts/icon.eot' or '../../fonts/icon.eot'.

It seems like others have submitted issues similar. Let me clarify why this feature is needed, it's just like the href tag case.

I am hosting my same site code on many different production environment, and they may have different root. As in a environment A, the hugo site will be visited under http://example.com/, but in environment B, it is visited under http://example.com/hugo. As you can see, i can't use '/fonts/icon.eot' because the root is different.

This example what i extracted from ipfs static blog site. I want to visit my site from https://ipfs.io/ipns/... or a web hosting of mine with http://example.com/. Hope you understand now.

[bep]

This is a known limitation. Have you searched for a duplicate issue?

[apporc]

Is this hard to implement, i have searched the code, got to transform/absurlreplacer.go, but i am not really familar with go.

[bep]

Is this hard to implement

Yes it is.

I suggest you look for older threads and workarounds for this.

[apporc]

I searched again in the older threads, didn't find a workaround. But i thought out an ugly one for myself, to restrict all my production environment with the same root.

[daviddavo]

I have the same issue, how did you manage to hack it? I'm trying to use .RelPermalink but it is relative to the base...

[jmooring]

@daviddavo The relativeURLs setting should only be used when creating a server-less site, navigable via the file system. The documentation includes the following guidance:

Do not enable this option unless you are creating a serverless site, navigable via the file system.

Please use the forum (https://discourse.gohugo.io/) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks.