You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first folder or file in the list of files should open.
Actual behaviour
A new line is added to the Readme file.
Background
I'm running some basic end-to-end tests for my app Linkeditor. With NC 26 tests suddenly started to fail all over the place. I looked at the screenshot that Cypress took and saw that text was entered into the Readme section instead of into the "new file" input or the input in my app's modal (see screenshot below).
The reason for this is that initialization of the editor for the Readme section is async. And as soon as the editor has loaded it steals focus, leading to unpredictable results when either (1) loading of the editor is slow or like in this case (2) the (automated) user takes a different action really fast.
For now I solved this by making my tests wait a couple of seconds for the editor to be initialized before taking any other actions.
But I don't believe that stealing focus to the Readme section is the best solution. My suggestion would be to make this section manually focus-able by the user instead. What do you think?
Steps to reproduce
Expected behaviour
The first folder or file in the list of files should open.
Actual behaviour
A new line is added to the Readme file.
Background
I'm running some basic end-to-end tests for my app Linkeditor. With NC 26 tests suddenly started to fail all over the place. I looked at the screenshot that Cypress took and saw that text was entered into the Readme section instead of into the "new file" input or the input in my app's modal (see screenshot below).
The reason for this is that initialization of the editor for the Readme section is async. And as soon as the editor has loaded it steals focus, leading to unpredictable results when either (1) loading of the editor is slow or like in this case (2) the (automated) user takes a different action really fast.
For now I solved this by making my tests wait a couple of seconds for the editor to be initialized before taking any other actions.
But I don't believe that stealing focus to the Readme section is the best solution. My suggestion would be to make this section manually focus-able by the user instead. What do you think?
Server configuration
Operating system: N/A
Web server: N/A
Database: N/A
PHP version: N/A
Nextcloud version: 26.0.0
Where did you install Nextcloud from: Docker
List of activated apps:
Nextcloud configuration:
Client configuration
Browser: Firefox 111.0.1
Operating system: MacOS
The text was updated successfully, but these errors were encountered: