I'm having a dashboard containing ten c3.js graphs.
Rendering takes 900 ms in Chrome, but 4600 ms in Internet Explorer 11 (10-modus).
When profiling, the getBoundingClientRect method takes a lot of time (2995 ms).
I already tried putting the dom element to visibility hidden, etc.
Any idea why and how to improve the Internet Explorer performance?
Try adding the following CSS solved the problem entirely: svg { position: absolute !important }
Related
I taught myself Vue.js a couple of days ago in the evening and already created my first application yesterday which will soon be used by tens of thousands of users on a daily basis. The original was made with HandleBars and jQuery.
The only thing I couldn't get to work as of yet is the following piece of code:
$(".conversation-container").animate({ scrollTop: $(".conversation-container").prop("scrollHeight") }, 10);
I tried with the following:
var container = this.$el.querySelector(".conversation-container");
container.scrollTop = container.scrollHeight;
but unfortunately that didn't provide the same behavior.
Anyone can help me out to accomplish this so I can take jQuery out of the page and go solely Vue.js?
There is no one liner solution to get smooth scroll animations in vanilla JavaScript. If you want pointers on how to attain the same behavior please reference this answer:
Cross browser JavaScript (not jQuery...) scroll to top animation
We've been build a site for quite a while and I am implementing UI UnitTesting.
It relies heavily on overlaying buttons with "proxies" to allow for more capabilities like dragging from one iframe into another. From a testing perspective, I want/need to "click" the button. It should click the proxy element overlaid on it. Then the test can continue. This works in IE and even Chrome, but when we went to test on the Build Server it failed with the error
threw exception: System.InvalidOperationException: unknown error:
Element is not clickable at point (265, 87). Other element would
receive the click: div class="v-iframe-proxy" style="width: 100%;
height: 100%;" /div
I am hoping there is a way to ignore this condition and click anyway. Any help would be awesome.
I believe that you have 3 options here:
1. Perform click using JavaScript like this:
((JavascriptExecutor) webdriver).executeScript("arguments[0].click()", elementToClick);
Try to click using new Actions(webdriver).click().build().perform();
Surround your click with try catch and continue execution.
I think that your UI tests work on headless browser in the server side. So you need to set width and height initially.
If you print size of the window, you'll see: 0,0
System.out.println(driver.manage().window().getSize());
So you can set window's size as 1024x600 (or whatever you want):
Dimension d = new Dimension(1024,600);
driver.manage().window().setSize(d);
This morning my Chrome has been updated to version 44 and dojo editor widget I am using in my projects no longer works in some cases.
It seem to be working fine when used on a plain html page, but when using on modal window or inside an element with positioning the content of iframe becomes invisible due to zero width and being positioned at the left top corner of the browser.
Even dojo editor example in the documentation (http://dojotoolkit.org/reference-guide/1.10/dijit/Editor.html) does not work in Chrome 44.
Any help?
Edit: as a temporary workaround, we found this solution is working for us when loading the content of an editor into iframe:
this.iframe.style.display = "none";
setTimeout(dojo.hitch(this, function() {
this.iframe.style.display = "";
}), 100);
I'm trying to test a site with Selenium Grid via recordings from Selenium Builder. Everything seems to work for Firefox and Chrome on Windows and Mac, but I'm getting error messages when testing in Windows 7 + IE11.
Whenever I try to select or interact with an element I get:
Exception: Unable to find element on closed window
HTML element I'm waiting for is loaded after page load via jQuery and appears on page as:
<input id="email" name="username" type="email" autofocus="autofocus">
Selenium Builder Step waits for it to appear before continuing:
{
"locator": {
"type": "id",
"value": "email"
},
"type": "waitForElementPresent"
},
From various posts of people with similar problems I have done the following to try and rectify:
Made sure the security zones were all the same in IE 11
Made sure I wasn't using any "FLAKY" options anywhere (INTRODUCE_FLAKINESS_BY_IGNORING_SECURITY_DOMAINS)
Should I be accessing elements in a different way? Or is there an IE 11 setting I'm missing?
According to the Selenium IE guide (https://code.google.com/p/selenium/wiki/InternetExplorerDriver) IE 11 has a known problem where security zones can cause issues even when they are all set correctly.
The best option is to downgrade from IE 11 to IE 10 (How to downgrade from Internet Explorer 11 to Internet Explorer 10?)
This solved this issue.
A while ago noticed this strange behavior with IE(Cant remember which version), using Selenium and C#:
When an element is clicked for the second time, the whole thing freezes.
My fix was to keep track of all clicked elements in order to avoid repeated clicks.
This fixed some of the issues I was having with IE.
Hope it helps.
I recently by accident found an issue I have with a web application I have made entirely with dojo.
I have a TabContainer and a toolbar with buttons and each button adds a Tab in the TabContainer.
Each of these new Tabs has as children, created programmatically, one or more of the following BorderContainers, ContePanes, Editors, FilteringSelects, Uploader and Buttons. I should point out that I do not have parseonLoad: true byt false and I call manually the parsers.parse when required. I should point out that in the ContentPanes in the content attribute I put also declarative filteringSelects and ValidationTexts and Uploader I hope that is not a problem.
Everything is working great in all browsers even in IE9 besides one thing in Firefox 12.
When I create many new tabs and the ScrollingTabController gets created (The left/right and dropdown arrows of the tabstrip) when I use the ScrollingTabControllerMenuButton (the down arrow at the far right) the TabContainer behaves wrongly and eventually freezes. Firebug shows weird errors when I select different tabs via this menu of the tab strip. Errors of the buttons that I have in these tabs, weird errors mentioning StackController or ScrollingTabController
[ e.g.
button is undefined
if(this._selectedTab === button.domNode){ StackController.js (line 222) ]
different each time...
This weird behavior only happens in Firefox. IE9 and Chrome do not have any issue at all!
Could anyone have an idea on what might be the problem? Is it a known bug? Is it a problem that I have many widgets in each Tab ?
It seems that it is indeed a browser specific bug and as I was told it should be fixed in the following releases
I first reported it to the dojo community and from there they reported it to the Firefox team
http://bugs.dojotoolkit.org/ticket/15496