What the heck is with this noise?!? I am scrolling down an Arduino document page and the durn thing resets my vertical scrolling position. I don't want to scroll over the same piece of the page eternally, I want to move around and see what else there is on the same page. If I disable Jabbascrapped to stop that from happening then all the content disapears. What a pile of scrap (POS).
Does someone know what piece of JS is doing this ugly thing? If I could find it I could add a function killer to my Chrome and Firefox so that I could visit these pages without the annoyance of bouncing up to previously-viewed content. Otherwise the pages are kinda kaka.
I have experienced the same. Refresh the page. Call @ptillisch who may have the status of this as a known "feature." : )
no particular page or topic.
@MartySchrader - I feel the problem is (our?) CPU running on Win11. I do not get this problem with Linux Mint LTS. Surf to an Adafruit web page. Scroll down. Do you experience a "half page cutoff?" I can not duplicate it now, but it literally has half a page of "black" until you scroll past the black.
In JavaScript and the web context in general, the term document refers to the Document Object Model (aka DOM), which represents the structure of a web page.
It's essentially an object-based interface that allows JavaScript to interact with, manipulate, and update the content, structure, and styles of an HTML or XML document dynamically.
I'm assuming that OP found a web page where there is some sort of JS running that prevents her/him to see the whole page (document) ➜ OP assumes there is a JS function messing with the DOM as he scrolls around.
A function killer is essentially a redefinition or "stub" for a problematic function. By replacing it with a no-op (a function that does nothing) or a safe implementation, you effectively stop or "kill" the original function, preventing it from executing. Chrome and Firefox support extensions to automate the injection of JavaScript into web pages, and you can specify the pages where the script should run using the extension manifest.
Wow, why so complex, a simple txt file or if fancy is need rtf seems like it would work as well. I suspect it creates more jobs, so I guess that's a good thing.
The experience is: Imagine a spring attached to the forum web page... as you scroll down, the spring pulls you back to the location from which you scrolled.
JavaScript can also suffer from proprietary extensions. Windows and Apple are known for creating their own browsers using proprietary HTML extensions. In the wayback machine, NetScape Navigator was the defacto browser unattached to any hardware architecture. Netscape followed the most current HTML/CSS/JavaScript commands. Just like the CD and videotape wars... it is not always the best idea that wins.
JavaScript allows web sites to run on a front-end HTML template with one line linking to a source file written in JavaScript (flat text), which contained current data, but easily live-changeable, residing on the host. JavaScript also allowed avoiding monthly databases charges needed by modern web site content management software.
Oddly enough, this effect only seems to happen on Chrome. I hadn't used my other web viewers to look at Arduino docs up until now. No problems on Firefox and Seamonkey. On MX Linux Chromium works fine as well. What has the crew at Arduino.cc done to make the Windows version of Chrome behave in this fashion? And how can I fix it if they won't?
As I said above, it only seems to be happening with Chrome on Windows. Firefox and Seamonkey don't show this effect, and Chromium on Linux is also clean.
