M
For older devices I’d downscale to 1080p, since many of them can’t decode 4K H.264 at all. With software x264, an RF around 18-20 with the medium or slow preset is a common starting point, plus 8-bit and the High profile at level 4.1 for compatibility. For audio, stereo AAC at about 160 kbps works nearly everywhere. Hardware encoders (NVENC/QuickSync) are much faster, but as far as I know x264 in software still gives smaller files at the same visual quality, so it depends on whether you care…
M
Yeah kind of one of the reasons why I moved away from using Mozilla and using Chrome as my daily, but some of my users are mozilla userbase and wanted to support them. I just hope my addon doesn’t become one of these stories of waiting months.
M
I have the same issue. Checked, no emails from Mozilla notifying me of a suspended or banned account. Please help me!
M
Thanks for the screenshots. A good way to see what Firefox is actually running is to type about:processes in the address bar, which opens Firefox’s built-in task manager. It lists every process with its type, the tabs or pages it hosts and its CPU and memory use, so you can tell whether a given process belongs to a page you have open or is an idle spare process. Firefox normally keeps a spare content process around to make opening new tabs faster, and that shows up as a process that isn’t tied…
M
Hi @plan291037, I’m just another user, so I can’t lift an account block, but here is what usually moves these cases forward. Since the disablement decision can’t be appealed through the Developer Hub, the next step is to email the AMO admins (the notice you received normally lists the contact address, often amo-admins@mozilla.com) from the same address as your developer account, and quote the decision ID and your add-on slug in the subject line. In that email, explain briefly what the corrected…
M
Nova’s toolbar chrome changes make a lot of older theme CSS assumptions break in small ways like that hairline under the toolbar. Building on mozchris’s note about toolbar_bottom_separator, it’s worth testing a fully opaque value matching your toolbar or frame color in the manifest.json colors, since semi-transparent values seem to be what lets the lighter background show through. If it still reproduces with a minimal theme, posting the toolbar / frame color keys you use can help others confirm…
M
Your CSS looks correct, and Firefox has supported the range syntax (width < 550px) since version 63, so this isn’t a Firefox bug. The most likely cause is Responsive Design Mode’s touch simulation: when it’s on, Firefox behaves like a mobile browser, and a page with no viewport meta tag gets laid out at a default width of about 980px, so the (width < 550px) rule never matches no matter how narrow you make the frame. Add this line inside the of your HTML file: and reload. Alternatively, turn off…
M
Make sure you are running the latest version of Firefox and also see if the developer has published an updated version. If the issue still persists, read the whole guide here.
M
Hoping it doesn’t go into three weeks plus
M
The MDN documentation for addEventListener() and the general guide on events are indeed the best places to find this information. Specifically, the “Event objects” section in the events guide and the “The event listener callback” part of the addEventListener() reference explain that the browser automatically passes an Event object to the handler function. This object contains details about the event that occurred, which is then accessible via the parameter you define (like e or event).
M
Hello AMO team, My add-on “TextPhantom — แปลข้อความในภาพมังงะ มังฮวา” was force-disabled as “Deceptive or misleading” (decision 01a1400d-7e36-78c0-a228-8ca663358f7c, which cannot be appealed). Since then my developer account shows “The email address used for your account is not allowed for submissions”, so I cannot upload a fixed version or submit anything. The disablement did not say which part was deceptive. I reviewed the Add-on Policies and changed the extension (version 2026.10.16.2) to…
M
As far as I know, that’s right: the tabGroups API only exposes groups that are currently open in a window. Saved-and-closed groups aren’t queryable from extensions yet. A workaround is to track groups yourself: listen for tabGroups.onRemoved (and tab events) and store the group title and tab count in storage.local before it closes. It’s worth filing a request on Bugzilla under WebExtensions: General for read access to saved groups.
M
The distinction Keith is drawing between “age” and “date of birth” is technically correct, but it’s worth thinking through how the data actually behaves over time. Age at the time of recording is a snapshot value. It’s accurate only relative to the recording date, and if the metadata doesn’t include when the recording was made, the age value alone is ambiguous. A contributor who recorded at 34 in 2019 is 39 now. If the dataset only stores “34” without a timestamp, downstream users have no way…
M
Amazing! Here’s a published Firefox extension as well. This one also helps to alter the number of closed windows and tabs recoverable, as well as the maximum duration after which closed windows are forgotten.
M
Thank you please, I would like to contribute as an AI Engineer, is there a way I can help in that regard?
M
Hello, I’m currently at the section “Getting started with CSS” where they teach about at-rules. I’m trying the following code example: @media (width < 550px) { body { background-color: rgb(179, 255, 0); } } @media (width >= 550px) { body { background-color: rgb(255, 153, 0); } } Warning: Flashing lights/colors in the gifs! Seems to work as expected with Visual Studio Code’s “Live Preview” extension. VSCode Live Preview GIF (click for more details) Does not work with Firefox’s “Responsive Design…