My memory lied to me that it was JS, but I checked with older research browser that is much more secure than these modern automatically leak everything browsers and that old browser does it while new one does not. spy scripts in Xenforo of course, so there is JS, but those are everywhere these days.Īnyway go to Tools -> Web developer -> Inspector to browse trough things, not sure if there is anything to spot though, but maybe someone figures out something. Idk, probably something out of the scope to be able to fix easily as it might be Xenforo thing that has came in some update. I'm not sure why thing happens though, div uix_paneContainer thinks it's enough big to require scrolling, some auto detection probably not working quite perfectly? Cybersecurity is turned to be leech everything from users and secure corporate sites with helps of collected data these days and browsers are made to support that view. New browser is Waterfox Alpha 68.0a1 which does not get that odd browsing issue, but it is as bad as IE in so many ways, despite claimed to be secure. My research browser is ancient Cyberfox 52.4.1, because for that there still was extensions that can block everything so malicious sites are not a problem.
I find this really annoying, is it just me?Ĭlick to expand.My memory lied to me that it was JS, but I checked with older research browser that is much more secure than these modern automatically leak everything browsers and that old browser does it while new one does not. If you are in the middle of a page the scrolling works fine, but if you have just loaded a page or have hit the top or bottom then the scrolling is lagged. Why is it counting the extra scroll attempts and adding it onto the page length? If I get to the top or bottom and continue trying to scroll, why do I have to count back through all the failed scroll attempts before the page moves in the other direction? CharmCit圜rab makes some intelligent and well-written comments. Funny, they are poor at receiving criticism about Pale Moon, yet, they have no problem throwing Alex and Waterfox under the bus. when you want to go back up you have to give 5 flicks of the scroll wheel before the page starts going up again. Apparently the Moon-Matt team over at Pale Moon have big issues with the new Waterfox v68 Alpha.
Say you hit the bottom of the page and keep scrolling down 5 more flicks of the scroll wheel. Its kind of like the end stops on the scroll bars don't actually stop at the end of the visual range. One of the scroll bars only ever has one pixel of movement while the other one seems to do all the work. There seems to be two scroll bars on the right hand side and I have a feeling that might have something to do with it.
#WATERFOX ALPHA SOFTWARE#
On the other side, there will not be any reason to keep that version if its got issues though it would be good to try to nipp as many of these issues in the bud and I think unlike mozilla and its view on security and accessibility software the people behind waterfox won't be so stupid over it.I'm not sure if it's just me, but when I try and scroll up or down a page it takes 4 or 5 flicks on the scroll wheel before the page actually scrolls. If classic addons work on 68 like noscript 5x or even if some of the newer stuff is accessible I will try to see what that does.
#WATERFOX ALPHA UPDATE#
Now I will of course see later on if I can update and see what goes and what loads. Waterfox 56.x branch will be renamed waterfox classic and will continue as it is till the end of time most likely. Waterfox will be modernised and people will be encouraged to use the latest and greatest. Its good to know that unlike firefox, all that will happen is that waterfox will simply split in half. I would encourage anyone and everyone to test this. Unlike firefox quantom it does appear that generally things do load in an accessible manner but there are a lot of changes under the hood. I don't have any way to contact the devs directly about us screen reader users but it would be good to well have them on board. However, it appears that the older waterfox while itself will be eventually dieing when 68.0 comes out is not going away in fact according to the waterfox blog its going to be called waterfox classic, and will remain being updated with security and bugfix updates when possible, there won't be any schedual as such but both branches will be active, its just that eventually all addons will be updated for the alpha version.Īccording to the blog, there are addons updating, it stresses its the first alpha. I assume it uses the newer quantom inaccessible interfface sadly. This is not strictly an nvda issue, however I know a lot of us use this so I thought I'd put it out.įrom inital useage the only major issue I found is that extentions seems to not be accessible or at least none of my addons show.