SharePoint Online/2019 javascript/spfx click/popstate not working

Are you working with SharePoint 2019?

Maybe making some SPFx Extensions? 

popstate not working? 

click not working? 

MutationObserver not working? 


well, take a look at this


As you can see, Microsoft are intercepting every click in the page, while stopping any bubbling.

Therefor, any window/document/body onclick event will not work, in case you are trying to globally catch it.

Same for popstate or MutationObserver.

*Note - on SPO it seems that popstate event works.


Solution - make an interval to keep watching href change:

let xPrevLocation = location.href
let xOnLocationChangeFunctions = []
setInterval(()=>{
    if (location.href != xPrevLocation){
        console.log("interval location change", xPrevLocation, location.href)
        xPrevLocation = location.href
        for (let i=0; i<xOnLocationChangeFunctions.length; i++){
            xOnLocationChangeFunctions[i]();
        }
    }
}, 350)

Usage:

window['xOnLocationChangeFunctions'].push(()=>{
   //code...
})


My Scenario:

I've added some scripts via Extension, but when user changed a page, I needed to re-run those scripts, like page load/ready. 

*Note - this is not really page load/ready, just a notification that the page has changed location


Upgrade - run it aslo 1st time, so that xOnLocationChangeFunctions can be used for 1st time also


let xPrevLocation = location.href
let xOnLocationChangeFunctions = []
let xIsFirstLoad = true;

setInterval(()=>{
    if (location.href != xPrevLocation){
        console.log("interval location change", xPrevLocation, location.href)
        xPrevLocation = location.href
        for (let i=0; i<xOnLocationChangeFunctions.length; i++){
            xOnLocationChangeFunctions[i]();
        }
    }

    if(xIsFirstLoad == true){
        xIsFirstLoad == false
        for (let i=0; i<xOnLocationChangeFunctions.length; i++){
            xOnLocationChangeFunctions[i]();
        }
    }
}, 350)







Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX ...
Read more