04-22-2024, 12:56 PM
(This post was last modified: 04-22-2024, 12:56 PM by matthewadamsdk.)
This is a problem that I've had with using Cent browser as a maximized window for as long as I can remember. I had hoped that the new version 5.1.1130.82 might have resolved the issue, but it seems to persist...
The problem: when using Cent browser as a maximized window with several open tabs, if the selected tab is *not* the tab furthermost to the right, then there will be a pixel-error between the furthermost (not-selected) tab to the right, and the title bar. Se my uploaded picture for clarification.
![[Image: dh9xrdl-0e261701-b17b-4d6e-b480-5c5a36ec...3WoXxt32vg]](https://images-wixmp-ed30a86b8c4ca887773594c2.wixmp.com/f/13b1ab2e-0dc0-479d-a5da-d6faaa5498e7/dh9xrdl-0e261701-b17b-4d6e-b480-5c5a36ece31f.png?token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ1cm46YXBwOjdlMGQxODg5ODIyNjQzNzNhNWYwZDQxNWVhMGQyNmUwIiwiaXNzIjoidXJuOmFwcDo3ZTBkMTg4OTgyMjY0MzczYTVmMGQ0MTVlYTBkMjZlMCIsIm9iaiI6W1t7InBhdGgiOiJcL2ZcLzEzYjFhYjJlLTBkYzAtNDc5ZC1hNWRhLWQ2ZmFhYTU0OThlN1wvZGg5eHJkbC0wZTI2MTcwMS1iMTdiLTRkNmUtYjQ4MC01YzVhMzZlY2UzMWYucG5nIn1dXSwiYXVkIjpbInVybjpzZXJ2aWNlOmZpbGUuZG93bmxvYWQiXX0.2dd0UlhFA8uojIddmvLOKJWTcSmec_0jp3WoXxt32vg)
This problem is not present when using Cent browser as a restored window.
I haven't seen this problem being addressed in the forums - if it has, I apologize.
Does anyone have an idea what might cause this error? The error is not present when using either Google Chrome, MS Edge or Supermium.
The problem: when using Cent browser as a maximized window with several open tabs, if the selected tab is *not* the tab furthermost to the right, then there will be a pixel-error between the furthermost (not-selected) tab to the right, and the title bar. Se my uploaded picture for clarification.
![[Image: dh9xrdl-0e261701-b17b-4d6e-b480-5c5a36ec...3WoXxt32vg]](https://images-wixmp-ed30a86b8c4ca887773594c2.wixmp.com/f/13b1ab2e-0dc0-479d-a5da-d6faaa5498e7/dh9xrdl-0e261701-b17b-4d6e-b480-5c5a36ece31f.png?token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ1cm46YXBwOjdlMGQxODg5ODIyNjQzNzNhNWYwZDQxNWVhMGQyNmUwIiwiaXNzIjoidXJuOmFwcDo3ZTBkMTg4OTgyMjY0MzczYTVmMGQ0MTVlYTBkMjZlMCIsIm9iaiI6W1t7InBhdGgiOiJcL2ZcLzEzYjFhYjJlLTBkYzAtNDc5ZC1hNWRhLWQ2ZmFhYTU0OThlN1wvZGg5eHJkbC0wZTI2MTcwMS1iMTdiLTRkNmUtYjQ4MC01YzVhMzZlY2UzMWYucG5nIn1dXSwiYXVkIjpbInVybjpzZXJ2aWNlOmZpbGUuZG93bmxvYWQiXX0.2dd0UlhFA8uojIddmvLOKJWTcSmec_0jp3WoXxt32vg)
This problem is not present when using Cent browser as a restored window.
I haven't seen this problem being addressed in the forums - if it has, I apologize.
Does anyone have an idea what might cause this error? The error is not present when using either Google Chrome, MS Edge or Supermium.