Skip to content

Commit bc18899

Browse files
committed
🐞 fix iframe references in docs
- there's no word 'iframe' so the content is incorrect - replaced with code reference to the HTML element
1 parent 30ee8ef commit bc18899

15 files changed

+132
-138
lines changed

docs/design/ui-text-for-web-parts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: UI text guidelines for SharePoint web parts
33
description: Use simple, understandable, and concise UI text to create effective web parts in SharePoint.
4-
ms.date: 06/28/2022
4+
ms.date: 03/08/2023
55
ms.localizationpriority: medium
66
---
77

@@ -134,7 +134,7 @@ Hint text, or ghost text, is the text element you display in a UI element, typic
134134

135135
- Repeat the label. For example, if you have a text box with the label **Name**, the hint text **Enter name** is redundant and potentially confusing.
136136

137-
The following hint text is for the embed web part. The text field can accept a secure website address or an iframe embed code. The text shows an example of both.
137+
The following hint text is for the embed web part. The text field can accept a secure website address or an `<iframe>` embed code. The text shows an example of both.
138138

139139
<img alt="Web part hint text" src="../images/design-uitext-06.png" width="800">
140140

docs/scenario-guidance/Development-models.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Development models
33
description: Development models
4-
ms.date: 06/28/2022
4+
ms.date: 03/08/2023
55
author: vesajuvonen
66
ms.author: vesaj
77
ms.topic: article
@@ -51,7 +51,7 @@ The SharePoint Add-In model is a development model for SharePoint Online and Sha
5151
This goal adheres perfectly to the cloud offering model and philosophy. Users can discover and download SharePoint Add-ins from a public SharePoint add-in store or from their organization's corporate add-in catalog. With the SharePoint Add-In model you can create SharePoint-hosted and provider-hosted solutions. The former are just client-side and JavaScript based applications, hosted in SharePoint. The latter typically are .NET applications hosted on Microsoft Azure, or on any other hosting platform. With the SharePoint Add-In model you can create:
5252

5353
* Full-page solutions: an immersive full-page experience that can have the look and feel of a SharePoint page.
54-
* App-Parts: parts of a webpage, using a special kind of control called an add-in part, to surface an iframe element that contains the add-in.
54+
* App-Parts: parts of a webpage, using a special kind of control called an add-in part, to surface an `<iframe>` element that contains the add-in.
5555
* UI Custom Actions: UI commands that extend ribbons and menus for lists, documents, and more.
5656

5757
Moreover, a SharePoint Add-in can include classic SharePoint components such as lists, custom website pages, web parts, workflows, content types, and many other artifacts.

docs/solution-guidance/Sandbox-Solution-Transformation-Guidance-WebParts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Replace web parts in sandbox solutions
33
description: Learn about the options and strategies of converting existing functionality to the SharePoint Add-in model or alternative solutions.
4-
ms.date: 06/10/2022
4+
ms.date: 03/08/2023
55
ms.localizationpriority: medium
66
---
77

@@ -11,14 +11,14 @@ One of the reasons many developers have leveraged code-based sandbox solutions i
1111

1212
Another option is to rewrite the web part as a client-side solution. This involves redesigning the solution to use JavaScript, HTML fragments, and one or more supporting frameworks. While this is net-new work, it has the added benefit of setting up your solution to easily integrate into the upcoming SharePoint Framework. This is a great choice for simple display or data entry web parts, and can scale up to full-page client applications.
1313

14-
> [!NOTE]
14+
> [!NOTE]
1515
> [Code-based sandbox solutions were deprecated](https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/) in 2014, and SharePoint Online has started the process to completely remove this capability. Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016.
1616
1717
## Options for replacing web parts
1818

1919
|Approach|Design considerations and more information|
2020
|:-----|:-----|
21-
|Provider-hosted add-in client web part|<ul><li>Requires hosting infrastructure.</li><li>Hosting infrastructure must be highly available.</li><li>Client part is displayed in an iframe limiting communication with the rest of the page.</li><li>Must use remote APIs either via CSOM or REST.</li></ul><ul><li>[Get started creating provider-hosted SharePoint Add-ins](../sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md)</li><li>[Create add-in parts to install with your SharePoint Add-in](../sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md)</li><li>[Client Web Part Definition schema](../schema/client-web-part-definition-schema.md)</li><li>[Set up an on-premises development environment for SharePoint Add-ins](../sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)</li></ul>|
21+
|Provider-hosted add-in client web part|<ul><li>Requires hosting infrastructure.</li><li>Hosting infrastructure must be highly available.</li><li>Client part is displayed in an `<iframe>` limiting communication with the rest of the page.</li><li>Must use remote APIs either via CSOM or REST.</li></ul><ul><li>[Get started creating provider-hosted SharePoint Add-ins](../sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md)</li><li>[Create add-in parts to install with your SharePoint Add-in](../sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md)</li><li>[Client Web Part Definition schema](../schema/client-web-part-definition-schema.md)</li><li>[Set up an on-premises development environment for SharePoint Add-ins](../sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)</li></ul>|
2222
|Client-side solution|<ul><li>The ability to embed JavaScript in the prescribed way (through a UserCustomAction) does not work currently outside of the classic experience. For these cases you can link to the files by using a Script Editor web part.</li><li>Cannot elevate permissions, instead use a micro-service with add-in-only permissions.</li><li>Limited by permissions of current user.</li></ul><ul><li>[Simple React Form Sample](https://github.com/pnp/PnP/tree/master/Samples/SharePoint.React.SupportTicket)</li><li>[JavaScript Embedding Samples](https://github.com/SharePoint/PnP/tree/master/Samples/Core.JavaScript)</li><li>[Patterns and Practices JS Core](https://github.com/SharePoint/PnP-JS-Core/)</li></ul>|
2323

2424

0 commit comments

Comments
 (0)