File upload causes Firefox to be unresponsive and must close browser to continue. Tried all the fixes. Other browsers fine. Several computers.
Please if you have any suggestions, I'll try them. I thought a new clean computer might solve the problem, but no luck there either.
Could this note be referred please, to the FF programming manager? First my congrats on FF overall of course, to you and your many volunteers. But I notice a large phil…
Could this note be referred please, to the FF programming manager? First my congrats on FF overall of course, to you and your many volunteers. But I notice a large philosophical programming problem which you might consider.
This problem mostly shows with multiple tabs open. Web servers certainly are slow, and many pages' Html etc poor. This all results in lots of delays such as reported during:
Waiting for () Read () Transferring data from () Performing a TLS handshake to () Connecting to ()
These display the moving "working" dot in the left of the affected tab title. And less often, "(not responding)" in FF's title bar, which eventually gets cleared automatically.
I have reviewed all 17 screens, and a number of the individual results, from today's FF forum search of:
169 results for (not responding) for Firefox
None address the lack of prioritized co-operative multi-tasking/ threading, DURING such delays as "Waiting for ()". During such a necessary wait, it is very slow at best, e.g. for a user to switch tabs. Even to one which is ready for display.
Responsiveness to user input should be the top multi-tasking priority. Tab switching. Rendering/ display of the foreground tab. Scrolling that down. Tab closing by user!, and "X" to STOP a page from loading -- give those user clicks priority. Let's not have to wait 10 seconds for a right-click to open its option box. Let the other busy tabs finish up their work, overlapped in the background priority-wise.
This could be done now, but perhaps it would be difficult for volunteer programmers. Worse case might require a custom replacement, for the effective TCP part of the default vanilla TCP/IP stack. However I suspect a lot could be fixed short of that, with the correct management encouragement and guidelines. At least if the continuous motion of the "busy dot" indicator in the tab title is a task, just change that to something like just gray-ed out while busy.
My experience is with much headroom: CPU (50%), memory, disk, and network bandwidth, per Task Manager. NO McAfee. Mainly just ZoneAlarm taking 30% of that CPU 50% usage. This is not a problem with start-up delay. And delays within only one open tab are necessary, of course. Cheers
Hi, I'm just working on a new website, and I noticed something odd that happens only when I open the site via Firefox. On browsers like Safari and Chrome the rgb hex colo…
Hi, I'm just working on a new website, and I noticed something odd that happens only when I open the site via Firefox. On browsers like Safari and Chrome the rgb hex colour looks identical as in Adobe Photoshop or Apple Pages, where I created content, but Firefox seems to oversaturate the fonts quite nasty for some reason.
I attachted you a screenshot where it should be very visible. If this is a bug, is it possible to get this fixed soon? I don't really want to put a warning on my website for Firefox users if possible.
A) i tried with shape css code it doesnot open the webpage as it shouldbe. It shows ignoring shape code. B) whenever I click links it takes me to unwated webpages please …
A) i tried with shape css code it doesnot open the webpage as it shouldbe. It shows ignoring shape code. B) whenever I click links it takes me to unwated webpages please advise.