Firefox Developer Edition 44 now has a built in JSON Viewer. It's a nice gesture, but I highly prefer the readability of the third-party JSON viewer I was using.
Is there any way to disable, override, or otherwise customize the new built in JSON viewer?
Go to about:config
In search, paste 'devtools.jsonview.enabled'
Select the pref, right-click and select 'toggle'
Related
I understand it may be possible in the "sources" tab, but how about the console tab? I find it supereasy to test stuff there, and quickly aligning / indenting code would be fab. Related answer for the sources tab:
Write JavaScript in Chrome developer tools
There's currently no way to auto-indent a selection of text in the Console.
The Console's built off of CodeMirror though, which does have support for that feature, so it's possible this could get added in the future. CodeMirror's keyboard shortcut for auto-indent is Shift+Tab.
You can post to the mailing list to request the feature.
Is there a way to click on the Save or Open button in the pop up that appears while downloading a file in IE 11? I am using Robot Framework AutoIt Library.
I can handle the windows that comes subsequent after clicking the Save or Save As option.
What kind of file are you downloading? Depending on the file type you should be able to set a default behaviour in IE11.
Personally I think AutoIT solutions with this are overkill, I'd recommend looking at the following blog post for alternative ideas if possible:
https://blog.codecentric.de/en/2010/07/file-downloads-with-selenium-mission-impossible/
However, if this is a scenario you simply MUST automate as you're doing then my first line should help you.
How can I get the fields logical names of webpage to be tested so that I can write script in Robot Framework.I understand we use key words to check/validate the controls (input, out and images etc) as required. I am come from manual testing background so obviously need to know how does it all work in Robot Framework.
Every browser has developer tools which you can use to inspect the page. For example, on chrome and firefox you can press Control-Shift-I to open the developer tools window. On IE I think it's F12. From there you can inspect the elements that make up the page.
You can also simply ask the members of your development team to help you.
we are displaying a reporting services report as a pdf document in acrobat reader. when the user clicks on the print in the acrobat reader, I will like to print the report and close the report. The user should be able to print the report only once.
I do not think that this is possible. You need much more access then browser can give. May be ActiveX or browser add-in can help...
Anyways, browsers have some limited support for printing. Check out:
window.print();
I am not sure if it works in all browsers, though.
This is possible to do. You simply need to add
this.print();
as a "JavaScript PDF action" to the "open" event of the document. Unfortunately, if your report generator is creating the PDFs internally you might not be able to inject the necessary code.
What's the best way to put the "debugger;" statement inside the __doPostBack method or a way to step in the method?
__doPastBack is still javascript running in the browser.
While it's possible to debug javascript using visual studio and IE, if you want to set a break point you need to be able to open the javascript in visual studio. You can' do that for __doPostBack because it's generated by the compiler.
However, if you view the page in firefox you can use the firebug extension to set break points in the browser after the page loads.
You can manually attach to the iexplore.exe process as Script debugger and set the breakpoint accordingly on generated page. Or you could break into debugger anytime by selecting the option from menu if you had enabled script debugging in advanced tab in Internet options
In IE you can go to internet settings -> advanced -> and uncheck the "Disable Javascript debugging" boxes. This will allow you to put a breakpoint in the JS code.
It really is just a lot easier to use FireBug inside of FireFox and you don't have to go through a lot of nonsense.
Another option for JS debugging and FireFox (which I use a lot) is to use venkman. You can get it as FF extension right here.