As already reported on the forum 3 weeks ago, unfortunately I’m here to report that the broken code editor bug on Windows (11) / Chrome (138) is still here despite the " Complete Frontend Re-optimization" in 4.4.0
New examples of the discrepancy between the cursor location on screen and its actual true location - in both examples the cursor is actually located at the end of line :
Please fix ASAP as it makes any code edit a struggle.
Also while we discuss the topic of code editing, the experience could be improved overall, starting by the possibility to expand the editing area in the code node editor. Being able to load our own .py scripts (based on a template) would also be a huge workflow improvement.
Between the cursor bug and the limited space, currently having a Python code node of 100+ lines is quite a challenge
Actually the forum message editor is much nicer, with no cursor bug and the full screen composer option.
It’s all the more important that I believe a lot of power comes from the customization potential opened up by code nodes.
Hey @cdromain! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @cdromain Thanks again for flagging this and really appreciate your patience. I’m no longer able to reproduce the issue with the recent updates. When you get a chance, could you use this link to screen record what you’re seeing on your end? That would help us pinpoint what’s going on and get it fixed for you. Thanks again for your help with this.
Just recorded a quick example, let me know if you need more.
Look at how the highlighted (selected) area doesn’t correspond to the actual code characters :
Hey @cdromain – This issue should be fixed now, do you mind deleting the run code node and adding it back again to see if it works as expected now please? Thank you for your patience here