Description
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 read the FAQs.
- 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?
Yes
Are you sure?
Yes
Cromite version
Cromite 134.0.6998.39
Device architecture
arm
Platform version
Android 15
Android Device model
Samsung Galaxy s2x line
Is the device rooted?
No
Changed flags
Attempting to
Is this bug happening ONLY in an incognito tab?
No
Is this bug caused by the adblocker?
No
Is this bug a crash?
Yes, that's a fair description. It actually says, 'Cromite has crashed'
Describe the bug
That's easy!
Navigate to chrome://flags
Change anything</>
BOOM!
'Cromite has crashed,' and regardless of any other detail or variable, we're back at the beginning. The 'flag,' toggle, feature, or whatever else, never changes. The browser's crashing prevents any of the options in the entirety of the flags world to be changed.
Would you kindly hypothesize,
What's wrong?!?~`~2!!?!1m?
And what can be done?
There are so many things that the flags world opens up, and a few in particular would make the work that I do significantly more efficient and functional. A huge difference. Cromite would probably become my favorite browser here in the Android universe.
Maybe everywhere. (Except our beloved, slogging Tor)
I've tried to change stuff in chrome://flags a number of times, as well as all around the browser's settings menus, etc., prevented in flags. the present difference between this configuration and the default are probably trivial except for one little switch.
How can it be discovered?
While I'm here ... Theres a second behavior I'd like to ask about. In Tab A, ill open Tab B, at which time Cromite autodirects to B (i'd also like to change the autodirection). Perhaps ill also go play in C, D, N, M, ... (or not). regardless, when i return to A, it appears empty, as if there's no content for the browser or user to perceive or interact with.
In fact, returning to any (?) earlier tab(s) in this iterative sequence of openings will reveal a faux blank page.
to jolt the program into displaying what's already there, I'll plop the cursor into the address bar and voila! This reveals what has remained there fought, been temporarily concealed. (but sometimes it reloads the page, which I don't look as ever good, and is sometimes disastrous, destroying content I was working on that had not yet been saved.)
Help here too?
Please let me know if I can elaborate. And please please please share your thoughts, insights, suggestions, questions, comments, and wisdom!
I'm very eager to fix some of the stuff in flags – so much so that I've already
returned here, to this issue, twice! Hoping that editing the entry might strike the reader's fancy a bit more.
Please?
Thank you!
Steps to reproduce the bug
chrome://flags
Attempt to change any setting with a drop-down menu that enables or disables. Toggles or boggles.
poof!
'Cromite has crashed'
__ and never saves any change.
Expected behavior
Honor user's changes. Not crash.
Screenshots
Speaking of issues ... Regardless of how the screenshot is attempted, from what program and configuration of settings a shot is launched, etc., Android always says in the notification menu, "ouldn't save screenshot," lowercase like that, and I've gone mad trying to fix it.
(I promise I'm not needy usually, but the computers, man. software - especially when these transnational LLCs are involved.)
Thx!!
No response