I can’t debug a large four part Bootstrap Accordion registration form because it appears that the scripts in the embedded browser in phpEd are not working, so that the required data on collapse two to four can’t be entered, plus I’ve noticed that all script functionality is inoperative in the browser. Everything else in this out-of-the box, unchanged installation is fine.

Currently when debugging I’m using a Firefox external browser but this very tiresome because the form clears when debugging stops and you repeatedly have to re enter data, this doesn’t occur in the embedded browser.

Any directions? Tell me there’s some tiny box somewhere I can tick. Some tiny box that should have hover help and DOESN’T.

There is nothing that would block scripts in embedded browsers. I can see they work and can post some logs and can find tags in DOM. If something does not work for you, you need to check if the scripts are loaded in the first place. If they are, start posting logs and check console.

Which logs do I look in? Do you know how many logs there are on this machine?
I complain continually that people who “know” are incapable of answering because they assume too much.
Imagine your customers are Gibbons, and then write a reply.
Before you post your reply, go away, make tea, (or coffee) return and after rewriting you answer so it’s EXPLICIT you may post it!

Thanks for instructions on how to make posts.

Perhaps, the wording is not very clear -- I want to expand a little bit. Basically, PhpED that does not make any efforts to run or not to run your scripts in either embedded browsers or external ones. The scripts are running by a piece of code that was developed by the browser development teams, not NuSphere. We only integrated their work. I know that scripts work in embedded browsers and you can see it yourself if you check something simple. But if _some_ of your scripts do not work there, how can we help? You just indicated you're experiencing a problem. That's it. All right, you can blame us, you can blame people who developed browsers, you can blame people who developed scripts, but doing so you change really nothing. If you need help, you can create reproducible case, as small as possible, learn how to write scripts and how to write functions that log activity in particular, then find what drives the running process, find corresponding developers and check with them. May be they will help. That's my suggestions on how to handle such situations. Of course, with full respect and good wishes.

PS Since you did not provide much details, except where the problem (potentially) happened - embedded browser and some 3rd party Bootstrap Accordion js framework, I assumed that it's JavaScript you're trying to run in embedded browser.