Skip to content
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

[BUG] side effects (undo/redo/coloring) since new code editor #168

Open
FabriceNeyret opened this issue Jul 5, 2023 · 5 comments
Open
Labels

Comments

@FabriceNeyret
Copy link

On my chrome/linux/nvidia ( but not FF) I very recently see 2 big buttons to choose the editor.
Simultaneously, several things no longer work correctly on shadertoy (whatever the editor).

  • redo feature (in code) no longer works correctly ( if covering several locations ), and no longer really usable.

  • change of the undo behavior: undo now seems to be global rather than by text block in the html page:
    if I code a portion A
    then type a message portion B in the chat
    then code aportion C

then doing undo in the code box will undo C then B then A rather than acting only on the code.

@FabriceNeyret
Copy link
Author

Really, ctrl-Y / restore function no longer working is way too annoying. ( regularly loosing work ).
I have to switch off the extension because of that. :-(

@patuwwy
Copy link
Owner

patuwwy commented Aug 16, 2023

@FabriceNeyret, please use older version

You can load it into browser following these instructions

I’m sorry but I won’t be able to help with this issue in the nearest future.

@FabriceNeyret
Copy link
Author

done, thanks !
Note that I got the error message "Manifest version 2 is deprecated, and support will be removed in 2023.",
but it still seems to work :-)

minor details: last changelog is 0.13.247 ( 22/02/2022 ) ;-)
even after relaunching chrome, the menu in the toolbar icon still displays 0.14.211.

@FabriceNeyret
Copy link
Author

The redo is still broken in the "new" version, which is extremely inconvenient (massively loosing changes when trying to undo-redo).
Today I tried the VScode editor: clicking in the code set the cursor at the end of the line rather at the mouse location so hardly usable.
→ I have to stick to the 0.13.249 version as you advised above, but I understand it won't work forever.
Any plan to fix this nasty bug ?

@FabriceNeyret
Copy link
Author

Am I the only one to have this very annoying bug ?
( chrome on linux here. Still using the default code editor ).
One of the strange behavior: when undo-ing, the focus of the undo can suddenly go in another area (e.g. the chat part, if a ongoing text was typed there) and anachronistically undo there (and apparently not coming back to code).
And even when not doing that, if undoing goes on different code regions, redoing is a mess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants