I am new to Karate UI and trying to maximize the chrome browser using Karate ZIP release(0.9.6RC4) on mac
I tried both with no luck
Given driver 'https://google.com'
And driver.maximize()
And maximize()
However fullscreen() is working fine, kindly help
Sorry it seems to be a bug in Chrome itself. You can try this experiment:
* driver.send({"method":"Browser.setWindowBounds","params":{"windowId":1,"bounds":{"windowState":"minimized"}}})
Now replace minimized with normal or maximized and you will see maximized does not work. But it is supposed to as per the spec: https://chromedevtools.github.io/devtools-protocol/tot/Browser/#method-setWindowBounds
This definitely used to work in previous versions of Chrome :)
We don't consider this a priority, feel free to raise a feature-request and also investigate if there is a known problem with Chrome. So I put the question back to you "kindly help". We need more open-source users to contribute.
Also note that driver type chromedriver works fine.
Related
I am new to Karate UI and trying to maximize the chrome browser using Karate ZIP release(0.9.6RC4) on mac
I tried both with no luck
Given driver 'https://google.com'
And driver.maximize()
And maximize()
However fullscreen() is working fine, kindly help
Sorry it seems to be a bug in Chrome itself. You can try this experiment:
* driver.send({"method":"Browser.setWindowBounds","params":{"windowId":1,"bounds":{"windowState":"minimized"}}})
Now replace minimized with normal or maximized and you will see maximized does not work. But it is supposed to as per the spec: https://chromedevtools.github.io/devtools-protocol/tot/Browser/#method-setWindowBounds
This definitely used to work in previous versions of Chrome :)
We don't consider this a priority, feel free to raise a feature-request and also investigate if there is a known problem with Chrome. So I put the question back to you "kindly help". We need more open-source users to contribute.
Also note that driver type chromedriver works fine.
The charts, especially when exportedToImage are oversized/scaled - discovered on a MacBook in Chrome and Safari - while testing for an issue with Primefaces (Pf uses JqPlot for charts)
See on the jqplot test-page, but it is also reproducible on Linux/Ubuntu with a Chromium-based browser when opening developer tools and selecting any mobile-device (in this case I set it to "responsive")
!! - reload the page after opening dev-tools !! - at any resolution the image keeps getting oversized. To disable the effect, just close dev-tools and reload. Now the image looks correct again.
There was an issue on GitHub, but it was closed.
Also the showcase of PrimeFaces using this library works.
How can that be? I've checked this with all my available devices to rule that out - but it's somehow strange - can someone also reproduce this?
What does developer tools and Chromium on Mac do to get these results? - ignoring media-queries? I've also experimented with that, no success.
If your read that jqPlot ticket you posted here it has a solution in it: https://github.com/jqPlot/jqPlot/issues/119
PrimeFaces 8.0 Showcase has the following manually patched fix applied from that ticket:
https://github.com/primefaces/primefaces/issues/4655
That is why the PrimeFaces showcase does not exhibit the issue if you read through that ticket it is a two line fix applied to the JQPlot code.
I have an aurelia application updated to the latest beta, 1.0.0-beta.1.2.1 at the time of this writing. This version of aurelia already uses Babel 6, and my application is based on the based on the ASP.NET 5 ES2016 navigation skeleton.
"All of a sudden", whenever I try to open my untranspiled javascript source files in Chrome (Version 49.0.2623.110 m (64-bit)) Developer tools, for instance main.js, all I get to see is the html of Index.cshtml.
It doesn't matter which javascript file I try to open, it always shows the html of Index.cshtml instead of javascript.
The transpiled files are displayed correctly in Chrome Dev Tools.
I've had this before but it usually meant I had a binding or templating error somewhere, but in this case the application works perfectly, so it probably has to do with the sourcemaps... Or does it?
My questions are:
What is the best way to track down a subtle binding or templating
error in Aurelia? Everything I've tried to do in my applcation works
fine, but I don't want to rule out this being my own fault just yet.
In case it's not my fault, has anybody come across this before? What
is the reason the sourcemaps are not working; is it Aurelia? is it
Babel 6? Is it Chrome?
Update
It doesn't seem to be a Chrome issue; the same problem occurs in Edge.
Update 2
By turning off Enable javascript sourcemaps on Chrome Developer Tools I can debug de transpiled code.
The transpilation gulp tasks I'm using are copy/pasted from the version mentioned above.
Has anybody else come across this issue?
Ok, I think I've found the problem.
I changed includeContent to true for sourcemaps.write in the build-system gulp task defined in build\tasks\build.js, so that line 23 of that file looks as follows:
.pipe(sourcemaps.write({ includeContent: true}))
This comes set to false in the navigation skeleton, so more people should have this same issue. Anyhow, this seems to have solved the problem.
I also removed the sourceRoot: "/src" parameter in that call, as it is only necessary when includeContent is false.
I'm having a problem with the built-in help/documentation within MATLAB 2013a (issue also present in 2012b).
Upon opening the help files the pages appear with no formatting, only plain text. Search results do appear correctly though.
I have found only one instance of someone else with this issue, on MATLAB central here. However, there are no responses to the author's question. The issue I'm having is exactly the same as described there.
I have tried removing the preference folder and relaunching MATLAB but this doesn't help.
I'm using Windows 8.1 and MATLAB 2013a.
Any help or suggestions on how to fix this would be very much appreciated.
Edit:
Thank you everyone for the feedback so far. I don't believe java to be the issue, I have the latest version installed (1.7.0_45) while MATLAB uses it's own version (1.6.0_17). Both of which co-exist on my machine.
Following horchler's thread led me to another semi-related bug report here. The following code is listed at the bottom of the workaround (the script attached to the workaround didn't fix anything unfortunately).
com.mathworks.mlwidgets.html.HtmlComponentFactory.setDefaultType('HTMLRENDERER');
This results in a degraded appearance of documentation pages and loss of some functionality but is still an improvement over the plain text and scrambled pages.
Hopefully from this new information we can work towards a solution!
One solution is to go back to IE-10, or to use the patch on http://www.mathworks.com/support/bugreports/989850
Which basically replaces the localnav.js at <MATLAB>/help/includes/product/scripts
The link to download!
This is an old post, but I had the same issue and have a fix (not downloading R2013b or java related). Just downgrade from IE 11 to 10: Go to System (or System & Security)->Windows Update->View Update History->Installed Updates -> Find IE11 and uninstall it. Your system should revert back to the prior installed version. This fixed the help issues.
The problem is related to Internet Explorer 11, which MATLAB uses to render its help files. I was experiencing this problem in Windows 7 and rolling back to IE 10 fixed it right up. Unfortunately, that's not an option with Windows 8.
(Running MATLAB 8.1.0.604 (R2013a), Mac OS 10.8.3)
When I use the doc command, for example, doc fwrite;, or when I click the "more help" item in the popup help bubble for a command, the documentation window opens, but MATLAB subsequently hangs (the spinning beachball appears). This lasts indefinitely, and I inevitably have to force quit MATLAB. This also happens when using the Publish option from the editor.
Anyone have any ideas for diagnosing this? I tried taking a process sample but I didn't see any info I could interpret, I think since it's in Java the relevant information is obfuscated behind the JVM.
See this post on MatlabCentral: http://www.mathworks.com/matlabcentral/answers/71718 ... and more specifically this bug report which includes a "workaround." They don't suggest what could be the cause, but you might make sure that OS X is updated and that you have the latest version of Java. If you do other work with Java or with WebKit these might cause issues.
I hope you have already solved the problem. Otherwise a solution has been found, the bug resides in the Access for Assistive devices (only for version 2012b and later). If you can turn them all off from System Preferences, do that. If you can't, type this in the command window:
com.mathworks.mlwidgets.html.HtmlComponentFactory.setBrowserProperty('JxBrowser.BrowserType','Mozilla15');
From http://www.mathworks.com/support/bugreports/870843
I had the same problem with Matlab R2014a on OS 10.10.4. For me the solution involved disabling Cinch (a window management tool I had installed). This can be done by clicking on the Cinch icon in the menu bar then Disable Cinch, or from System Preferences > Security and Privacy > Accessibility (as MarcoB detailed in his answer).
More suitable as comments (but I don't have enough rep yet):
I just updated to Java 1.8.0_73 and to Safari 9.1 and the patch horchler posted no longer works.
MarcoB's command still works for fixing the crashes. But with this, no longer retina resolution in the Doc browser (so it looks ugly).