Earlier quoted context omitted.
I actually think it has more to do with the increasing size and sophistication of the touchpad in Macs. There is no need for a scroll bar when you have a touchpad you can flick (likewise for magic mice).
I don't know, not everybody has a macbook or a magic mouse. Plus even old, small, unprecise PC touchpads were enough to scroll a website. To me, it looks more related to the recent fashion of "minimal" interfaces. Like material design and ultra-skinny fonts. Could also be related to the "infinite scroll" some sites have. A scroll bar doesn't make much sense for those.
Scrollbar Blindness
61–70 of 575 posts
Re: Scrollbar Blindness
#62I loathe the fact that scrollbars are now hidden. I'm constantly looking for it to either a) find out how big the page is b) scroll more precisely I don't even understand why they would remove them? Who ever complained of a scroll bar?
I wonder if the designers of the systems , after becoming so bored with the status quo, begin to fetishize the sleek hidden thing that is scroll bar right now ... like when coders are writing algorithms for say, 10-15 years I bet their code gets a lot more compact and sleek looking , almost akin to tight 3 character variable leet code solutions etc.. maybe this is just the same phenomenon tearing its head in the desi…
If those coders are like me their code becomes more verbose, less clever, more obvious, less dependent on the quirks of the programming language I use. The reason is that it's easier for me and the other developers in the team to read and understand what it does.
On my way to here I really hated many geeky clever and brilliant pieces of code I found in projects I inherited. They made me and my customers lose days at decoding all that brilliance.
Re: Scrollbar Blindness
#63Earlier quoted context omitted.
They can be partially or completely re-enabled in the settings on MacOS.
Now I'm really confused, when does MacOS decide to hide scrollbars? Only when you're using a touchpad?
Re: Scrollbar Blindness
#64> Alternatively, you can set the scrollbars to be visible at all times by setting System Preferences -> General -> Show scroll bars to Always. Hidden scrollbars recently caused me an extra day of work. I was documenting all options in hundreds of html select boxes (dropdowns) on a legacy product being rewritten. Many of these dropdowns were vertically scrollable, but macOS using Chrome did not display a scrollbar. I…
Give the Chrome dev tools a try. It "un-minifies" the html making it viewable and easily traversable.
https://developers.google.com/web/tools/chrome-devtools/dom/
Re: Scrollbar Blindness
#65Another one of such thing: please try to scroll on your site using a mouse wheel from time to time, even if you're normally using a touchpad (from your laptop or an external one)! Lot of fancy homepage with scroll animations are awful on anything that isn't scrolling as smoothly as a MacBookPro touchpad. Example: https://www.apple.com/ipad-pro/ is horrible to use on anything that isn't a mobile device or a Mac.
I guess this is an example of being in my own bubble, but I can't stand touchpads. I've used the touchpad on MacBook, like, twice in 2 years.
Re: Scrollbar Blindness
#66Another one of such thing: please try to scroll on your site using a mouse wheel from time to time, even if you're normally using a touchpad (from your laptop or an external one)! Lot of fancy homepage with scroll animations are awful on anything that isn't scrolling as smoothly as a MacBookPro touchpad. Example: https://www.apple.com/ipad-pro/ is horrible to use on anything that isn't a mobile device or a Mac.
Re: Scrollbar Blindness
#67Earlier quoted context omitted.
Same complaint with contrast aye Yes your giga HD retina Mac displays these colours perfectly, I'm sure it looks great. On my screen however I can't read a damn thing.
Kind of an off-topic but recently I noticed capturing a gameplay video of an HDR-enabled video game with any kind of software (OBS, Twitch Studio, GeForce Experience, FRAPS, Discord) also produces terrible results. This happens even if I capture the entire monitor or just the app window. Both OpenGL and DirectX games suffer from this. How one can tell whether what you capture/develop is what you will see without test…
As a general rule of thumb, if it has anything to do with colors and comes from either computer or photography people, there's a solid 99 % chance it's broken or doesn't even know what color is. If you want to know how it's done right, you gotta look at how the "moving photos" people do it.
(Note: "everything" for me means "everything that's not Apple", because I cba to care about those snowflakes)
[1] Yes, yes, OpenGL has sRGB types for framebuffers, which doesn't work on half the devices in the wild (on the other half it applies the sRGB gamma function to linear sRGB data) and isn't meaningful anyway, because we _don't_ want to use sRGB. DXGI only does Rec.709 and Rec.2020, no DCI P3, and it also treats everything that's not HDR as sRGB.
Re: Scrollbar Blindness
#68Earlier quoted context omitted.
This highlights the bigger issue of web developers and designers only working on the latest and greatest hardware with the fastest performance and the best user experience. Their users may not have access to the same hardware, while developers and designers are totally blind to how their software might perform on anything but a recent model MacBook Pro or XPS.
In this case I'd say it highlights another problem too: web developers thinking it is their prerogative to control how their users scroll.
Apps and media can do whatever to the scrolling since it just an implementation detail to achieve some effect like slide transitions.
Documents shouldn’t touch it and leave it up to the client.
Re: Scrollbar Blindness
#69> Alternatively, you can set the scrollbars to be visible at all times by setting System Preferences -> General -> Show scroll bars to Always. Hidden scrollbars recently caused me an extra day of work. I was documenting all options in hundreds of html select boxes (dropdowns) on a legacy product being rewritten. Many of these dropdowns were vertically scrollable, but macOS using Chrome did not display a scrollbar. I…
> I could not look at the html for it as it was minimized and not easily searchable. Give the Chrome dev tools a try. It "un-minifies" the html making it viewable and easily traversable. https://developers.google.com/web/tools/chrome-devtools/dom/
https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
Re: Scrollbar Blindness
#70> Alternatively, you can set the scrollbars to be visible at all times by setting System Preferences -> General -> Show scroll bars to Always. Hidden scrollbars recently caused me an extra day of work. I was documenting all options in hundreds of html select boxes (dropdowns) on a legacy product being rewritten. Many of these dropdowns were vertically scrollable, but macOS using Chrome did not display a scrollbar. I…
In Chrome:
1) Right click on element you want to grab all of the contents of, and select Inspect Element. NOTE: If this element is the sort that isn't properly placed in the DOM and/or disappears when focus/mouse leaves, you can freeze the current DOM...but the right way to do that will depend on your context.
2) In Elements tab in Dev tools, the element should now be highlighted. You may need a parent or child element. But hopefully you can find it nearby and verify you have the right one with the Inspect tooling.
3) Right click on the element that has all your data in the DOM. Select Copy. Sometimes it will be enough to just Copy Element and paste it somewhere where you can start organizing the data. But for your task, it sounds like you might want to write a script for this so you can do it across multiple Elements. So, try Copy > Copy JS Path.
4) You now have access to the DOM element, even if it was created dynamically by JS and exists in the Shadow DOM. Try "paste" in the Console tab of Chrome DevTools.
5) The thing you grabbed might not be exactly the right one. Navigate down to the level you want to iterate across with the "children" attribute. Example:
const myStuff = document
.querySelector("#output > shadow-output")
.shadowRoot.querySelector("div > ul > li:nth-child(2)")
.children[0].children
6) You now have an HTMLCollection. You could be done! See if this gives you what you need: console.table(myStuff, ["innerHTML"])
-7) Unfortunately, HTMLCollections are only Array-like. Fortunately, it's very easy to convert. const stuffArr = [...myStuff]
-8) Now that you have a proper Array filled with HTML elements, you can do any kind of processing you need to grab the data you want. const mappedStuff = stuffArr.map(x=> { /* transform each thing */ }
console.table(mappedStuff)
Hope this helps somebody write a script to remove the tedium from a data extraction job.