07-31-2017, 04:02 AM
Good news. No need to try on another OS.
Because I found out which revision/commit started the problem (Of course, after I spent 4-5 hours downloading and tring old versions of Chromium).
This is 42d287c9658c6bfa1202275597f28399409e8603 refs/heads/master@{#416995}.
Reproduce:
Build 416996 - The CTRL-T problem begins. (No existed the snapshot of Build 416995)
Build 416972 - The last snapshot that has no problem.
I apologize to you for thinking that this mistake belongs to Cent.
So, what do I have to do now? This problem not happened updated Opera but there is exist on new versions of Chrome and Chromium.
Am I supposed to write this in the Chromium Issue page? That's what they already did. Obviously, I don't think chromium developers will care.
I hope, you don't add this commit to new version of Cent Browser. If this isn't possible, halfheartedly I will have to report the Chromium Issue page (And I'm already sure they will not care).
My only browser is Cent Browser and Cent Developers is my only hope.
Because I found out which revision/commit started the problem (Of course, after I spent 4-5 hours downloading and tring old versions of Chromium).
This is 42d287c9658c6bfa1202275597f28399409e8603 refs/heads/master@{#416995}.
Reproduce:
Build 416996 - The CTRL-T problem begins. (No existed the snapshot of Build 416995)
Build 416972 - The last snapshot that has no problem.
I apologize to you for thinking that this mistake belongs to Cent.
So, what do I have to do now? This problem not happened updated Opera but there is exist on new versions of Chrome and Chromium.
Am I supposed to write this in the Chromium Issue page? That's what they already did. Obviously, I don't think chromium developers will care.
I hope, you don't add this commit to new version of Cent Browser. If this isn't possible, halfheartedly I will have to report the Chromium Issue page (And I'm already sure they will not care).
My only browser is Cent Browser and Cent Developers is my only hope.