Message-ID: <a2057ea0-a8ca-9774-47f7-9a84372b8a87@solarpunk.cool>
Date: Mon, 8 Mar 2021 09:55:01 +1300
MIME-Version: 1.0
Subject: Re: [pages] Behaviour of Links
Content-Language: en-US
To: ~sircmpwn/sr.ht-discuss@lists.sr.ht
References: <fc729915-55f3-eff5-e345-c1fb0560a41b@coolguy.website>
 <20210307092859.epjy2rpc6svzblxa@arch>
From: "Webmaster At Solarpunk.Cool" <webmaster@solarpunk.cool>
In-Reply-To: <20210307092859.epjy2rpc6svzblxa@arch>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

 > Hm... This page[1] on my site includes an image that is inserted from

 > a relative path and there's never been a problem with it.

I checked your page, https://ariadnavigo.xyz/bio, on my phone and

desktop, using firefox, chrome, and safari.  Unfortunately, your 
profile image does

not load for me.  Your site reinforces my issue, actually, that the 
page is trying

to load:

https://ariadnavigo.xyz/ari.jpg#center

instead of:

https://ariadnavigo.xyz/bio/ari.jpg#center


 > W3C's (X)HTML5 validator shows there are errors in your HTML code,

Good catch with the w3c spec.  I updated the site so it now passes 
(except for a

warning about the content-security policy):

https://validator.w3.org/nu/?doc=https%3A%2F%2Fsolarpunk.cool%2Fexample

but my issue persists :(


On 3/7/21 10:28 PM, Ariadna Vigo wrote:
> Hi!
>
>> As the page shows, relative links (whether for navigation, external
>> stylesheets, or images) do not work as expected.  Only absolute paths work.
>> Also, links that open in a new tab do not work.
>>
>> The relative paths and links work when viewing the page locally.  I also
>> uploaded this folder to another site(hosted by nearlyfreespeech.net), and
>> the relative paths work as expected there too:
>> https://coolguy.website/example
> Hm... This page[1] on my site includes an image that is inserted from
> a relative path and there's never been a problem with it.
>
> W3C's (X)HTML5 validator shows there are errors in your HTML code,
> though.[2] I think my intuition isn't far too off if I tell you the
> problem seems to be that you're relying on some undefined behavior.
>
> Hope this helps!
>
> [1]: https://ariadnavigo.xyz/bio
> [2]: https://html5.validator.nu/?doc=https%3A%2F%2Fsolarpunk.cool%2Fexample&showimagereport=yes
>