Minor Usability Issues List

[Koetype]

Firstly, I would like to say thank you and that you are doing awesome work with Sushi, Kura. I enjoy using the browser.

I've prepared a list that is based on issues seen on Windows 10 across both 0.24.0-beta versions, 0.24.0, and 0.24.1 of the Chrome edition. You've likely seen most if not all of them as well as some others, Kura, so while you continue working on tasks like creating the Mac and Linux versions, you can use this list as a reference for usability issues. The issues are relatively minor and do not prevent me from using Sushi for a variety of tasks. Also, I added workarounds for anyone who would like to know.

• The browser crashes when the Ctrl + N new window shortcut is used after a few windows are opened
  • Workaround: using the menu's New Window option
• Browser windows' views and frames still occasionally partly scroll off the desktop and cause the affected windows to become unusuable
  • This issue was more present in prior browser versions. Edit: the following is an example of it against a black background for visibility.
  • Workaround: replicating the windows using the session manager, which is easier if at least one other, unaffected window is open
• Multi-panels and sidebar panels generally persist after they are closed or collapsed in the windows in which they were opened. The following image is against a black background for visibility and has a sidebar panel example on each side.
  • Workaround: usually clicking anywhere inside the affected windows when needed or duplicating the window through the session manager or other means
• The child Chrome windows' tab settings usually do not follow Sushi's tab control settings even when using Cent Browser and other Chromium-based browsers that have many of the same settings and aligning Sushi and the puppet browser's applicable options
  • Workaround: Tab Position Options and other, similar extensions
• Ctrl + Shift + I and other developer tools shortcuts usually do not work
  • Workaround: the default F12 shortcut and related shortcuts
• The context menu's reload option cannot be used, and the default Ctrl + R shortcut usually does not work
  • Workaround: the default F5 shortcut and custom shortcuts such as the default of double-clicking on a tab
• For at least some other Chromium-based browsers, the child Chrome windows are not completely maximized within their parent windows
• Please refer to the image and observe the context menu and the Cent Browser puppet window's boundary near the bottom

[JustinWoodring]

This is a handy list. Also good work Kura keep it up!

_{Sent with GitHawk}

[kura52]

Thank you for pointing out a lot of defects. Several bugs have been fixed in v0.24.2.

Below are answers and questions to this issue.

The browser crashes when the Ctrl + N new window shortcut is used after a few windows are opened

This seems to be a bug in Electron, but changing the timing of displaying the BrowserWindow probably prevented it from crashing.

Browser windows' views and frames still occasionally partly scroll off the desktop and cause the affected windows to become unusuable This issue was more present in prior browser versions. I'll add an image of this if and when I see it once more.

I'm aware of this problem, and I intended to prevent scrolling from working before, but it seems that there is still a lack of countermeasures. I'm looking forward to the reproduction image.

Multi-panels and sidebar panels generally persist after they are closed or collapsed in the windows in which they were opened. The following image is against a black background for visibility and has a sidebar panel example on each side. Persisting Collapsed Sidepanels

Fixed behavior when hiding the sidebar. Can you check if this corrects it?

The child Chrome windows' tab settings usually do not follow Sushi's tab control settings even when using Cent Browser and other Chromium-based browsers that have many of the same settings and aligning Sushi and the puppet browser's applicable options

Could you tell me specifically which settings do not work?

Ctrl + Shift + I and other developer tools shortcuts usually do not work

I fixed it.

The context menu's reload cannot be used, and the default Ctrl + R shortcut usually does not work

I fixed it.

For at least some other Chromium-based browsers, the child Chrome windows are not completely maximized within their parent windows Please refer to the image and observe the context menu and the Cent Browser puppet window's boundary near the bottom

Is Chrome's "Show bookmarks bar" turned on? The area excluding the Chrome UI part (tab bar, address bar, etc.) is the maximum area where child windows can be displayed. This issue is likely to occur when the Chrome UI is set to be vertically long, such as displaying a bookmark bar.

[Koetype]

You're welcome, Kura. I'm glad to be able to help.

The browser crashes when the Ctrl + N new window shortcut is used after a few windows are opened

This seems to be a bug in Electron, but changing the timing of displaying the BrowserWindow probably prevented it from crashing.

I understand. The issue related to the shortcut appears to be fixed.

I have an image of the window scrolling issue above as you've probably already seen.

Fixed behavior when hiding the sidebar. Can you check if this corrects it?

Yes, this has been good for me so far.

Could you tell me specifically which settings do not work?

It's only the tab settings that I've noticed as of now. As can be seen in the following images, Cent and Sushi share some of the same options.

When I set new tabs to open in the background in both browsers' settings and in the same panel in Sushi's settings, they sometimes still open in the foreground with the previous tab still selected in the tab bar. Using extensions like Tab Position Options helps with this. It is a minor issue, one which I wanted to bring up for awareness for anyone who may use other, Chromium-based browsers with Sushi.

Cent is one of the few Chromium-based browsers that has many advanced settings, and with so many, it's possible that Puppeteer cannot handle many of them. Based on what I've read, Puppeteer has been made specifically to control Chrome and Chromium, so such minor issues with other, related browsers are to be expected. It's nice that at least Cent still works rather well in this setup.

The context menu and developer tools shortcuts also are working now.

Is Chrome's "Show bookmarks bar" turned on? The area excluding the Chrome UI part (tab bar, address bar, etc.) is the maximum area where child windows can be displayed. This issue is likely to occur when the Chrome UI is set to be vertically long, such as displaying a bookmark bar.

I also thought that was the case based on the address bar from Cent and Chrome that I've seen on the Top page.

The bookmarks bar was not on when I was using Cent, but turning it and other options on in its settings, restarting Cent and Sushi, turning the bookmarks bar off, and restarting the browsers again sort of fixed it temporarily. It can reappear particularly after restarts.

Windows' taskbar seems to be related. When I took the last image in my previous comment, I had my taskbar turned off. I turned it back on afterwards, and the boundary basically disappeared. The issue may be a minor limitation of Puppeteer.

[Koetype]

Fixed behavior when hiding the sidebar. Can you check if this corrects it?

As I've been using 0.24.2 more, the issue relating to closed or collapsed panels still can happen occasionally but not as often or as persistent as before, which is good.

[Koetype]

The window view and frame scrolling issue appears to not really happen anymore in 0.25.0, but a frame occasionally can disappear, which makes the window unusable as you've likely seen. This has happened most often when opening new tabs. New windows generally can be opened without having to restart the browser.