Why'd you use the formatting for blocks of code, for key parts of this post? Sentences cut-off on mobile and can't scroll to read the rest. I'm actually mostly making this comment so I can check the post later, on the desktop, to read what I missed.
It's an annoying workaround. Web-code (JavaScript, et-all) has been standardized for a long time. Too bad tech companies only acquire diversity-hires and incompetent woke-tards these days. Fwiw, I'm using Brave— the Christian Man's chrome browser.
Brave, me too. I have not heard anything about Brave, just been hoping it works ok and maybe avoid any issues of snoops. I have tried others, yanek, ecosia, couple of others but didn't really like those. So thanks for mentioning Brave!
Brave is run by one of the first Christian men to be cancelled by the tech industry. The man invented JavaScript, and was kicked off Firefox (his invention) for being anti-gay-marriage. So I fully support Brave in every single way.
Well, then it sounds like a problem with Brave. Because I am not having the issue you have in Chrome on mobile. These edge cases can often slip by a small team, they would probably appreciate a support ticket.
And yes, the problem is that web code was standardized a long time ago when screens were all horizontal and weighed 10 pounds. Most mobile browsers are forks and not built from the ground-up. Eventually AI will be embedded in all corporate browsers that can "smart" rearrange the HTML to look perfect on any screen, as well as algorithmically serving you ads and tracking you.
Or just, you know, add like a paragraph of code that stops superfluous shit from running off-screen and intelligently (no AI needed) wraps stuff when it does. Think of how many millions of dollars goes in to web-engine development. This problem shouldn't even exist. I blame diversity hires.
Why'd you use the formatting for blocks of code, for key parts of this post? Sentences cut-off on mobile and can't scroll to read the rest. I'm actually mostly making this comment so I can check the post later, on the desktop, to read what I missed.
Three dots. Scroll down. "Request Desktop Site" or something similar. FWIW, code blocks wrap correctly on Chrome mobile
It's an annoying workaround. Web-code (JavaScript, et-all) has been standardized for a long time. Too bad tech companies only acquire diversity-hires and incompetent woke-tards these days. Fwiw, I'm using Brave— the Christian Man's chrome browser.
Brave, me too. I have not heard anything about Brave, just been hoping it works ok and maybe avoid any issues of snoops. I have tried others, yanek, ecosia, couple of others but didn't really like those. So thanks for mentioning Brave!
Brave is run by one of the first Christian men to be cancelled by the tech industry. The man invented JavaScript, and was kicked off Firefox (his invention) for being anti-gay-marriage. So I fully support Brave in every single way.
Well, then it sounds like a problem with Brave. Because I am not having the issue you have in Chrome on mobile. These edge cases can often slip by a small team, they would probably appreciate a support ticket.
And yes, the problem is that web code was standardized a long time ago when screens were all horizontal and weighed 10 pounds. Most mobile browsers are forks and not built from the ground-up. Eventually AI will be embedded in all corporate browsers that can "smart" rearrange the HTML to look perfect on any screen, as well as algorithmically serving you ads and tracking you.
Or just, you know, add like a paragraph of code that stops superfluous shit from running off-screen and intelligently (no AI needed) wraps stuff when it does. Think of how many millions of dollars goes in to web-engine development. This problem shouldn't even exist. I blame diversity hires.