4 ms·

https://archive.ph/oiYsr https://archive.ph/oiYsr (Page is not scrollable for me)

by forgotmypw17 4y ago

deleted 4y ago
[deleted]
cassiepaper 4y ago
Huh. Scrolls on my Pixel mobile device. Please specify browser and OS.
- forgotmypw17 4y ago
  Chrome on Android, JS off. I could not scroll down more than a couple lines of text. On desktop, I could reproduce the same issue in both Firefox- and Chrome-derived browsers.
- edent 4y ago
  On Firefox for Android the page suddenly jumped halfway down when I tried to scroll. Looks like you've implemented your own scrollbar which overrides the browser?
  - cassiepaper 4y ago
    Ah, yeah, I see now. I can recreate the problem on desktop. On my mobile it works. Indeed, the scrollbar is implemented to override the browser's. Why go to archive.ph, though, when you can go directly to https://melsloop.com/docs/mels-hack-the-missing-bits https://melsloop.com/docs/mels-hack-the-missing-bits ? - should work nicely on mobile.
    - qu4z-2 4y ago
      Presumably because the archive.ph version is actually scrollable cross-browser (or with JS turned off).
    - forgotmypw17 4y ago
      I use archive.xx to strip the original page of accessibility obstacles, such as modals and home-made scrolling behavior. Though most of the time I encounter such nonsense, I just close the tab and move on. There is rarely good content behind it.
- Wowfunhappy 4y ago
  On my iPhone 13 Mini, I can scroll up and down but the text is wider than the width of the screen and I can't zoom out or even scroll horizontally.
  - NobodyNada 4y ago
    On iOS you can trick the page into scrolling horizontally by selecting some text and dragging the selection marker beyond the right edge of the screen. Still an annoying workaround though, because the page snaps back to the left as soon as you try to scroll vertically again.
oneeyedpigeon 4y ago
I have a different issue with the custom scrollbar, although it's no less annoying - when I press anywhere near it (android), it auto-jumps, losing my place.
ddevault 4y ago
Tip: there is no reason to implement custom scrolling behaviors like this.
- cassiepaper 4y ago
  We'll consider a fix. Right now the scroll area is implemented via RadixUI, which seems to be very good, but your point is clear. If you have any practical tips/ideas/links to a good, solid, cross-browser scrollarea component - please let me know :)
  - HHad3 4y ago
    Just, uh... don't have a custom cross-platform scrollarea? This is a feature the browser provides already. Your page is perfectly usable by just removing `overflow: hidden scroll;` of div.data-radix-scroll-area-viewport`, and `overflow: hidden;` from .s24. So you'll probably achieve intended behavior of having a scroll area that works on all browsers by just not using any custom scroll area plugin, but a plain <div> instead.
  - oneeyedpigeon 4y ago
    I don't think I've ever had a good experience with a custom scrollbar. If it behaves any differently from every other scrollbar on my system, it's going to be inferior. And scrollbars work differently from system to system. What are you trying to achieve beyond the default scrolling behaviour?
  - ddevault 4y ago
    Just use HTML. Cleverness will not be tolerated.
    - cryptonector 4y ago
      Ironic, considering that TFA is judgmental about exactly that: > This approach to coding is far from extinct. One often finds it in software teams, among some highly regarded – though less valued – members. If you've spent several years in the industry or in Computer Science academia, you surely know this subspecies: the developer that replaces a straightforward loop with a series of auto-resolving promises, capped by a cryptic reducer, then revels in their teammates' bewilderment at the sight of the new code. Hardly the personality that you'd select for a coding legend. And then the site uses JS to implement a feature that every browser has! :)
cryptonector 4y ago
It is when you enable JS. Which, admittedly, is annoying.
- forgotmypw17 4y ago
  And the stairs are accessible if you're not using a wheelchair.

https://archive.ph/oiYsr https://archive.ph/oiYsr (Page is not scrollable for me)

deleted 4y ago

[deleted]

cassiepaper 4y ago

Huh. Scrolls on my Pixel mobile device. Please specify browser and OS.

forgotmypw17 4y ago
Chrome on Android, JS off. I could not scroll down more than a couple lines of text. On desktop, I could reproduce the same issue in both Firefox- and Chrome-derived browsers.
edent 4y ago
On Firefox for Android the page suddenly jumped halfway down when I tried to scroll. Looks like you've implemented your own scrollbar which overrides the browser?
- cassiepaper 4y ago
  Ah, yeah, I see now. I can recreate the problem on desktop. On my mobile it works. Indeed, the scrollbar is implemented to override the browser's. Why go to archive.ph, though, when you can go directly to https://melsloop.com/docs/mels-hack-the-missing-bits https://melsloop.com/docs/mels-hack-the-missing-bits ? - should work nicely on mobile.
  - qu4z-2 4y ago
    Presumably because the archive.ph version is actually scrollable cross-browser (or with JS turned off).
  - forgotmypw17 4y ago
    I use archive.xx to strip the original page of accessibility obstacles, such as modals and home-made scrolling behavior. Though most of the time I encounter such nonsense, I just close the tab and move on. There is rarely good content behind it.
Wowfunhappy 4y ago
On my iPhone 13 Mini, I can scroll up and down but the text is wider than the width of the screen and I can't zoom out or even scroll horizontally.
- NobodyNada 4y ago
  On iOS you can trick the page into scrolling horizontally by selecting some text and dragging the selection marker beyond the right edge of the screen. Still an annoying workaround though, because the page snaps back to the left as soon as you try to scroll vertically again.

oneeyedpigeon 4y ago

I have a different issue with the custom scrollbar, although it's no less annoying - when I press anywhere near it (android), it auto-jumps, losing my place.

ddevault 4y ago

Tip: there is no reason to implement custom scrolling behaviors like this.

cassiepaper 4y ago
We'll consider a fix. Right now the scroll area is implemented via RadixUI, which seems to be very good, but your point is clear. If you have any practical tips/ideas/links to a good, solid, cross-browser scrollarea component - please let me know :)
- HHad3 4y ago
  Just, uh... don't have a custom cross-platform scrollarea? This is a feature the browser provides already. Your page is perfectly usable by just removing `overflow: hidden scroll;` of div.data-radix-scroll-area-viewport`, and `overflow: hidden;` from .s24. So you'll probably achieve intended behavior of having a scroll area that works on all browsers by just not using any custom scroll area plugin, but a plain <div> instead.
- oneeyedpigeon 4y ago
  I don't think I've ever had a good experience with a custom scrollbar. If it behaves any differently from every other scrollbar on my system, it's going to be inferior. And scrollbars work differently from system to system. What are you trying to achieve beyond the default scrolling behaviour?
- ddevault 4y ago
  Just use HTML. Cleverness will not be tolerated.
  - cryptonector 4y ago
    Ironic, considering that TFA is judgmental about exactly that: > This approach to coding is far from extinct. One often finds it in software teams, among some highly regarded – though less valued – members. If you've spent several years in the industry or in Computer Science academia, you surely know this subspecies: the developer that replaces a straightforward loop with a series of auto-resolving promises, capped by a cryptic reducer, then revels in their teammates' bewilderment at the sight of the new code. Hardly the personality that you'd select for a coding legend. And then the site uses JS to implement a feature that every browser has! :)

cryptonector 4y ago

It is when you enable JS. Which, admittedly, is annoying.

forgotmypw17 4y ago
And the stairs are accessible if you're not using a wheelchair.