New Version:
Previously method name used to show up besides Name in chrome inspector.In latest version of chrome it is missing any way to get it back?
Old version:
Got it
Just needed to right click and select options to show
Related
The extension used to work when it is simply added to GuiViewer3D as an extension option, such as :
options = {extension:['Autodesk.Viewing.ZoomWindow']};
viewer = new Autodesk.Viewing.GuiViewer3D(htmlDiv,options);
I checked it with EXTENSION_LOADED_EVENT eventListener
Actually it is loaded. But somehow on toolbar it only shows default(dolly) option.
What could be the problem ?
Apparently looks like there's been a regression with this extension in one of the recent upgrades and can confirm to be getting the below error which must have prevented the plugin from loading:
document not ready yet, trying again in 500 milliseconds...
As a workaround delay the loading of the extension till when the document is fully ready - see live demo here
NOP_VIEWER.addEventListener(Autodesk.Viewing.MODEL_ROOT_LOADED_EVENT,()=>{
NOP_VIEWER.loadExtension('Autodesk.Viewing.ZoomWindow')
})
Since two days it is not possible anymore on my PC to open websites with firefox via Selenium WebDriver (Java, Maven, IntelliJ). A blank page is opened in a new firefox window and nothing happens. I can access the specified website manually in the firefox window that is opened.
This is the code I am using for creating the webdriver (the profile SELENIUM exists; I created it manually):
System.setProperty("webdriver.gecko.driver", "geckodriver.exe");
ProfilesIni profile = new ProfilesIni();
FirefoxProfile ffprofile = profile.getProfile("SELENIUM");
return new FirefoxDriver(ffprofile);
And to open pages I am using:
driver.get(myURL);
The error message from IntelliJ is:
SZgNd84ad1sbgGXU5f5p+46dwuqwWXX8hUp4lAPBZwEAAA0DAAANAAAAAAAAAAAAAAAAALfGQwB4dWxzdG9yZS5qc29uUEsFBgAAAABGAEYAnRUAAFnIQwAAAA (and some million more letters) == does not equal undefined"] (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Today Chrome also stopped working, it only shows "Not secure" next to the URL and data; in the URL bar.
Is there any way to find out what caused this and how this can be fixed?
I am using the latest version of selenium (defined in pom.xml) Chrome Version 57.0.2987.133, Firefox 45.4.0.
Thanks in advance for any help!
I have seen this in a previous project, so basically what happens is that all this is caused by incompatibility between Selenium and Firefox/Chrome versions, but not by any one specific version number. So what you really want is to be 1-2 driver versions behind the newest, if your WebDriver is on the latest version. Otherwise, roll the Firefox/Chrome version back even further if your WebDriver is older, or upgrade Webdriver.
Other options is to use FF profiles/Chrome preferences. This is an example that was working back then:
FirefoxProfile prof = new FirefoxProfile();
//FirefoxProfile prof = profile.getProfile("default");
//prof.setPreference("browser.startup.homepage", pageUrl);
//prof.setPreference("startup.homepage_welcome_url", pageUrl);
//prof.setPreference("startup.homepage_welcome_url.additional", pageUrl);
prof.setPreference("xpinstall.signatures.required", false);
prof.setPreference("toolkit.telemetry.reportingpolicy.firstRun", false);
You can try other combinations of those settings and see which one will work for you.
I have already published an app with the Version 1.1.0.0.
When I'm trying to update the app with a new .appx file after creating the AppPackage I'm getting this kind of an error.
It's a Universal app where i've published the first versions of the Windows Store & Windows Phone. Now i'm trying to update the Win Phone app where i'm facing the issue. I can't even see the replace button near the Delete option.
Whenever i try to upload the new appx or the bundle file, it's not letting me to submit.
Any help would be appreciated.
Looks like a Firefox problem - use IE and this seems to work (at least has for mine!)
Try IE, Firefox doesn't show 'replace' option. Add new option is not for update. If you use replace then you will be able to update.
I used "chrome://inspect" for a few days. Everything was fine. Today, for some reason, when I click "inspect" the result is "404 Not Found The resource could not be found."
What could be the reason for this ?
I was able to find only this topic: https://code.google.com/p/chromium/issues/detail?id=329979
I guess the drivers are OK if the device appears ? I`m able to transfer files, to "focus tab" or "close tab" and "reload" but i can't "inspect".
Chrome Version: 37.0.2062.124 m
DevTools URL : chrome-devtools://devtools/remote/serve_rev/#180870/devtools.html?&remoteFrontend=true&dockSide=undocked&toolbarColor=rgba(230,230,230,1)&textColor=rgba(0,0,0,1)
Edit:
I tink this comment is important so...
A bug was opened in the Google tracker: Link Please star it! Remember that you don't have to add a comment to it if you don't have new information :)
by MM
Edit 2:
DevTools are actually broken for ANY kind of Android devices, regardless device's version, Chrome version or OS. URLs of such kinds - http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html - that must return DevTools code - now returns 404. That could be fixed by Google without any change in the Chrome code, it's completely server-side problem.
by vrid...#gmail.com at bug tracker
Edit 3: At this time http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html is OK but slow. I realy cant get why I need usb driver to send data over the internet... to this page just to debug.
I had the same problem, but it was caused by chosen AOSP WebView instead of Chrome Stable at Developer Options > WebView Implementation. If you do not have Chrome Stable option available, then try to install Chrome and check again.
Just had the same issue. VPN was on, turnning it off fixed it.
That was a cloud storage glitch. Things have reverted to normal since then.
After updating chrome version on Android device worked for me.
This still occurs and workaround is to open chrome://inspect and click on inspect link under Remote target assuming the command node --inspect server.js is already hit.
Workaround:
disable chrome updates. Instructions: https://www.makeuseof.com/tag/stop-automatic-chrome-updates-windows/
uninstall latest Chrome on desktop.
install previous version: (I used slimjet: https://www.slimjet.com/chrome/google-chrome-old-version.php)
Open chrome://inspect/#devices url and choose inspect-fallback instead of inspect.
I'm trying to get TypeScript source debugging working in Chrome, but I'm running into two specific and perhaps related problems.
The first is that the comment generated by the TypeScript/WebEssentials compiler that's supposed to identify the location of the source map file looks like this:
//sourceMappingUrl=MySourceFile.js.map
But Chrome won't read that file. It seems expect that the comment will look like this:
//# sourceMappingUrl=MySourceFile.js.map
If I manually change the comment to that, and refresh my page, then magically the references to all the .ts files show up as sources in the Chrome Developer Tools.
However, that leads to my second problem, as the files don't actually get loaded. The .ts source file that Chrome should be trying to download is http://localhost/MySourceFile.ts, but the one that it's actually trying to download is http://localhost/C:/source/web/MySourceFile.ts. That sort of makes sense, as the opening attributes of MySourceFile.js.map look like this:
{"version":3,"file":"tmp1523.tmp","sources":["C:/source/web/MySourceFile.ts"
But that obviously doesn't work with Chrome, as it interprets the source-map location to be entirely relative, and IIS (quite correctly) won't serve up any URL looking like http://localhost/C:/source/web/MySourceFile.ts.
So, with respect to these two problems, is it Chrome or the TypeScript source-map feature that's doing it wrong? And what's the recommended way of doing this?
I'm using Chrome 25.0.1323.1 dev-m, with TypeScript 0.8.1 and WebEssentials 1.8.5.
This is an issue with version 1.8.5 of Web Essentials (the version currently available from the Visual Studio Gallery). The latest nightly build (at time of writing http://madskristensen.net/custom/webessentials2012.vsix) fixes the problem and generates the map linkage correctly.