Im developing a fairly normal web application using Angular2. I've run into an annoying problem: From time to time scrolling up and down does not work.
There is no errors or anything to indicate why this problems occurs. Only solution is to refresh the page, and scrolling will work again. This problem has been observed in all major browsers (Safari, Chrome, and Firefox).
Does anyone know what might be the root of this problem? and on use of this.router.navigate() the navigated page has no scrollbar until i refresh the page manually.
Faced the same issue. my issue was there wee popups which i used, using ngxsmartmodal. After closing needed to remove it which i was not doing.
Related
Recently I've been testing my website using screen readers and ran into a page that lags like crazy when using NVDA. More specifically:
All browser actions are substantially delayed, but NVDA itself runs perfectly fine
For example, the page normally loads in its entirety in less than a second, but with NVDA active, the first image can take several minutes to render
Refreshing the page takes several minutes to execute
Even switching or closing the tab takes several seconds
After some extensive debugging, I isolated the issue into a rather specific set of criteria causing the slowdown:
This only happens on Firefox (I'm currently on Firefox 90); Chrome and Edge are fine
This only happens with NVDA; VoiceOver on Mac is fine even on Firefox. I do not have JAWS.
The action causing a slow down is setting an element's textContent on every requestAnimationFrame, so it's happening dozens of times per second
I am uncertain if this is experimentally significant, but I'm running on Windows 10 Home
I managed to scrape together a minimal CodePen example. I used CodePen here because the simplest way I could replicate the issue was by refreshing the page. In the example is a refresh button that activates a spinner, so if the page is fast the spinner will show up for only a brief moment; if it's slow then you'll get to observe the spinner in all its glory.
What I see when I try to refresh:
So while I isolated what is causing the issue, I have no idea why this is happening and hence how to solve my original page's problem without deactivating the widget outright.
What might be the underlying cause(s) of Firefox/NVDA slowing down on a page setting textContent?
Is there an alternative to setting textContent that I can or perhaps should consider?
Is this perhaps an issue that should be filed directly with either Firefox, NVDA, or both?
Thank you!
Addendum:
NVDA Github Issue: This open issue indicates long pages are slow to load, which may be related to my problem
My Website's Page: The page on my website I'm talking about
We have recently changed our navigation menus. They have been working fine for everyone except for one user only when that user is using chrome.
The menu will render when they hover over an option the first time but after that, no menus render (see screenshots).
We are using the exact same version of chrome rendering the same website. Has anyone else ever experienced anything like this or have any ideas what could cause this?
Working:
Broken:
Looks to me very much like a caching issue. Some of the JavaScript or CSS from before the update may still be stored in the user's browser cache.
To resolve this, clear Chrome's browser cache.
You can access the relevant dialog via ctrl+shift+del.
I was finally able to resolve the issue.
Firstly, everyone was using the same version of chrome in incognito mode with no extensions and a cleared cache so we're still not sure why only one specific user was getting the issue and no one else. Also that user was 2000 miles away so we could not physically debug on that machine. (It was an manager/admin with sensitive info on the machine so RDP was also not an option)
I was finally able to reproduce the issue by testing using Chrome Canary and discovered that the issue was directly related to hiding the sub-fly-out menus off screen using left -999999999px instead of display: none. Apparently just holding the '9' key down for a few seconds was a bad idea and it seemed to cause an overflow error of some kind and changing the left value to -9999px instead fixed it for that user and everyone else in Chrome Canary.
Thanks to everyone who contributed.
Good day,
I have a problem with IE and iframes.
So I have a huge application with legacy code, designed in early 2000. iFrames are used everywhere.
When something big is loaded inside the iframe, there is no display in browser throbber. So the loading icon starts spinning only when the main page is loaded, not iframes, so its impossible to say if anything is happening at all.
The users complain, that IE10+ gives them this problem, earlier versions worked. For me IE9 also has this issue.
Unfortunately, it is impossible to use JS on every page and manually add the 'loading please wait' icon or message, there are more than 100 pages with more then one iframe on each.
Chrome works fine, but nothing except IE can be used.
Could you please recommend solution for this trouble?
I have a fairly long page with the Facebook comments widget at the bottom. With this widget in place the page jumps to the bottom on loading in IE7 and IE8. Whenever I remove the widget the page loads normally. This doesn't happen on any other browser. Can anyone suggest any way to prevent this? I've tried appending the .fb-comments div and calling FB.XFBML.parse() on it on document ready, but the behaviour in this case is the same.
This is a Facebook bug. I think they are working on it. If you go to the developers area on FB is a thread discussing it.
Also occurs in IE9, no updates in the last weeks for my web applications, should be a facebook bug or IE bug
I've developed a responsive-based website for a client, however upon testing on Blackberry OS5 (old, I know, but it is a requirement of the job) we have found that a lot of the elements on the page are invisible. I say invisible because the spacing is there where the elements should be, there are just blank spaces.
I started to debug the issue, and I found that disabling support for JavaScript in the browser causes the website to render fine. This led me to think that some of the JavaScript on the website was causing the issue, however upon removing all references to JavaScript on the website, the issue still occurs.
Any ideas?