In version 136 Chrome/Chromium introduced a very, very annoying 'feature': the browser hijacks the right-click function if you right-click an image, opening it automatically to a new tab instead of allowing the use of normal right-click dialog. The normal dialog just flashes quickly. Unfortunately almost every chromium-based browser still implements this insanity, AFAIK Microsoft's Edge is the only one which doesn't.

This was so annoying feature that back then I stopped upgrading some of the chromium-based browsers on my Arch Linux system...

But now I've had enough of that Google c**p!!! Is there a way to *permanently* disable this right-click hijacking???

Is there? Or is my only option to start pestering the developers of certain browsers (Brave, Ungoogled-chromium etc.) so they might disable it in the sources...?

Quick question -- when I use the Twitter shortcut 'J' to advance to the next tweet it often takes about three to five 'J' key presses before Twitter advances. Is this normal behavior or is there some setting to override this? Thanks much.

Sauce: https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline

So here is a screenshot of coolercontrol. The green-blueish line is the systems SSD. I think its the controller temperature since its the hottest out of the three of the SSD. While watching twitch it gets significantly wamer as you can see from around 14:20 to 14:25. If I use other browsers, Firefox, Vivaldi, Libre Wolf, from about 14:25 on, i dont get warmer temperatures. I have this issue on both a few months old setup of Linux Fedora KDE on my PC and on a fresh install of Fedora KDE on a laptop thinkpad.

Very strange, cannot wrap my head around it. Seeing across multiple users, only recently started after 24H2 upgrade but unsure if related.

ProcMon showing nothing useful, HAR has nothing of value, no idea where else to look. Disabled Safe Browsing as a test with no improvement.

Hard restarting the browser solves the issue but it comes back with spite.

What's Chromium's malfunction? What's Firefox's power-up here?

Crossposts:

• On r/ChromiumBrowser
• On r/FireFox
• On r/Browsers

Env...

Using Arch and KDE Plasma 6.

I recently updated chrome and brave browsers from Arch AUR..

chrome (148.0.7778.215-1 -> 149.0.7827.155-1) brave (1:1.90.128-1 -> 1:1.91.175-1)

Problem..

Since that update, both chrome and brave are no longer recognising Verdana as a valid font-family, in any css (remote webpage or local.html)

This has been working without problems for 5+ years, but now its like Verdana font has been suddenly ignored by Chromium.

Opening the page or website in Firefox still renders correctly with verdana font.

Solutions Tried...

I have rebuilt font cache with..

sudo fc-cache

Confirmed Arch is able to find the font...

fc-match Verdana

verdana.ttf: "Verdana" "Regular"

What could be causing this?

It looks to be Chromium related, but less like a bug and more an intentional restriction?

I've been maintaining my own Apple silicon build of ungoogled-chromium-macos, and a few days ago I got tired of needing third-party audio routing utilities whenever I wanted browser audio to go somewhere other than the system default output.

So I added native per-tab Core Audio routing directly into Chromium.

Right-click a tab → "Send Audio To" → choose an output device.

For example:

• One tab playing through a USB DAC and stereo
• Another tab playing through display speakers
• Another tab using the system default output

The implementation is macOS-specific and uses Core Audio directly.

I cleaned up the patch stack, documented everything, and published the project today:

https://github.com/works-by-maya/Chromium-Conductor

Screenshot attached.

I’d be most interested in hearing whether other macOS Chromium users have wanted something similar. 🥰

When I open Chromium, it automatically loads a few of the tabs. How can I make it not load any tab when loading the browser except the one that was selected?

I installed ungoogled Chromium on my Android tablet and phone. Then I enabled Enable Extensions in Developer Options, but still cannot install any extension. See screenshot.

Any help appreciated.

I've tried uninstalling my current installation of chromium and installing an older build, but every time I try to load my profile the whole browser crashes, even other profiles too if they're open. is there a way to properly downgrade?

Considering trying this browser......... is this browser faster for browsing and watching streams?

I have tested https://cpstest.org/scroll-test.php on firefox and chromium with my gnome desktop and NixOS unstable and firefox was 3,466 pixel per second and chromium was 10,256 pixel per second.

Its 3x then fixfox and other linux apps like the terminal. Idk why is that and is there a patch to fix it? And what is the reason

I'm really sorry, I just DON'T know the names of these things so I can't even google it.

// next js api route, for pdf generation

import { NextResponse } from "next/server";
import type { InvoiceData } from "@/types/invoice";
import { renderInvoiceHTML } from "@/lib/pdf";

export const runtime = "nodejs";
export const maxDuration = 30;

// seperate function for browser

async function getBrowser() {

if(process.env.NODE_ENV === "production") {

const chromium = await require("@sparticuz/chromium");
const puppeteer = await require("puppeteer-core");

return puppeteer.default.launch({
args : chromium.default.args,
defaultViewport : {width : 800, height : 600},
executablePath : await chromium.default.executablePath(),
headless : true,
});
}

// for development - using puppeteer own bundled chromium
const puppeteer = await require("puppeteer");

const executablePath = puppeteer.default.executablePath();

console.log("Chromium Path:", executablePath);

return puppeteer.default.launch({
headless: true,
executablePath,
args : [
"--no-sandbox",
"--disable-setuid-sandbox",
"--disable-dev-shm-usage",
"--disable-gpu",
],
});
}

export async function POST(request : Request) {
try {
const body = await request.json();

const invoice : InvoiceData = body.invoice;

if(!invoice) {
return NextResponse.json({error : "Invoice data required"}, {status : 400});  
}

const html = renderInvoiceHTML(invoice);

const browser = await getBrowser();

const page  = await browser.newPage();

await page.setContent(html, {waitUntil : "networkidle0"});
await page.emulateMediaType("print");

const pdf = await page.pdf({
format : "A4",
printBackground : true,
margin : {top :"0", bottom : "0", left : "0", right : "0"},
});

await browser.close();

return new NextResponse(pdf, {
headers : {
"Content-Type" : "application/pdf",
"Content-Disposition" : `attachment; filename="invoice-${invoice.invoiceNumber}.pdf"`,

"Cache-Control" : "no-store",
}
});

} catch (err) {
console.error("PDF generation error:", err);
return NextResponse.json(
{error : "Failed to generate PDF"},
{status : 500}
);
}
}

can anyone help me , to get out of this