Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organic repeatable queries is missing. #1647

Open
4 tasks done
GitAlasGo opened this issue Nov 17, 2024 · 7 comments
Open
4 tasks done

Organic repeatable queries is missing. #1647

GitAlasGo opened this issue Nov 17, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@GitAlasGo
Copy link

Preliminary checklist

  • I have read the README.
  • I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
  • I have updated Cromite to the latest version. The bug is reproducible on this latest version.
  • This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else.

Can the bug be reproduced with corresponding Chromium version?

No

Are you sure?

Yes

Cromite version

131.0.6778.70

Device architecture

arm

Platform version

Android 11

Android Device model

TECNO SPARK 8C

Is the device rooted?

No

Changed flags

no flags changed

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

No.

Describe the bug

When navigating: chrome://flags/#organic-repeatable-queries the flag is missing in cromite.

Steps to reproduce the bug

Navigate to: chrome://flags/#organic-repeatable-queries

Expected behavior

There should be a chrome://flags/#organic-repeatable-queries just like the latest Chrome Beta 132.0.6834.5 has.

Screenshots

https://imgur.com/a/kuGYet0

@Liamgz
Copy link

Liamgz commented Nov 18, 2024

This has been discussed lately around community. And this is one of the reason i do not go for v131 update.
Meanwhile, there's temporary workaround for this: go to chrome://flags and Enable "Temporarily unexpire M130 flags" this should bring back the "organic-repeatable-queries" .but remember this is only temporary solution, we don't know for the upcoming
cc; @uazo

@uazo
Copy link
Owner

uazo commented Nov 19, 2024

This has been discussed lately around community.

I do not understand

chrome://flags/#organic-repeatable-queries the flag is missing in cromite.

I will do better, I will turn off the expiry management completely, so that all flags are always selectable.
the warning remains not to modify anything if you do not know what you are doing.

@uazo uazo added the enhancement New feature or request label Nov 19, 2024
@GitAlasGo
Copy link
Author

This has been discussed lately around community.

I do not understand

chrome://flags/#organic-repeatable-queries the flag is missing in cromite.

I will do better, I will turn off the expiry management completely, so that all flags are always selectable. the warning remains not to modify anything if you do not know what you are doing.

@uazo Are you gonna obliterate the expiry flag or are you just making it disabled by default?

@uazo
Copy link
Owner

uazo commented Nov 19, 2024

I will completely remove support for expiry_milestone in chrome/browser/flag-metadata.json.

@Liamgz
Copy link

Liamgz commented Nov 19, 2024

This has been discussed lately around community.

I do not understand

chrome://flags/#organic-repeatable-queries the flag is missing in cromite.

I will do better, I will turn off the expiry management completely, so that all flags are always selectable. the warning remains not to modify anything if you do not know what you are doing.

I meant.. apparently chrome v131 has disabled "organic-repeatable-queries" flag and this has already been discussed in reddit lately

@larena1
Copy link

larena1 commented Nov 19, 2024

I will completely remove support for expiry_milestone in chrome/browser/flag-metadata.json.

Are you sure that's a good idea in general? Previously set flags might break stuff then or even crash the browser when they're still set while expired

@uazo
Copy link
Owner

uazo commented Nov 19, 2024

the browser is at the service of the user: my advice is always not to change anything, but there are users who know what they are doing and I don't understand why limit them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants