It's bound to have repercussions on the direction the greater webz take etc.
IE only type sites and stuff with Chrome ? Nope don't really see that happening, still too much influence in Goog's hands atm. It's just a reality and not something any developer can ignore.
Still though when any one browser reaches 2/3rds or so share, yep web-devs are going to devote more efforts to making sure it's supported on sites-etc they create. doubt Goog Inc will take it to the extremes M$ did, as long as they keep things above board and web-standards compliant. Mozilla has to have some serious browser dev skills by this point, been in the field for a LONG time. Had to cook dinner/eat and go grab some brew. Plus it's somewhat annoying and takes mucho bandwidth keeping them all upgraded, so with no web-dev going on, don't need them right now. Don't need to do any cross-browser testing atm, so got rid of Chrome, Chromium, Opera for now and only have a couple versions of Firefox. So reasonable about:config tweakage I feel is prudent, at least it's the way I prefer things. Tend to lower these from 10, a bunch of this little stuff can no doubt add up in terms of system overhead the browser is using. Max windows undo, default is 3, I set it to 1, am I really ever going to need to reopen 3 FF/windows I've closed ? Same for max tabs undo, or serialize back tabs thingy. Some of it is about:config tweaks too, mentioned no longer do much fiddling with that, stuff like disable prefetch, changing the session store frequency, by default it saves a users session every 15secs, I set this at 300000 or longer and it doesn't seem to matter, looks like FF now saves session on close/crash anyway. It may be a good idea to test this on the local system to find out if the local Firefox installation is affected by the issue.Anal edit, though technically would need a list of those 8 sites, to really get an accurate and comparable results. Reports suggest that some users managed to reduce the Firefox web browser's memory usage after disabling the service others on the other hand reported that changing the setting did not impact memory usage. While it is still possible to turn them off using about:config, it is probably not something that most users know about or feel comfortable using. To make matters worse, Mozilla did remove options to control the desktop browser's accessibility settings from the preferences some time ago. Firefox users who are experiencing performance issues while using the Firefox web browser on desktop systems and on Android, may improve performance by disabling the browser's accessibility services.Ī bug opened on four days ago suggests that Firefox's Accessibility Service has a memory leak that is causing performance degradation, especially on heavy webpages.
0 kommentar(er)
