-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing changes from week 8, 2020 #1911
Comments
I don't know. I was able to reproduce the bug and I tried with a couple different notes. Nothing as complicated as what you have there though. |
Looks like this is an Electron bug: electron/electron#14705 |
That is not the current functionality in production. @SylvesterWilmott what should it do? |
I can see why this would be the expected behaviour in a situation where you are restoring a single note. However, by doing this we would be switching from trash to all notes without an explicit user input to do so. And for the user restoring multiple notes it can get frustrating pretty quickly. Perhaps what is missing is some feedback that the note has been restored with an action to jump to that note which I think is a broader project to include messaging to the user in the form of snackbars as we do on mobile. |
@belcherj @SylvesterWilmott definitely I didn't intend to trigger design changes here. I noted the behavior because it was unexpected but as we're in the thick of stabilization work I'd be reluctant to introduce destabilizing factors like changing existing behaviors and adding new flows to the app |
This bug exists in production. |
The two issues that I see as regressions are:
And from my testing:
|
Trash
All Notes
orTrash
immediately updates filtered notestag:
does not result a list of all tags in the autocompletertag:
and something else, liketag:te
results in autocomplete results starting with that something else, e.g.test
tag:test
format search string🅰🅱
to🅰🅰🅱
All chagnes synced
Note Display
mode immediately updates and reflects in note listLine Length
betweenNarrow
andFull
removes and adds border around note content appropriately and immediately.Sort Type
mode immediately updates and reflects in note listSort Order
immediately updates and reflects in note list for each sort typeTheme
immediately updates app for desired color schemeInsert checklist
item from the format menu inserts a checklist- [x]
creates a checked checklist item- [ ]
created an unchecked checklist item-
creates a list-
to+
changes the list item bullet, also for*
and•
(\u2022
)Notable issues
Frozen trash view
This is an odd one. I entered a search string into the search field and waited for the list to filter. Then I turned on preview mode. Then I selected the trash view. The app froze in a weird state for a bit before showing the filtered list of trashed notes matching my search. When I cleared the search field the app froze for another bit before showing the full trash view. The Chrome profiler shows nothing but
Rasterizer Thread 1
andRasterizer Thread 3
for that time and they take the full CPU. Will have to investigate more as there doesn't appear to be a cyclic loop in the execution code. When I tried to open the sidebar and go back to all notes it froze again and this time spent over a second in theEvent: pointerout
event. Maybe we aren't throttling some handler. I was able to reproduce without the preview step so it appears to be unrelated to that. This was present in the latest web app deployment.Single-use print
I'm only able to print once it seems. There's a funny behavior on the toolbar when I print and once I've printed once, even though I can open the print dialog again, it doesn't print and there are no errors in the console.
Also, the cursor was visible in the non-Markdown-rendered preview
Notes
develop
open in Electron and made changes in the Electron window then those changes were wiped out when I closed the dialog in the web. I reproduced this behavior to confirm. The wiped-out changes were available as the most-recent revision of the note. Probably we're saving the entire note when we unpublish instead of only sync'ing the publish status.update
from Simperium and somewhere we're only looking at notecontent
instead oftags
.The text was updated successfully, but these errors were encountered: