Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Debugging javascript code break points not maintained

  • 1 wótegrono
  • 1 ma toś ten problem
  • 12 naglědow
  • Slědne wótegrono wót Roland Tanglao

more options

Hi, I'm developing some code in js , and use many functions in my file.js

I use FF Quantum v.63 on ubuntu 18.04 64 bit

In the Web Developer section, on the Debugger tab, when I set the break points and need to reload the page so I can run also the init functions, then the break point are lost, more precisely they are pointing the first line in file with the same code as the breakpoint was set.

for example: I have many lines as

var self = this;

when I put a break on a line like this, then when I reload the page, the break is pointing to the linenum 36 where there is the first code occurrence like I breakpointed.

On chrome, when I put the break for ex. to the line 1000, when reload the break is on line 1000!

Hi, I'm developing some code in js , and use many functions in my file.js I use FF Quantum v.63 on ubuntu 18.04 64 bit In the Web Developer section, on the Debugger tab, when I set the break points and need to reload the page so I can run also the init functions, then the break point are lost, more precisely they are pointing the first line in file with the same code as the breakpoint was set. for example: I have many lines as var self = this; when I put a break on a line like this, then when I reload the page, the break is pointing to the linenum 36 where there is the first code occurrence like I breakpointed. On chrome, when I put the break for ex. to the line 1000, when reload the break is on line 1000!

Wót gbonline změnjony

Wšykne wótegrona (1)

more options

Hi gbonline:

This is a firefox user support forum; we don't have the expertise here to handle developer questions, please ask on stackoverflow.com and tag it 'firefox'. (My GUESS would be that running in Firefox Safe Mode or removing all your Firefox add-ons would fix it but it's only a guess)

Cheers!

...Roland