That is a fascinating image. It lets you see how color information is encoded in video. The vertical green bar is a glimpse of the luma (Y) channel. To the left is the chrominance blue (Cb) and to the right is the chrominance red (Cr). But the chroma channels are (obviously) supposed to be aligned with the luma, yielding full color video. Unfortunately, I can't offer a suggestion why they aren't aligned.
You can have two separate profiles, and two different task bar shortcuts that open up the different profiles. They'd essentially store different user data like history and bookmarks and previously opened tabs, and you could have a music profile and work profile. I did this for work at one point in my life. One helpful thing was making sure they each had different theming to be visually distinct so I could keep track of where to open things.
If you want different shortcuts, use the following command in your .desktop file (assuming you use Linux): firefox -no-remote -P <profilename>
for example, assuming you named your music profile music, you put the following line in a firefox-music.desktop file you'll create in ~/.local/share/applications/:
Exec=firefox -no-remote -P music (in addition to other common .desktop file fields)
If your firefox executable is not located in your $PATH (for example if you downloaded it directly from Mozilla), then you need to put the path too. for example: Exec=~/apps/firefox/firefox -no-remote -P music
Edit:
here's a full .desktop file example for a profile named "work":
file path and name: /home/confusedllama/.local/share/applications/firefox-work.desktop
Content:
[Desktop Entry]
Name=Firefox for work
GenericName=Web Browser
Exec=/home/confusedllama/apps/firefox/firefox -no-remote -P work
Icon=/home/confusedllama/apps/firefox/browser/chrome/icons/default/default128.png
Terminal=false
Type=Application
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
StartupNotify=true
Categories=Network;WebBrowser;
Name[en_US]=Firefox for work
Actions=new-window;new-private-window;
[Desktop Action new-window]
Name=Open a New Window
Exec=/home/confusedllama/apps/firefox/firefox -no-remote -P work -new-window
[Desktop Action new-private-window]
Name=Open a New Private Window
Exec=/home/confusedllama/apps/firefox/firefox -no-remote -P work -private-window
This example will give you "Open a new window" and "Open a private window" options too, when you right click on the shortcut. Also as you can see, you can even set a different icon for each shortcut.
You could do the following to improve things somewhat:
type about:config into the address bar
read and accept the warning
type browser.tabs.tabMinWidth into the search field
set value to 0
It will let you open a lot more tabs before scrolling away, but stll not an infinite amount.
Now what’s keeping you from getting arbitrarily narrow tabs are the icons displayed on them.
Removing them is more difficult:
Type about:config into your address bar. Promise you’ll be careful and proceed. Now type toolkit.legacy into the search bar on the about:config page and hit enter. Look for an option named toolkit.legacyUserProfileCustomizations.stylesheets and click the toggle on the far right side to set this option to true.
Type about:support into your address bar. Follow along the left side of your screen until you see a row titled Profile Folder. Directly to the right of this you should see an Open Folder button. Click on this.
A window should launch in Windows File Explorer that will navigate to your Firefox profile’s folder. Go ahead and create a new folder inside this profile folder. You can do this by either clicking the new folder icon in the top left or by using the keyboard shortcut, CTRL + Shift + N. Rename this new folder as “chrome” (do not include the quotation marks and ensure all letters are lowercase). Open this new chrome folder.
Right click in the empty space inside the folder, click on new, and click on Text Document. Now open this new text file. Copy and paste the following into it:
Click on ‘File’ in the top left and then ‘Save As…’. Towards the bottom of the file save window, change the name of the file to “userChrome.css” (once again, do not include the quotation marks and ensure everything is lowercase except the ‘C’ in ‘Chrome’).
Underneath the File Name box, you’ll see a Save as Type box that should currently be set to Text Documents (*.txt). Change this to All Files. Click on Save. Now go back into Firefox and type about:profiles into your address bar. Click on the Restart Normally… button in the top right corner of the page.
I’m using Floorp, a Japanese open source fork, since a week. Much better than vanilla Firefox, you can give it a try: github.com/Floorp-Projects/Floorp
That tab you are hovering is “special” (because it has a protected domain addons.mozilla.org, there are a couple of them ) addons can not inject content so i assume generating a screenshot also wont work here.
Also the addon wont be able to generate previews if the tabs are discarded, so the tabs need to have been active at least once in the current sessions, otherwise there also wont be a preview available.
Well … in my case the hover cards dont show up at all. The tab image generation seems to work, from what i can see when i debug the capture loop, so i assume there is some issue with the CSS theme.
Kind of a big update... this is the last version of Firefox for Windows 7 and Windows 8, along with macOS 10.12, 10.13, and 10.14. I know this is forcing family members to finally upgrade their (mac) OS.
More big updates:
Hardware video decoding is now enabled for Intel GPUs on Linux.
We've refreshed and streamlined the user interface for importing data in from other browsers.
The builtin editor now behaves similarly to other browsers with contenteditable and designMode when splitting a node, e.g. typing Enter to split a paragraph, and also when joining two nodes, e.g. typing Backspace at the start of a paragraph to join the paragraph and the previous one.
Pretty sure that last feature is what finally fixes the Reddit Fancy Pants editor in Firefox... exactly when Reddit is destroying itself.
IndexedDB is now also supported in private browsing without memory limits thanks to encrypted storage on disk. The temporary keys to decrypt the information are hold in RAM only and all stored information is purged at the normal end of a private browsing session from disk.
This might help WhatsApp web run in private browsing, among other sites.
The most impactful thing is definitely going to be OS compatibility... this is going to be the last version of Firefox for a long time for a lot of people.
I know it says the extension is not available from the Firefox addon site if using Russian IPs, but I wonder if they have also gone so far as to make the browser itself not be able to install them in other ways. I would guess they have not, since that would mean a complicated setup in terms of the signatures, like they would have to have a separate FF version and set of signatures per country, or use a central server to authenticate things rather than client validation of signatures. In that case it would be easier to find the addon file somewhere other than the store and install it, since using unsigned addons requires installing a whole separate version of Firefox.
Even if that's how it is this whole thing still illustrates that prohibiting unsigned addons from being installed is user-hostile, because on an ideological level Mozilla probably would use that power to advance state censorship if it came down to it.
Ah yeah, true, getting just the signed XPI should work as well.
And well, it is tricky. The signing requirement allows them to block malicious add-ons, which could also be used for state censorship.
I think, offering a separate path for people to install unsigned extensions, if they need it, while blocking them for the majority and therefore making them inviable for malware to target, that's in principle a smart compromise.
Also, side-note: Folks who are on Linux likely don't need to install a separate version of Firefox. Linux distros tend to compile with the unsigned extension support enabled (just need to toggle the flag in about:config).
I guess in this case the malware angle means it's probably better to require signing, since maybe Russia could successfully distribute malicious fake versions of these extensions otherwise. Still, the centralization here is worrying.
Mozilla is bending the knee to Russia? Is this real life? Have we stepped into an alternate timeline? Whats going to happen to all the psycho FireFox users when they find out this happened, will they stop screaming at everyone to use FireFox?
I'm not sure what you expect to happen. If they don't do this, Russia will ban Firefox. And I do think, it's better for the Russian people to have Firefox available, even if it bends its knee in certain situations. Because I'd wager the alternatives proactively stick their tongue up Putin's.
our end goal is to make it available in general browsing for users with screen readers.
So obviously the people working on it know that the appropriate place for this stuff is in the screen reader, and/or in software that is designed for producing web pages. Who made the decision to cram it into the Firefox PDF editor instead, and why? Is anyone actually using that when they want to create a new PDF document? Is it just for PR reasons so they can claim there's AI in Firefox now? To impress us, or to make way for more of the same? What is actually going on Mozilla?
But anyway it's a difficult problem, as the example image suggests. It'll be interesting to see how much progress they make.
I don't know why, but I feel like putting the new experimental feature in your niche use first, possibly where alt text barely exists with how people generate pdfs, so getting feedback is to a specific audience who need it most while impacting nearly everyone else, does seem like a logical first step.
I got to compare that to Google, who put it front and centre of their namesake product.
firefox
Popular
Esta revista es de un servidor federado y podría estar incompleta. Explorar más contenido en la instancia original.