-
I generally never use the Script Editor; it’s vastly simpler to use the Source pane, but I’m troubleshooting an onClick script issue so I’m letting “it” decide how to do it in case I’m wrong.
-
So I edit this code as a Simple Action, Execute Client Script:
sessionScope.viewBy=“”+aView;
sessionScope.viewName=“”+sessionScope.viewLinks.get(aView);
//context.redirectToPage(context.getUrl().getAddress());
And I get this code in the Source pane:
viewBy=“”+aView; sessionScope.viewName=“”+sessionScope.viewLinks.get(aView);//context.redirectToPage(context.getUrl().getAddress());
Now it did show that code in the Script Editor when I clicked “edit”, so it saved what was presented, but I thought it was render bug, not a data bug. I’ve seen the old LS editor “truncate” code on many, many occasions, but it was fine once saved. Here it was not.
- This is not liable to affect me much because I don’t generally use the Script Editor, but if I did this would certainly not be desirable behaviour, so I thought Lotus should know…