[help] [img] [forum]
[Catalog] · [Search] [News] [Manage]
[Return]
Posting mode: Reply
Post reply
Name
Email
Subject
Message
CAPTCHA CAPTCHA Challenge Click to refresh.
File
Password For post deletion.
Submit  
  • Helpful information is available in the visitor guide. Currently 11 unique user posts.
  • Supported file types are JPG, PNG and GIF.
  • Maximum file size allowed is 2MB.
  • Images greater than 250x250 will be thumbnailed.
  • Supported BBCode tags are b, code, i, pre, sjis, spoiler, s and u.
1785094725561.png
Hi,

I'm not quite sure what's causing this behavior, or if it's just something on my end (I suspect it is), but these aren't supposed to show up on desktop view, are they?

I tried clearing cache/cookies, tried Firefox, Chromium, same thing happens.
I assumed this was caused by me being on Linux, because everything looks normal on Windows (no long bar, post hover activates only when you hover over the number), but I've spinned up a linux VM and it's not happening there as well.
The weirdest thing it didn't use to happen on my machine either, when it suddenly started happening after I reloaded a Sriracha instance and now it's happening everywhere.

When looking at the html It seems I'm triggering the mobile view version of the backlinks? I really have no idea why because it happens on different browsers with cache/cookies completely wiped and no extensions installed at all, only user agents should trigger these to appear shouldn't they? Is there anything else that could cause this behavior?

Html I'm seeing:
<a href="/help/res/52.html#54" class="refreply touchreflink" refid="54">&gt;&gt;54</a>


Sriracha currently determines when to enable mobile reflinks (touchscreen reflinks) based on the following:

1
2
3
4

const touchScreen = 'ontouchstart' in window ||
    (window.DocumentTouch && document instanceof window.DocumentTouch) ||
    navigator.maxTouchPoints > 0 ||
    window.navigator.msMaxTouchPoints > 0;

Do you also have a touchscreen attached to the device or any other pointer device beyond a mouse?

Please visit https://jsfiddle.net/Loyf8hvm/ (detects coarse pointer) on the same device you are experiencing this behavior and let me know what the alert message says. This might be a better way to detect when a touch screen is actually in use.


>>59
I do have a phone connected via KDE connect which can act as a pointer device but I never use it as such, but I also have a wireless usb keyboard with an integrated track-pad so not sure if that counts. When I visited the link I got a "Coarse pointer: false" but I am also currently not experiencing the issue.

I'm kinda leaning into the phone being at fault, although I wasn't able to directly trigger it by deliberately using it as a pointer device, I will see if the issue occurs with KDE connect being turned off although that's not ideal.

I'm guessing the reason this is done this way and not just via user agent is because touch capable devices can use non-mobile OSes too?

Also since we're on the topic of mobile backlinks, personally I find that their horizontal length makes triggering hover or a reply when just normally scrolling the page almost an inevitability while on a phone, at least from my experience. I think they should be probably way shorter, since on a phone they take up the entire horizontal length.


>>60
Thanks, that is helpful context. If you do experience the issue again, please retry that coarse pointer detection. If it still returns false, that would be good to know.

User agent matching might work for most cases, but I am hoping there is a reliable standard way to detect what kind of input device is actually being used to browse the page. The coarse pointer detection might work well for this.

I made the links wider to make it easier to preview posts, but I can see how it also interferes with page scrolling. I have been considering flipping the input scheme on mobile devices for other reasons, and since that should also resolve the issue you mentioned, I will plan on making those changes in the next release. Tracking issue:

https://codeberg.org/tslocum/sriracha/issues/121


>>60
Sriracha v1.9.0 is now available, which includes the mobile input changes I mentioned. Please refresh your page cache by pressing Shift+Refresh or by long-pressing the refresh button, then give the mobile reflink previews another try. Page scrolling should work now, even when a reflink is tapped.


1785284114399.png
>>61
Hi,

Reflinks are present and I'm still getting
Coarse pointer: false

I figured out what's causing it though, it's only happening when using Moonlight to remote into my machine, it seems Moonlight creates a virtual touch device which is what I'm guessing is triggering this, so it's not really an issue with Sriracha.

>>63
Thanks, scrolling is much less disruptive now.


>>64
Once v1.9.1 is released, Sriracha will rely on coarse pointer detection instead, which should resolve the issue you mentioned. I have also deployed the fix here just now.

Delete Post  
- Sriracha -