RetroFed Forum
Your home away from modern life.
Search Categories Forum list Register Log in
About RetroFed
RetroFed

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

  • Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
  • Communities need to be Retro or Retro-adjacent.
  • Please don't upload pornographic content. (use an external image host for that)
72 registered users
Administrators: DosDude, Die4Ever
Visit retrofed.com
Chrome manifest v2 workaround 202509 v140
Post Reply RetroFed Forum Forum Index » jet's interesting finds
AuthorMessage
jet hackertalks.com jet@hackertalks.com
Joined: 2023-07-06
Quote

chrome v140+ now needs command line args when launching

  • --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

Building on our last workaround post https://hackertalks.com/post/13751580

and stealing from: https://superuser.com/questions/1917854/is-there-any-way-to-still-use-manifest-v2-extensions-in-google-chrome-139
1   Original
Post Reply
Back to top
Powered by PieFed · PieBB frontend · All times are Europe/Amsterdam