Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

last 2 Firefox updates have each broken some of my scripts

  • 2 replies
  • 0 have this problem
  • 2 views
  • Last reply by csuflinux

more options

After making a jump to FF 105, my virtual bookmark function started landing on different places each time I invoked it, even though I wasn't changing the window.pageYOffset value. Now after updating to FF 106, where I had the option of setting that value using the onLoad option, the page remains absolutely blank until I confirm or reject the window.pageYOffset value. Since I cannot see where on the page I am positioned (because it won't finish loading) it is now useless. This tool had been my most frequently used function for many years as I could reposition to a desired location by merely pressing my home key. OnKeydown it would jump to the top of the page and onKeyUp, it would return me to virtual bookmarked position, no matter where I was on the page. For some of my pages, I would invoke it more than once in less than a minute. It was really useful!. (Now it is useless!) These problems happened immediately after each FF update.

 /russ
After making a jump to FF 105, my virtual bookmark function started landing on different places each time I invoked it, even though I wasn't changing the window.pageYOffset value. Now after updating to FF 106, where I had the option of setting that value using the onLoad option, the page remains absolutely blank until I confirm or reject the window.pageYOffset value. Since I cannot see where on the page I am positioned (because it won't finish loading) it is now useless. This tool had been my most frequently used function for many years as I could reposition to a desired location by merely pressing my home key. OnKeydown it would jump to the top of the page and onKeyUp, it would return me to virtual bookmarked position, no matter where I was on the page. For some of my pages, I would invoke it more than once in less than a minute. It was really useful!. (Now it is useless!) These problems happened immediately after each FF update. /russ

All Replies (2)

more options

Hi Russ, for what it's worth, I don't see any compatibility notes on https://developer.mozilla.org/docs/Web/API/Window/pageYOffset so if there was a change, it probably was not intentional.

Is there a test page demonstrating the problem somewhere (that doesn't require a login)?

When sharing a link to a non-Mozilla site, you can put a space before the top level domain to bypass the spam link moderation queue:

https://www.example .com/somepath

more options

I apologize to the community for having specified what are very likely two different issues in one post. (I suppose it is too late to split them apart, but I am willing to do that if someone can advise me how to go about it.) I appreciate your checking page.YOffset. I didn't think it was deprecated, but I hadn't confirmed it. (I didn't know where to research that.) I developed a homegrown script that uses the page offset (issue #1) I use as a tool, not just on my pages (which are offline now), but on any page where I want to place virtual bookmark. It is pretty much a simple "bookmarklet" piece of code I employ when I see something I may want to either frequently return to or relocate a "needle I found in a haystack" of text. Each time I press my designated "return to bookmark" offset key, it seems to go to different offsets that are in the vicinity of where I want to go, but are somewhat inconsistent. The offset is established thusly:

       if(window.pageYOffset) vertPosit = window.pageYOffset;
       else if(document.body.scrollTop) vertPosit = document.body.scrollTop;
       else {
           alert('Unable to determine offset for this browser');

On some of my own pages that are date or time sensitive, the tool is invoked using the HTML BODY onLoad option which is now having the before described (issue #2) of not being able to see whether I should or should not confirm the script. Note: these issues appeared at different update release levels; 105 then 106. As this may not have a quick or simple resolution, I am willing to take this process offline and later return the solution to the community once it is resolved.

 /russ