|
Max Wilco posted:I've run into a weird issue with Firefox and YouTube. Typically, when I opened an video in a new tab, the video will not start until I click play, and from there, any video I navigated to from that tab would play automatically. Do you have autoplay with sound disabled?
|
#
?
Apr 25, 2020 20:31
|
|
|
|
| # ? Apr 17, 2024 00:08 |
|
|
astral posted:Do you have autoplay with sound disabled? I do. The permissions in the address bar setting is set to 'Block Audio'. I can toggle it to 'Allow Audio and Video'. The catch is that I can open a video in a new tab, but once I click to that tab, the video will start playing automatically. I suppose I could just toggle it on-and-off as needed (for the most part, I play YouTube video in a private browsing wIndow, and it doesn't seem to retain the settings), but it's odd, since I recall I could open a video in a new tab without it automatically playing, but any new video I clicked on within that tab would play automatically. Max Wilco fucked around with this message at 21:29 on Apr 25, 2020 |
|
#
?
Apr 25, 2020 21:24
|
|
|
Max Wilco posted:I do. The permissions in the address bar setting is set to 'Block Audio' Add an exception for youtube to allow audio and video.
|
|
#
?
Apr 25, 2020 21:28
|
|
|
Check your media.block-autoplay-until-in-foreground about :config setting.
|
|
#
?
Apr 25, 2020 21:35
|
|
|
astral posted:Check your media.block-autoplay-until-in-foreground about :config setting. Where would that be located? EDIT: Oh, I just type about :config in the address bar.  It's set to 'True' EDIT2: Tried tweaking it a bit, but still not getting the desired result. I wonder if it's something YouTube changed? Max Wilco fucked around with this message at 21:58 on Apr 25, 2020 |
|
#
?
Apr 25, 2020 21:36
|
|
|
Max Wilco posted:I've run into a weird issue with Firefox and YouTube. Typically, when I opened an video in a new tab, the video will not start until I click play, and from there, any video I navigated to from that tab would play automatically. Sounds like one of your YouTube addons is breaking it. The block autoplay in Firefox was designed with playlists in mind. Once there has been a user action on a page, it doesn't block subsequent videos.
|
|
#
?
Apr 26, 2020 10:43
|
|
|
Applebees posted:Sounds like one of your YouTube addons is breaking it. The block autoplay in Firefox was designed with playlists in mind. Once there has been a user action on a page, it doesn't block subsequent videos. That was it. The problem was the YouTube Classic add-on. Once that was disabled, I could open videos in new tabs without them playing unless I started them, and videos navigated to from the current tab or in a playlist will play automatically. Thank you. Of course, now the issue now is that YouTube+ doesn't work with the new layout, and it sounds like it isn't going to be supported anymore (or at least it's going to be a while until the new version is stable).
|
|
#
?
Apr 26, 2020 12:23
|
|
|
I would like to promote the plugin "Request Control" because it has been a major help in correcting some of the new and innovative ways that big tech is making the internet suck via URL parameters. It can replace multiple different plug-ins and greasemonkey scripts in one place, with a (sort of) simple regex-based rules system, and more transparency about what it's doing. For example, forcing twitter to always show you the original image looks like this: Host: *.twimg.com, pbs.twimg.com Path: * Rule: {href/name=[a-z0-9]+/name=orig} And forcing old reddit looks like this: Host: reddit.com, https://www.reddit.com Path: * Rule: [protocol=https][hostname=old.reddit.com] By default, it comes with rules to disable google's link tracking and always remove UTM parameters. It has become indespensible for me in making the internet blow less and fixing ublock's blind spot with url tracking.
|
|
#
?
Apr 26, 2020 18:28
|
|
|
Max Wilco posted:Of course, now the issue now is that YouTube+ doesn't work with the new layout, and it sounds like it isn't going to be supported anymore (or at least it's going to be a while until the new version is stable). Looks like the new version of that extension is at https://github.com/ParticleCore/Iridium
|
|
#
?
Apr 26, 2020 21:17
|
|
|
Applebees posted:Looks like the new version of that extension is at https://github.com/ParticleCore/Iridium Oh, cool. Thanks!
|
|
#
?
Apr 27, 2020 01:46
|
|
|
larper posted:I would like to promote the plugin "Request Control" because it has been a major help in correcting some of the new and innovative ways that big tech is making the internet suck via URL parameters. Applying simple regex to the problem is a much better solution, though  Especially because that's what they were made for.
|
|
#
?
Apr 27, 2020 10:30
|
|
|
This pisses me off: The new internet explorer. loving hell, Firefox supports all the standards needed to join, make and participate in an online meeting. WTF are you microsoft people doing there that requires Chrome? My hunch is that nothing, but you're just too drat loving lazy to test.
|
|
#
?
Apr 28, 2020 01:07
|
|
|
If it uses WebRTC Firefox has (from what I understand) a lot of bugs and unimplemented features which can cause interoperability issues with Chrome. Most of those bugs have workarounds, but it's just easier to ban Firefox. That said, Mozilla has been prioritizing fixing those bugs recently (I wonder why  ) so hopefully web conferencing software will stop blocking Firefox when they can get around to retesting everything with newer FF versions (because that's totally what they'll do, right?  ).
Mr.Radar fucked around with this message at 01:18 on Apr 28, 2020 |
|
#
?
Apr 28, 2020 01:15
|
|
|
Mr.Radar posted:If it uses WebRTC Firefox has (from what I understand) a lot of bugs and unimplemented features which can cause interoperability issues with Chrome. Most of those bugs have workarounds, but it's just easier to ban Firefox. That said, Mozilla has been prioritizing fixing those bugs recently (I wonder why From my experience with WebRTC on both Firefox and Chrome they both work just fine. Now, granted, I have not developed a video chat application, so it can be that these apps have some other weird requirements that hits these Firefox bugs, but I have not hit them with my applications. I'm quite convinced they're just drat lazy and took the easy way out.
|
|
#
?
Apr 28, 2020 01:46
|
|
|
You could try changing your user agent and see if it works. That's one good way to test if it's just that they are too lazy to test.
|
|
#
?
Apr 28, 2020 12:56
|
|
|
If you, like me, wanted to invert SA's favicon when your OS and/or Firefox ui.systemUsesDarkTheme setting is set to dark mode, here's some userChrome.css for you:code: e2 for bonus before pic:  e3: tweaked the invert to be 0.8 instead of 1.0 so it's a little less harsh:  astral fucked around with this message at 08:01 on Apr 29, 2020 |
|
#
?
Apr 29, 2020 03:38
|
|
|
Is there any addon that lets me open a big folder of bookmarks and have them only start loading once I switch to the tab? It's nice and all that Firefox warns when opening more than 25 tabs about how it might get all slow from opening so much stuff at once, but it'd be nicer if I didn't end up having to refresh tabs at the end of the row because they got 429'd (or worse yet, the server refuses all my requests for the rest of the day because I hit its rate limit). Tab Mix Plus (  ) could do it. And firefox can already kinda do it if you undo closing a window, but that requires having had it open first.
|
|
#
?
Apr 30, 2020 22:51
|
|
|
Does anyone have issues with Google Sheets? When entering a formula, the plus sign might suddenly stop working, and other character presses get messed up as well.
|
|
#
?
May 1, 2020 07:59
|
|
|
I literally just went in to punch in some bills and when typing more quickly than glacial the keystrokes get interpreted in the wrong order.
|
|
#
?
May 1, 2020 09:25
|
|
|
Any way to turn off the password prompt for show password in the new Firefox?
|
|
#
?
May 6, 2020 00:26
|
|
|
Anyone else using Live Stream Notifier just have it break? On the market for a fix or some kind of alternative.
|
|
#
?
May 7, 2020 16:32
|
|
|
Just make me miss RSS. 
|
|
#
?
May 7, 2020 18:40
|
|
|
Firefox has notified me that PIP now supports double clicking to make it fullscreen.
|
|
#
?
May 7, 2020 19:38
|
|
|
That's cool. Media playback still belongs in a program built for media playback, not in something with more lines of code than an OS. Admittedly, it does seem like Firefox wants to be an OS, considering they brought in a fork of FreeBSDs jemalloc and have been "optimizing" the hell out of that without upstreaming any of the code. It also seems they think they know better about how memory optimizations should work regardless of the fact that they're making software for at least 3 completely and radically different virtual memory subsystems which all behave in different ways, and support way more, including one that's based on the allocator they took. Case in point, they decide to automatically use ALL available threads on a system to do CPU cache/area multiplex optimizations, rather than the default which is "only" four times the number of CPU threads. Nowhere is it described why this was chosen, nor how and/or if it actually makes a difference - probably because to show the difference statistically, they'd have to do ten consecutive runs and recompiling twice takes a loving week using high-core-count build servers with almost 200GB memory to build their 20 million lines of code Funnily enough, if you disable Firefox memory caching and use disk caching on FreeBSD, Firefox runs substantially better. BlankSystemDaemon fucked around with this message at 22:31 on May 7, 2020 |
|
#
?
May 7, 2020 21:36
|
|
|
D. Ebdrup posted:That's cool. In an ideal world media playback is in a separate application, but we're living in reality where users expect things to just work even despite whatever customizations the website has done to their playback. Mozilla bringing in a fork of an established memory manager makes perfect sense considering they're running a VM for all the JavaScript which is hogging all the memory. That it's a totally different memory manager than the OS is using is irrelevant; that VM is a big black box of a process as far as the OS is concerned. It's not the operating system's job to manage memory inside a process. Regarding thread usage, are you sure it isn't your custom build loving things up again? Not saying Mozilla can't gently caress it up, but you've already demonstrated how a lack of config files at compile time leads to problems...
|
|
#
?
May 8, 2020 02:30
|
|
|
isndl posted:In an ideal world media playback is in a separate application, but we're living in reality where users expect things to just work even despite whatever customizations the website has done to their playback. mmap() is a system call telling the kernel to give a program an amount of memory that it can operate with, by definition that means it's up to the kernel to manage all of the memory mappings from the different processes Firefox spawns and therefore manage the memory. If Mozilla wants to do a proper hypervisor using VT-x/AMD-V and SLAT with its own DRAM management which gets taken away from what the host OS has access to and (thin-)provisioned, that's fine but that's demonstrably not what they're doing - and I suspect they won't, because then they're responsible for the security of the hypervisor too, or would have to rely on something like virt-manager (as a library) to talk to all the different hypervisors an all the systems they support (Hyper-V, KVM, Xen, QEMU, bhyve, vmm, nvmm, and so on and so forth). I'm talking about the default values that Mozilla ship. I assume you're talking about this build config? Those are port-defaults, set by jbeich who has been managing the builds for Firefox on FreeBSD since 2012 when Firefox was still version 13 - and who was involved with the malloc issues. Ultimately the build config dates back over the mozilla-firebird port all the way to the phoenix port in 2002, that was described like this: "Phoenix is a fast, minimal browser from the Mozilla project". BlankSystemDaemon fucked around with this message at 11:06 on May 8, 2020 |
|
#
?
May 8, 2020 10:38
|
|
|
 I am old and hate change. I really dislike the new twitter. Is there any way of keeping the old version?
|
|
#
?
May 9, 2020 09:42
|
|
|
I'd like to know too. I don't mind change if it's a good change but the new Twitter is complete dogshit.
|
|
#
?
May 9, 2020 13:28
|
|
|
They've broken me and I kinda like new Twitter after 12 hours since it's not being actively sabotaged.
|
|
#
?
May 9, 2020 14:10
|
|
|
My favorite feature is how they removed the little notification thing from the tab Twitter was open in, followed by a billion tweets loading once you glance at the page and you have to scroll down to read the ones you missed instead of scrolling up to get to the newest one right away.
|
|
#
?
May 9, 2020 14:46
|
|
|
D. Ebdrup posted:Except we wouldn't have these problems if people followed the standards, which make it quite simple to implement a third party video player (and a program to pipe the HLS or DASH stream to it) - but webdevs have decided they control the entire stack down to (remote, usually minified, and not signed - and definitely not trusted) assembly code that gets JIT'd to machine code, and therefore get to change APIs arbitrarily and on a whim. Keep in mind that piping everything out to a plugin to handle was how we ended up in the quagmire that was Flash, and understandably nobody wants to go back to that. The current system is imperfect but it works out of the box for the average user, and the major browser developers have been far better at keeping on top of security issues than plugin developers. Firefox makes a system call to be assigned memory for use, but FF is expected to manage that memory itself hence why they implemented a memory manager to cut down on fragmentation. Tabs share processes in FF, so when one tab starts bloating they need to be able to shrink it back down without nuking the other tabs. I don't know if they're doing anything security-wise with the custom memory manager, but given the surge of interest in memory based attacks like Rowhammer in recent years I wouldn't be surprised; I know some of them were mitigated at the browser level without requiring OS patching. I don't compile my own Firefox installs so I don't know how the build configs should look, but if you're sure that the default settings are at fault (and that precompiled releases suffer from the same performance issues you're observing), you should feel free to submit a ticket to get that fixed. My gut instinct is that if your installation has one setting missing there's probably others as well but you know your build better than me. 
|
|
#
?
May 9, 2020 14:55
|
|
|
Stare-Out posted:My favorite feature is how they removed the little notification thing from the tab Twitter was open in, followed by a billion tweets loading once you glance at the page and you have to scroll down to read the ones you missed instead of scrolling up to get to the newest one right away. My favorite feature is how you have to actually click on a tweet to save an image from it in full res, which you didn't have to before. Or how now there's no way to circumvent having likes show up. I gave tweetdeck a shot and I think I actually hate this more than new twitter? At lest new twitter has a relatively large column for stuff to show up in, this is just way too cramped, and is crammed full of even more screenwaste stuff. I feel like there's really no option anymore for just seeing only what the people you follow actually tweet out, in chronological order, in a large format not cluttered with notifications or trending poo poo.
|
|
#
?
May 9, 2020 19:30
|
|
|
Jippa posted:
For me it also started just hiding the whole tweet stream by adding some random attribute to the stream container and then adding a css rule like [qhwekqhj] { display none; } I made a user javascript that watches the stream for attribute changes and removes everything that is not "id" or "class", lol edit: I know random attributes and classes like that are some bullshit react CSS-in-JS thing and I know that the new twitter uses react, so
|
|
#
?
May 9, 2020 19:47
|
|
|
Stare-Out posted:My favorite feature is how they removed the little notification thing from the tab Twitter was open in, followed by a billion tweets loading once you glance at the page and you have to scroll down to read the ones you missed instead of scrolling up to get to the newest one right away. That's variably functional at best with the old format these days, but it was definitely the reason why I found a way to switch back at first.
|
|
#
?
May 10, 2020 03:09
|
|
|
Wheany posted:For me it also started just hiding the whole tweet stream by adding some random attribute to the stream container and then adding a css rule like [qhwekqhj] { display none; } Oh well, it turns out that mutationobservers fire after the attribute has been inserted so now my timeline just blinks in and out of existence and I can't find the actual stule declaration anywhere in the dom inspector or the css tab because as it turns out, firefox's developer tools are actually kind of poo poo. (the css tab has no "find in all files" as far as I can tell) I was thinking maybe I could maybe just remove the stylesheet completely. I guess Twitter wins
|
|
#
?
May 10, 2020 11:16
|
|
|
Jippa posted:
isndl posted:Keep in mind that piping everything out to a plugin to handle was how we ended up in the quagmire that was Flash, and understandably nobody wants to go back to that. The current system is imperfect but it works out of the box for the average user, and the major browser developers have been far better at keeping on top of security issues than plugin developers. I would like to think there's some sort of lee-way between NPAPI and flagrantly ignoring open web standards? They could have complete control if they went with the libvirtmanager that I outlined. Why settle for less? They're not performance issues I'm seeing, it's memory bloating beyond what's reasonable. Something Firefox is less-bad about than Chrome, but in degree not in kind. Anyway, I was mostly just ranting. Since I switched to putting caching "on disk", everything is great. On-disk in this instance means ZFS ARC, which has been optimized by both Sun VM people as well as FreeBSD VM people.
|
|
#
?
May 10, 2020 19:58
|
|
|
I hadn't checked out Tweetdeck in a few years now but I see it still has no real understanding of what "wide column" means.
|
|
#
?
May 10, 2020 20:29
|
|
|
I've tried tweetdeck a few times over the years, and I can't imagine using it in a case where riding herd over multiple feeds isn't part of your job duties. I really miss the third-party apps where I could have a tiny little ticker tucked away in a corner of one monitor. That was my ideal use case.
|
|
#
?
May 10, 2020 20:33
|
|
|
Mine too. The original (now long-dead) Twitter app for Mac was really simple and played really well with notifications. No such luck for PC though. Too much to ask for new tweets to pop up in the corner of my monitor for a few seconds before fading away I guess.
|
|
#
?
May 10, 2020 20:35
|
|
|
|
| # ? Apr 17, 2024 00:08 |
|
|
Stare-Out posted:I hadn't checked out Tweetdeck in a few years now but I see it still has no real understanding of what "wide column" means.
|
|
#
?
May 10, 2020 22:29
|
|