JSBreakpointModule: add document.readyState checks

[stsrki]

Closes #5482

[David-Moreira]

Looks ok, see comment for making sure the event is effectively attached? Also were you able to reproduce the issue? Or just trying to make the code more resilient?

[stsrki]

@David-Moreira can you take care of this PR?

[stsrki]

PS. I will rebase it to 1.6.

[David-Moreira]

@David-Moreira can you take care of this PR?

Wasn't this ready? What exactly do you want me to do here?
Do you want to patch 1.6 with this? I don't think I've seen many complaints about this? I'd probably do it for 1.7, what do you think?

[stsrki]

@David-Moreira can you take care of this PR?

Wasn't this ready? What exactly do you want me to do here? Do you want to patch 1.6 with this? I don't think I've seen many complaints about this? I'd probably do it for 1.7, what do you think?

I thought that you could finish the task. You had some comments previously about module loading and ready states, so maybe you could do it better.

[stsrki]

@David-Moreira can you take care of this PR?

Wasn't this ready? What exactly do you want me to do here? Do you want to patch 1.6 with this? I don't think I've seen many complaints about this? I'd probably do it for 1.7, what do you think?

I thought that you could finish the task. You had some comments previously about module loading and ready states, so maybe you could do it better.

PS. 1.7 sounds good to me.

[David-Moreira]

@stsrki
I guess at the point the module is called from .NET it's unlikely the DOM isn't loaded already. So my concern was probably not warranted.

Anyway:

• I added a check whether the ready state is in loading, go through the DOMContentLoaded
• Slightly refactored to exclude redundant comments.