-
Notifications
You must be signed in to change notification settings - Fork 92
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
Comments
This has been discussed lately around community. And this is one of the reason i do not go for v131 update. |
I do not understand
I will do better, I will turn off the expiry management completely, so that all flags are always selectable. |
@uazo Are you gonna obliterate the expiry flag or are you just making it disabled by default? |
I will completely remove support for |
I meant.. apparently chrome v131 has disabled "organic-repeatable-queries" flag and this has already been discussed in reddit lately |
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 |
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. |
Preliminary checklist
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
The text was updated successfully, but these errors were encountered: