Technology

59414 readers

2747 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

1064

Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com)

submitted 5 months ago by [email protected] to c/[email protected]

358 comments fedilink hide all child comments

Reminder to switch browsers if you haven't already!

Google Chrome is starting to phase out older, more capable ad blocking extensions in favor of the more limited Manifest V3 system.
The Manifest V3 system has been criticized by groups like the Electronic Frontier Foundation for restricting the capabilities of web extensions.
Google has made concessions to Manifest V3, but limitations on content filtering remain a source of skepticism and concern.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 5 months ago* (last edited 5 months ago) (1 children)

haha Safari would like a word.

[–] [email protected] 4 points 5 months ago (1 children)

What word? I spoke the truth: there are only two rendering engines. The only reason Safari/WebKit isn't considered a fork of Chrome/Blink is that Chrome/Blink is a fork of Safari/WebKit instead.

[–] [email protected] 5 points 5 months ago* (last edited 5 months ago) (1 children)

I deleted my original comment before you replied because I am not really in the mood to defend this but the OP was talking about the pain of developing for different browsers and I don't care what is a fork of what, this is a fact: Chrome, Firefox and Safari all render differently and have to be catered to individually.

Also, Safari, between desktop and mobile, has 30% of the market to Firefox's 8%.

I don't LIKE it, but there are "effectively" three, not two, rendering engines.

[–] [email protected] 1 points 5 months ago (3 children)

It's about browser architecture and not silly names ("Safari", "Firefox", "Chrome"). The point is that there are only two actual variants.

[–] [email protected] 4 points 5 months ago

Not when you have to make a web app render identically in them, which is what the OP was about.

[–] [email protected] 2 points 5 months ago

No, you still have three rendering engines. WebKit and Blink are different. Since the second is an (old) fork of the other one, they are similar but far from being the same. They are pages that work in one but not the other, even if you change the user agent.

[–] [email protected] 1 points 5 months ago

That's...not true at all.