Propose changes for file name + line number #48
Conversation
I feel it is more accepted to use `filename.ext:123` as this can easily be copied and pasted and use when looking up a file on sublime, chrome dev tools source files. it will help us save a few seconds each time we need to find the specific page and line number to make changes or place break points..
Propose changes for file name + line number
|
Nice change - thanks for suggesting this. I'll rebuild and deploy Visual Event shortly. |
|
A bit careless of me with the quotes, works like a charm, if I knew you'd respond this quickly would have suggested it monkeys ago :) |
|
No problem. You caught me at a good time for it :-) |
|
ok, just thought you may want to have a look at this... https://developer.chrome.com/extensions/devtools_panels it might be a cool idea, to create a new panel "Visual Events" maybe this could be the way forward to resolve or alternative to #43 . |
|
Actually Chrome already has an event listeners list (also shown in the screenshot in the document you linked to). So I'm not sure how useful it would be. I suppose it would help tell what library assigned the code and where it was attached... |
|
Function defined in Inline script:31 I think I may have made a mistake there, inline script:31 doesn't mean much... |
|
Yeah possibly not. I'll look at that when I get a chance. |
I feel it is more accepted to use
filename.ext:123as this can easily be copied and pasted and use when looking up a file on sublime, chrome dev tools source files.it will help us save a few seconds each time we need to find the specific page and line number to make changes or place break points..