Chromium-based browsers treat all buttons as a random button

[Zichqec]

We've had a lot of fun setting up a webring for our little community, but it seems that chromium-based browsers don't use the next/previous buttons correctly. On Firefox, everything works as intended, but on Chrome, Brave, and Edge, every button acts like a random button.

I messed around with your example webring a little bit, and I found something even more strange. While using Brave, the webring links on this page all work as intended: https://mxb.dev/blog/the-return-of-the-90s-web/
But on this page on the same ring, they all act as random buttons: https://fanlistings.nickifaulk.com/webrings/
I don't think it's directly related to if people use the pre-made box or not, because one of our webring members does not use the box and their links still all act as random buttons.

[sirodoht]

This project is based on the Referer header [1], which as of latest versions both major browser engines have dropped recently [2] [3]. Probably the reason it’s still working for Brave is that they haven’t (yet?) adopted Chrome’s new default referer policy even though they use the same engine.

I’m not sure how this can be fixed. I like the new default referer policy so I think I’d rather just have old school webrings with manual links instead.

[1]

webring/_lambda/next.js

Line 5 in d099a7c

const site = getNext(referer) || getRandom()

[2] https://developers.google.com/web/updates/2020/07/referrer-policy-new-chrome-default
[3] https://blog.mozilla.org/security/2021/03/22/firefox-87-trims-http-referrers-by-default-to-protect-user-privacy/

[Zichqec]

Hmm... That's a shame, it would be difficult to get webring members to manually change their links when a new member joins, so I worry new members wouldn't get much attention.

I tried Chrome with the links here ( https://mxb.dev/blog/the-return-of-the-90s-web/ ) too, and it works properly there as well. So I don't think there's any real difference between Chrome and Brave here? I'm curious why this one webring banner works as expected while all the others don't... there doesn't seem to be anything special about it. Very strange.

If there's nothing to be done about it I'll let the other members know, but I do wonder if there's some way to replicate that one banner that's working correctly.

[sirodoht]

@Zichqec

Hmm... That's a shame, it would be difficult to get webring members to manually change their links when a new member joins, so I worry new members wouldn't get much attention.

The cool thing with webrings is that only one needs to change only one of their links!

So, let's say I want to be part of your webring, all that needs to happen is for you to point to my website as your "next" and me to point to your old "next" as my "next" (and my "previous" to your website).

I tried Chrome with the links here ( https://mxb.dev/blog/the-return-of-the-90s-web/ ) too, and it works properly there as well.

Hmm yeah that’s weird. I wonder what’s the deal here.

[Zichqec]

Ahh, that's true. RIP our tidy order haha, because of the nature of our community a lot of folks have multiple pages on the webring. Hm, I suppose that means we'd probably have to get rid of the banner and just go with plain links then, huh? I'll bring it up and see if anyone else thinks it would be worthwhile to switch. Thank you!

[Porges]

This can be fixed by settting a different Referrer-Policy, such as referrerpolicy="no-referrer-when-downgrade", on the <a> links.