Skip to content

Commit c0f183e

Browse files
committed
acrolinx
1 parent 9074650 commit c0f183e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/active-directory/develop/msal-js-use-ie-browser.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,23 +26,23 @@ ms.collection: M365-identity-device-management
2626
Microsoft Authentication Library for JavaScript (MSAL.js) is generated for [JavaScript ES5](https://fr.wikipedia.org/wiki/ECMAScript#ECMAScript_Edition_5_.28ES5.29) so that it can run in Internet Explorer. There are, however, a few things to know.
2727

2828
## Authoring an application to run in Internet Explorer
29-
If you intend to use msal.js in applications that can run in Internet Explorer, you will need to add a reference to a promise polyfill before referencing the msal.js script.
29+
If you intend to use MSAL.js in applications that can run in Internet Explorer, you will need to add a reference to a promise polyfill before referencing the MSAL.js script.
3030

3131
```html
3232
<script src="https://cdnjs.cloudflare.com/ajax/libs/bluebird/3.3.4/bluebird.min.js" class="pre"></script>
3333
```
3434

3535
This is because Internet Explorer does not support JavaScript promises natively.
3636

37-
## Debugging an application runing in Internet Explorer
37+
## Debugging an application running in Internet Explorer
3838

3939
### Running in production
40-
If you deploy your application to production (for instance in Azure Web apps), this will normally work fine, provided the end user has accepted popups. We tested it with Internet Explorer 11.
40+
Deploying your application to production (for instance in Azure Web apps) normally works fine, provided the end user has accepted popups. We tested it with Internet Explorer 11.
4141

4242
### Running locally
43-
If you want to run and debug locally your application running in Internet Explorer you need to be aware of the following considerations (assume that you want to run your application as *http://localhost:1234*):
43+
If you want to run and debug locally your application running in Internet Explorer, you need to be aware of the following considerations (assume that you want to run your application as *http://localhost:1234*):
4444

45-
- Internet Explorer has a security mechanism named "protected mode" which will prevent msal.js to work correctly. Among the symptoms, after you sign-in, the page can be redirected to http://localhost:1234/null.
45+
- Internet Explorer has a security mechanism named "protected mode", which prevents MSAL.js from working correctly. Among the symptoms, after you sign in, the page can be redirected to http://localhost:1234/null.
4646

4747
- To run and debug your application locally, you'll need to disable this "protected mode". For this:
4848

0 commit comments

Comments
 (0)