I am seeing Chrome crash with just before OOM and it is related to the onBlur of a TextField, even if it's just a simple console.log of the event, any ideas / pointers? This is using 3.9.1.
onBlur={evt => { console.log(evt); }}
My specific issue was caused by #sentry/browser
Upgrading from 4.5.4 to 4.6.4 fixed it
Related
I've noticed strange behaviour using material ui tabs with i18next npm package (useTranslation hook) - for localize my buttons. The main problem is: bottom indicator doesn't recalculate its position after page reload, but when I comment my useTranslation hook - everything is ok. my hook looks like this at top of component:
const { t: tc }: UseTranslationResponse = useTranslation('common');
I don't see any dependency here or any asynchronicity problem why this happens. Any ideas? Thanks
I faced the same issue today. Just like you, I'm using react material tabs with i18next.
To solve this problem, I forced namespaces load on i18n initialization.
I don't know why this bug happens, but this workaround works for me.
i18n.init({ns: ['components', 'pages', 'common', 'generalData']})
You're probably loading your translations asynchronously? Using i18next-http-backend maybe?
Then you may not be using Suspense and also not waiting for the ready flag: https://react.i18next.com/latest/usetranslation-hook#not-using-suspense
I just updated my application from the old Dnd extension to Dnd5 and I'm now seeing multiple/many server AJAX calls (usually 5 or 6) when I hover over lazy-load nodes while dragging. I have only implemented the dragStart, dragEnter, and dragDrop callbacks, and I only see the dragEnter callback being called once when I hover. Is there some special handling or response required from the lazyLoad callback to prevent this? I should also point out that I also updated to the latest version of Fancytree (2.34.0) so perhaps something else has changed that is causing this? (My tree works fine otherwise.)
Thanks!
Seems you found a bug. This will be fixed in Fancytree 2.34.1
When I try to hover a hyperlink- ( anchor tag ) through automation using protractor in Chrome, I observed that hovering is not persisted. I can see the mouse over event but then it immediately stops and it is not waiting until the next action to perform because after hovering I need to verify a tool tip.
As mouse over is not waiting for the next action, I'm not able to verify the tool tip. I'm able to click the anchor tag but facing issue with hovering.
The code snippet that I used is
browser.sleep( 5000 );
var ele = element( by.xpath( '//tf-infobox//[normalize-space(.)="Error 1"]/following-sibling:://a' ) );
browser.actions().mouseMove( ele ).perform();
browser.sleep( 5000 );
Node Version: 4.2.2
Protractor Version: 3.1.1
Chrome Version: 52.0
Chrome driver version: 2.21
Additional Info: Hovering issue is seen only for hyperlink - anchor tag but not for the other elements.
Can someone help me out to solve my problem.
Thanks!
I have a similar test for a tooltip, and I use browser.wait(tooltip.isPresent(),5000) to wait until the tooltip is added to the DOM before I check its contents.
I found a solution for this.
I used jquery command in the scripts like
browser.driver.executeScript( '$('tf-infobox tf-spotlight:contains('Error 1') a').mouseover(); ' );
There are some issues with dropdowns and inputs as well but when I use jquery commands in the scripts they worked for me. So I am guessing with the latest version of webdriver there are some issues
We use the ag-grid in different parts of our site and with protractor tests where a test opens a component that contains the ag-grid the test freezes and nothing happens anymore. The test case is not being completed.
This happens as soon as the ag-grid is getting initialized. If I remove the grid, then the test case continues fine. This behavior is the same in every location where we're using the ag-grid.
Is this an issue or what else could be wrong here?
I have not found a way around this, but I can tell you its related to the setTimeout underneath the hood. I wound up using browser.ignoreSynchronization = true, and then doing specific Waits with ExpectedConditions.presenceOf. Very sloppy and hopefully ag-grid fixes this at somepoint.
I have a GWT application, with some buttons. These buttons seem to be unresponsive sometimes, i.e., clicking on them does nothing. Has anyone faced this problem before ? is it to do with the browser compatibility ?
PS: I am running the GWT development mode on MAC OS if that is relevant at all.
I encountered this in the past when an element in the widget hierarchy was added via getElement().appendChild() instead of .add()
See http://comments.gmane.org/gmane.org.google.gwt/78360 for a related thread.
-Clint