| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Initialize locationPrototype.$$absUrl to avoid exception when base href and current location have different dommains. Closes #11091
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Sorry, something went wrong.
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Sorry, something went wrong.
|
Hi, I just signed the CLA. |
Sorry, something went wrong.
|
Seems reasonable, but one can never be too sure with $location stuff 😛 (The CLA thing doesn't seem to have worked btw...) |
Sorry, something went wrong.
|
I signed the CLA with another account. My mistake. |
Sorry, something went wrong.
|
CLAs look good, thanks! |
Sorry, something went wrong.
|
CLAs look good, thanks! |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Initialize locationPrototype.$$absUrl to avoid a crash when base href and current location have different domains.
What is the current behavior? (You can also link to an open issue here)
#11091
What is the new behavior (if this is a feature change)?
Does not crash anymore.
Does this PR introduce a breaking change?
I don't think so...
Please check if the PR fulfills these requirements
Other information:
Closes #11091