|
Kheldarn posted:I'm on Chrome 78(.0.3904.97), and it's no longer showing https or www in the address bar. Searching for how to make it show up again leads me to results saying to go to chrome://flags/#omnibox-ui-hide-steady-state-url-scheme-and-subdomains or chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains, but neither of those exist for me. It hides that info until you focus the address bar. It's a recent change, and I don't know that there's a way to revert is especially since it's just cosmetic.
|
# ? Nov 10, 2019 00:16 |
|
|
# ? Apr 24, 2024 10:44 |
|
Atomizer posted:It hides that info until you focus the address bar. It's a recent change, and I don't know that there's a way to revert is especially since it's just cosmetic. Well, it sucks, because it screws things up when I browse reddit. I tend to click where https://www. is to replace it with old. and it selects part of it, and then either part of the [url]https://[/url] or part of the reddit. sections of the URL. Oh well. Guess I'm stuck with it.
|
# ? Nov 10, 2019 03:02 |
|
my workflow!
|
# ? Nov 10, 2019 03:07 |
|
Kheldarn posted:Well, it sucks, because it screws things up when I browse reddit. I tend to click where https://www. is to replace it with old. and it selects part of it, and then either part of the [url]https://[/url] or part of the reddit. sections of the URL. there's a much smarter way to accomplish what you want https://greasyfork.org/en/scripts/40897-old-reddit-please
|
# ? Nov 10, 2019 03:14 |
|
withak posted:my workflow! It's an unnecessary change no one asked for.
|
# ? Nov 10, 2019 10:01 |
|
Lambert posted:It's an unnecessary change no one asked for. Again, it's only cosmetic. The full address appears when you click it in the bar.
|
# ? Nov 10, 2019 11:43 |
|
There is a bit more take on it where it's part of Google's plan to kill URLs and force people to use search to access everything (see also AMP). I personally consider seeing the full URL a vital part of a browser's UI but I already use Firefox so I won't have to deal with this until they inevitably decide to copy it next year
|
# ? Nov 10, 2019 15:44 |
|
Mr.Radar posted:There is a bit more take on it where it's part of Google's plan to kill URLs and force people to use search to access everything (see also AMP). Settle down, it only hides http and www at the front of a url. IE the parts that are entirely irrelevant to anyone that isn't Kheldarn or other weirdos who constantly re-type https://www.reddit.com to old.reddit.com by hand. If you go to any site that leads the domain with anything other than www, it shows the sub-domain title. (Like, you know that if sign up a reddit account then you can just tell it to always use old reddit?)
|
# ? Nov 10, 2019 18:07 |
|
Klyith posted:Settle down, it only hides http and www at the front of a url. IE the parts that are entirely irrelevant to anyone that isn't Kheldarn or other weirdos who constantly re-type https://www.reddit.com to old.reddit.com by hand. If you go to any site that leads the domain with anything other than www, it shows the sub-domain title. So, basically, it hides the parts relevant to plenty of people for no gain to anyone. Got it.
|
# ? Nov 11, 2019 14:04 |
|
Lambert posted:So, basically, it hides the parts relevant to plenty of people for no gain to anyone. Got it. Ehh, I think plenty of normal people are confused by all the technical stuff in the address bar, so I wouldn't say "no gain to anyone". I'm not making any comments about whether the tradeoff is worth it or not.
|
# ? Nov 11, 2019 18:57 |
|
Kheldarn posted:I'm on Chrome 78(.0.3904.97), and it's no longer showing https or www in the address bar. Searching for how to make it show up again leads me to results saying to go to chrome://flags/#omnibox-ui-hide-steady-state-url-scheme-and-subdomains or chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains, but neither of those exist for me. For now, yes - "Temporarily unexpire M76 flags" - that brings back the various settings starting with "Omnibox UI Hide" that you then disable. https://www.reddit.com/r/chrome/comments/dlx3kj/how_to_show_http_and_www_in_the_omnibox_chrome_78/ Obviously Google are determined to get rid of the full URL permanently though. reddit posted:At that point someone will just write a 3rd-party extension.
|
# ? Nov 11, 2019 21:21 |
|
xiansi posted:For now, yes - "Temporarily unexpire M76 flags" - that brings back the various settings starting with "Omnibox UI Hide" that you then disable. Ah, thank you.
|
# ? Nov 12, 2019 05:36 |
|
I was reading that this new update will kill ublock origin for good? Is that true?
|
# ? Nov 12, 2019 13:51 |
|
Jippa posted:I was reading that this new update will kill ublock origin for good? Is that true? No, not yet. They just added manifest v3 to Canary (the alpha / testing branch of Chrome), which means it might go live in Chrome v80. But they're going to keep manifest v2 (what extensions use now) and v3 (the one that neuters adblock) both active at the same time. And then "v2 end of life to be determined in the future" which you should actually read as "when we think the mass audience has forgotten about the uproar and we've used financial support of Adblock Plus to get them moved to v3, so we can fight back by pitting users against each other and blame gorhil for being a bad stick in the mud who refused to adapt like ABP". In the meantime you have at least 6 months to try out other browsers and pick which one you like best. Klyith fucked around with this message at 16:09 on Nov 12, 2019 |
# ? Nov 12, 2019 15:09 |
|
Cheers.
|
# ? Nov 12, 2019 15:19 |
|
https://twitter.com/antumbral/status/1194973121888976896?s=19 This seems like a funny change that breaks a bunch of stuff https://www.zdnet.com/google-amp/article/google-chrome-experiment-crashes-browser-tabs-impacts-companies-worldwide/ Stormgale fucked around with this message at 21:46 on Nov 15, 2019 |
# ? Nov 15, 2019 21:42 |
|
says it's so they can stop people from playing YouTube in the background without a YouTube music subscription
|
# ? Nov 16, 2019 17:45 |
|
It's pretty useful for being able to throttle heavy CPU usage JS when the user isn't watching the fancy game/animation/spreadsheet.
|
# ? Nov 16, 2019 19:18 |
|
Why is vanilla Chrome even anyone's default browser at this point? It just seems to be getting worse.
|
# ? Nov 16, 2019 21:26 |
|
Woebin posted:Why is vanilla Chrome even anyone's default browser at this point? It just seems to be getting worse. For me it's literally because scrolling feels weird and off in Firefox compared to Chrome on Windows.
|
# ? Nov 16, 2019 21:37 |
|
effika posted:says it's so they can stop people from playing YouTube in the background without a YouTube music subscription I can totally believe this, since you already can't on Android without tricking it.
|
# ? Nov 16, 2019 23:23 |
|
This:Stormgale posted:https://twitter.com/antumbral/status/1194973121888976896?s=19 Hipster_Doofus posted:I can totally believe this, since you already can't on Android without tricking it. so now I have an addon for firefox-android that disables Page Visibility API rather than needing to force the desktop site (which my 720p phone can't really display).
|
# ? Nov 16, 2019 23:37 |
|
101 posted:For me it's literally because scrolling feels weird and off in Firefox compared to Chrome on Windows. Disable smooth scrolling in Firefox.
|
# ? Nov 17, 2019 01:27 |
|
effika posted:says it's so they can stop people from playing YouTube in the background without a YouTube music subscription
|
# ? Nov 17, 2019 04:23 |
|
Overlap checks is what the twitter thread and all the recent replies are about.
|
# ? Nov 17, 2019 05:38 |
Hipster_Doofus posted:I can totally believe this, since you already can't on Android without tricking it. newpipe is the bee's knees for this.
|
|
# ? Nov 17, 2019 07:03 |
|
drat straight. I don't even miss Vanced.
|
# ? Nov 17, 2019 12:18 |
|
Ghostlight posted:Overlap checks is what the twitter thread and all the recent replies are about.
|
# ? Nov 17, 2019 13:40 |
|
101 posted:For me it's literally because scrolling feels weird and off in Firefox compared to Chrome on Windows.
|
# ? Nov 17, 2019 17:01 |
|
I looked this WebContents occlusion poo poo up some more. These assholes over at Google want to hook into all running processes in the session, just to figure out if a window moved? gently caress that poo poo. Edgium was so nice, I guess not.
|
# ? Nov 17, 2019 17:50 |
|
I guess I'm missing something about why everyone is bent out of shape on this. It's been possible to detect if user has window focused or visible for many years, this just gives a better API for it.
|
# ? Nov 17, 2019 18:07 |
|
I mean they may or may not be wanting to do YT shenanigans, but prior to this API it was already possible
|
# ? Nov 17, 2019 18:09 |
|
Lambert posted:Disable smooth scrolling in Firefox. but then it's a jumpy mess that still doesn't feel like Chrome Woebin posted:I mean, in addition to Lambert's suggestion to disable smooth scrolling, there are tons of other Chromium-based browsers you could use that aren't pulling a lot of the poo poo Google is. Vivaldi's great these days, for instance. That's a fair point. I might give Vivaldi a try for a few days
|
# ? Nov 17, 2019 18:16 |
|
101 posted:That's a fair point. I might give Vivaldi a try for a few days It's good but still needs polish. I now use it for maybe 75% of my browsing.
|
# ? Nov 17, 2019 18:25 |
|
Thermopyle posted:I guess I'm missing something about why everyone is bent out of shape on this. I suppose in the case of Edgium, I can just run it permanently inside WDAG to wall it off, but I guess eventually I'll just switch to Firefox, until they do something stupid, too. --edit: Here's a quote from the Windows SDK documentation, that's probably relevant besides the principle of not wanting Chrome to snoop around among all processes: quote:Hooks tend to slow down the system because they increase the amount of processing the system must perform for each message. You should install a hook only when necessary, and remove it as soon as possible. Combat Pretzel fucked around with this message at 18:59 on Nov 17, 2019 |
# ? Nov 17, 2019 18:48 |
|
Woebin posted:Vivaldi's great these days, for instance. If Kiwi Browser had a windows port I'd cream my skivvies.
|
# ? Nov 17, 2019 19:01 |
|
For the rest of the thread, this doc is what Combat Pretzel is going on about. It isn't too technical for an average nerd to grasp. But the tl;dr is basically "oh the simple API that MS made for getting occlusion status isn't precise enough for us, we're gonna do it the hard way" and then lists a whole bunch of giant downsides of the hard way However: Combat Pretzel posted:--edit: Still, it seems like a dumb and fragile way to do things. You can't trust windows programs to tell you sane things about themselves, which is probably why it broke on terminal server. Even after their effort to discard stuff like complex or transparent windows, some program said that it had the entire screen region when it didn't so chrome thought it was occluded.
|
# ? Nov 17, 2019 20:31 |
|
It's funny that I switched into my browser to take a break from developing a library for python that uses the exact same windows APIs that are talked about in that document. (I'm so tired of the limitations of AutoIT and AHK) Hooking windows events is super common for many applications to do. It's not some shady weird thing. The APIs talked about in that document aren't peeking around into other processes. These are events that are broadcast to the whole system about the size and position of all the windows on the desktop. Of course, it's true that if you do it wrong like hooking from EVENT_MIN to EVENT_MAX, not throttling/debouncing, and running CPU-intensive callbacks on events it can really impact your CPU load...but since it seems like the whole purpose of that document is to improve performance I would assume they won't do it wrong. edit: I'm really struck by how much all of the thinking in that document are the same sort of things I've had to think about over the past many months working on this library of mine. Thermopyle fucked around with this message at 22:59 on Nov 17, 2019 |
# ? Nov 17, 2019 22:55 |
|
So my keyboard shortcuts for Atom and Google Play Music ran into a conflict, in as much as I wanted to trash my GPM shortcuts and use those for Atom. Go into Chrome to unbind them in the keyboard shortcuts section of the extensions window.. except Google yanked the ability to set keyboard shortcuts for GPM from the list, presumably in anticipating of killing it entirely in favor of YouTube Music. So I guess I need to entirely uninstall Chrome in order to unbind those keyboard shortcuts.
|
# ? Nov 18, 2019 23:24 |
|
|
# ? Apr 24, 2024 10:44 |
|
Cabbit posted:So my keyboard shortcuts for Atom and Google Play Music ran into a conflict, in as much as I wanted to trash my GPM shortcuts and use those for Atom. Go into Chrome to unbind them in the keyboard shortcuts section of the extensions window.. except Google yanked the ability to set keyboard shortcuts for GPM from the list, presumably in anticipating of killing it entirely in favor of YouTube Music. You need to got to about :flags (without the space the forums software adds) and disable "Hardware Media Key Handling"
|
# ? Nov 18, 2019 23:51 |