lightning-base-components 1.17.2-alpha → 1.17.5-alpha

package/src/lightning/inputAddress/inputAddress.js

@@ -2,6 +2,7 @@
 
 import labelRequired from '@salesforce/label/LightningControl.required';
 import labelHelpTextAlternativeText from '@salesforce/label/LightningInput.helptextAlternativeText';
+import labelMailingAddressFieldsUpdateText from '@salesforce/label/LightningInput.mailingAddressFieldsUpdateText';
 import locale from '@salesforce/i18n/locale';
 import { LightningElement, api, track } from 'lwc';
 import { classSet, formatLabel } from 'lightning/utils';
@@ -33,6 +34,7 @@ const FIELD_TYPE = {
 const i18n = {
     required: labelRequired,
     helpTextAlternativeText: labelHelpTextAlternativeText,
+    mailingAddressFieldsUpdateText: labelMailingAddressFieldsUpdateText,
 };
 /**
  * Represents an address compound field.
@@ -573,6 +575,10 @@ export default class LightningInputAddress extends LightningElement {
         this.country = country || '';
 
         this.postalCode = address.postalCode || '';
+        this._messageOnAddressUpdate = formatLabel(
+            this.i18n.mailingAddressFieldsUpdateText,
+            this.country
+        );
 
         this.dispatchAddressChangeEvent();
     }

package/src/lightning/modal/__docs__/modal.md

@@ -1,17 +1,17 @@
-A `lightningModal` component overlays a message modal on top of the current app window. A modal interrupts a user’s workflow and draws attention to the message. 
+A `lightningModal` component overlays a message modal on top of the current app window. A modal interrupts a user’s workflow and draws attention to the message.
 
 `LightningModal` implements the SLDS [modals](https://www.lightningdesignsystem.com/components/modals/) blueprint.
 
 Create a modal component in response to a user action, such as clicking a button or link. The modal blocks interaction with everything else on the page until the user acts upon or dismisses the modal.
 
-Unlike other components, this component doesn't use a `lightning-modal` tag or extend `LightningElement`. There is no `lightning-modal` component. Instead, you create a modal by extending `LightningModal` and using these helper `lightning-modal-*` components to provide a header, footer and the body of the modal. 
+Unlike other components, this component doesn't use a `lightning-modal` tag or extend `LightningElement`. There is no `lightning-modal` component. Instead, you create a modal by extending `LightningModal` and using these helper `lightning-modal-*` components to provide a header, footer and the body of the modal.
 - `lightning-modal-body`
 - `lightning-modal-header`
 - `lightning-modal-footer`
 
 To create a modal component, import `LightningModal` from `lightning/modal`. The component has access to the normal LWC resources as well as the special container, helper components, methods, and events of the `lightning/modal` module.
 
-In this example, the `content` property passes data to the modal from the component that invokes it. 
+In this example, the `content` property passes data to the modal from the component that invokes it.
 
 ```js
 /* c/myModal.js */
@@ -28,7 +28,7 @@ export default class MyModal extends LightningModal {
 }
 ```
 
-The modal’s HTML template uses helper `lightning-modal-*` components to provide a header, footer, and the body of the modal. In this example, the content for the modal body comes from the `content` property we defined in the modal's JavaScript file. 
+The modal’s HTML template uses helper `lightning-modal-*` components to provide a header, footer, and the body of the modal. In this example, the content for the modal body comes from the `content` property we defined in the modal's JavaScript file.
 
 ```html
 <!-- c/myModal.html -->
@@ -42,19 +42,19 @@ The modal’s HTML template uses helper `lightning-modal-*` components to provid
 </template>
 ```
 
-The `lightning-modal-body` component is required for the modal template. 
+The `lightning-modal-body` component is required for the modal template.
 
-The `lightning-modal-header` and `lightning-modal-footer` components are optional, but recommended. The `lightning-modal-*` components render in the order they appear in the template. Place the `lightning-modal-body` component after `lightning-modal-header` and before the `lightning-modal-footer` component. 
+The `lightning-modal-header` and `lightning-modal-footer` components are optional, but recommended. The `lightning-modal-*` components render in the order they appear in the template. Place the `lightning-modal-body` component after `lightning-modal-header` and before the `lightning-modal-footer` component.
 
 #### Open a Modal Instance
 
 `LightningModal` provides an `.open()` method which opens a modal and returns a promise that asynchronously resolves with the result of the user’s interaction with the modal.
 
-Each invocation of a modal component’s `.open()` method creates a unique instance of the modal. You can think of a modal as a self-contained application that starts from scratch when it opens. It displays the content you pass in through the `.open()` method or that you set within the modal's HTML template. 
+Each invocation of a modal component’s `.open()` method creates a unique instance of the modal. You can think of a modal as a self-contained application that starts from scratch when it opens. It displays the content you pass in through the `.open()` method or that you set within the modal's HTML template.
 
-When you close a modal, the modal instance is destroyed, not hidden. On close, the modal must save the user’s input data or pass it to the invoking component as the promise result. Otherwise, the data is lost when the modal instance is closed. 
+When you close a modal, the modal instance is destroyed, not hidden. On close, the modal must save the user’s input data or pass it to the invoking component as the promise result. Otherwise, the data is lost when the modal instance is closed.
 
-The `.open()` method lets you assign values to the modal's properties. `LightningModal` provides these properties. 
+The `.open()` method lets you assign values to the modal's properties. `LightningModal` provides these properties.
 
 * `label` - Required. Sets the modal's title and assistive device label. If the modal has a header, set `label` in the `lightning-modal-header` component. If the modal doesn't have a header, set the `label` property when opening the modal.
 
@@ -95,14 +95,14 @@ The HTML template for this app contains a button that opens the modal and displa
 <template>
     <lightning-button
         onclick={handleClick}
-        aria-haspopup="modal"
+        aria-haspopup="dialog"
         label="Open My Modal">
-    </lightning-button> 
+    </lightning-button>
     <p>Result: {result}</p>
 </template>
 ```
 
-You can also use `.open()` to pass data from your invoking component into the modal with custom properties decorated with `@api`. These properties can be any type, such as a string or an object that’s an array of key/value pairs to be assigned to the new modal instance. 
+You can also use `.open()` to pass data from your invoking component into the modal with custom properties decorated with `@api`. These properties can be any type, such as a string or an object that’s an array of key/value pairs to be assigned to the new modal instance.
 
 For example, this app component sets an `options` property to a set of key/value pairs in `MyModal.open()`. The promise is handled using an arrow function that logs the result to the console.
 
@@ -155,14 +155,14 @@ export default class MyModal extends LightningModal {
             >
                 {option.label}
             </lightning-button>
-        </template>   
+        </template>
     </lightning-modal-body>
 </template>
 ```
 
 #### Close a Modal Instance
 
-Use `this.close(result)` to close the modal, where `result` is anything you want to return from the modal. The `.close()` operation is asynchronous to display a brief fade out animation before the modal is destroyed. The `result` data can’t be modified after the close operation begins. 
+Use `this.close(result)` to close the modal, where `result` is anything you want to return from the modal. The `.close()` operation is asynchronous to display a brief fade out animation before the modal is destroyed. The `result` data can’t be modified after the close operation begins.
 
 You can also close the modal with the default close button, the X at the top right corner. Closing a modal like this is the same as calling `this.close()` with an `undefined` result, so any data input is lost.
 
@@ -320,7 +320,7 @@ export default class MyModalForm extends LightningModal {
 
 A modal can only fire events captured by the component that opened it, not the modal itself. Normal techniques can't catch events that fire from the modal, because the events bubble up to a top root element outside of the component that opened the modal.
 
-To capture modal events, attach them in the `.open()` method invoked by the component that opens the modal. 
+To capture modal events, attach them in the `.open()` method invoked by the component that opens the modal.
 
 For example, here's a custom `select` event dispatched from `MyModal`.
 
@@ -374,18 +374,185 @@ handleOpenModal() {
 
 See [Create and Dispatch Events](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/events_create_dispatch) in the LWC Dev Guide for more information about events.
 
+#### Modal Events with Aura
+
+For `LightningModal`, only the top level LWC component or application can communicate to the parent Aura component or application layer with eventing. This topmost component is usually the one that opens the `LightningModal`. `LightningModal`'s child components can't event to a parent Aura component or application layer.
+
+All required eventing that should occur during the `LightningModal`'s life cycle must be passed in when you call `Modal.open()`. See `onselect` within `.open()` in the **Modal Events** section. 
+
+If you want the Aura layer to respond to events within child components embedded in the `LightningModal`, use event bubbling to move any data that you want to make available to the Aura layer into the topmost LWC component that opened the modal. Then, send the event from the LWC component.
+
+With this in mind, there are two suggested methods for extracting data from the `LightningModal` to the Aura layer.
+
+1. To only communicate data out of modal after it's closed, first, close the modal, and pass the data out with `this.close({ data })`, and handle the data received in `.then((result) { ... })` where the Modal is initially opened.
+2. To continuously communicate data out of the `LightningModal` while the modal remains open, use events created and passed in when opening the modal from `Modal.open({ size, title, onmyevent })`.
+
+These extracting methods fit into the larger LWC Modal-to-Aura event workflow.
+
+1. Pass any events that should occur within the modal through `LightningModal`'s `.open()` method
+2. Have the `LightningModal` JavaScript code fire any custom events
+3. In the topmost LWC component that opened the modal, create an event handler to process the events, including stopping propagation.
+4. Fire a separate event containing the LWC-processed event details and send it to the Aura parent component.
+5. Use an Aura-based event handler to handle and process the event.
+
+For more information, see [Send Events to an Enclosing Aura Component](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.events_sending_to_aura_components) and [Events Best Practices](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/events_best_practices).
+
+Let's see this workflow in action. In this example, we'll create a button (`lightning-button`) that launches a modal (`LightningModal`) containing a tree grid component (`lightning-tree-grid`) with a button in each record row that automatically navigates our user to that record's page (`lightning-navigation`). This use case requires data passing between our LWC components and a parent Aura component. 
+
+Because `lightning-navigation` requires you to pass in a `recordId` to construct a page reference, we need to pass the record's data out of `LightningModal`, and then use the methods provided by `lightning-navigation`. With modal's limitations for event bubbling to the Aura layer, we can't just wrap the button or treegrid with `lightning-navigation`. We need to pull that data up to the topmost LWC component, where the `LightningModal` `.open()` is called, for our Aura wrapper to handle the navigation.
+
+So, we `import` the `lightning-navigation` component into the topmost LWC component that sits within the Aura layer by passing the data through `LightningModal`'s close method, `this.close({ data })`. Then the parent LWC component invokes the methods provided by `lightning-navigation`, which handles the navigation away from the page after the modal exits. From a UX perspective, this also lets us close the modal first, since `lightning-navigation` takes the user away from the current page.
+
+Note that this sample code isn't fully functional. We're only showing the relevant code that makes the `lightning-navigation` use case work with `LightningModal`.
+
+Here's our Aura component, containing our topmost LWC component, `myLwcAppModalLauncher`.
+
+```html
+/* c/myApp.cmp */
+<aura:component>
+    <!-- <c:myLwcTreeGridWithNavigation/> component is a child component
+        inside of <c:myLwcAppModalLauncher/>
+    -->
+    <c:myLwcAppModalLauncher/>
+</aura:component>
+```
+
+The topmost component, `myLwcAppModalLauncher`, launches and handles events that occur within our modal (`MyModal`). `myLwcAppModalLauncher` is also where we import the `lightning-navigation` component and use the `rowId` handed up through modal's `this.close({ ..., rowId })` function.
+
+```html
+<!-- c/myLwcAppModalLauncher.html -->
+
+<template>
+    <lightning-button
+        onclick={handleModalOpen}
+        aria-haspopup="dialog"
+        label="Launch Navigation Modal">
+    </lightning-button>
+</template>
+```
+
+```js
+/* c/myLwcAppModalLauncher.js */
+
+import { LightningElement, wire } from 'lwc';
+import { NavigationMixin } from 'lightning/navigation';
+import MyModal from 'c/myModalWithTreeGridNavigation';
+
+export default class MyLwcAppModalLauncher extends NavigationMixin(LightningElement) {
+
+/// ... other modal code
+
+handleModalOpen() {
+    // open up the Modal
+    MyModal.open({
+        size: 'medium',
+        heading: 'Navigate to Record Page',
+        description: 'Navigate to a record page by clicking the row button',
+        options: [{ data }, { data }],
+    }).then((result) => {
+        // when the LightningModal closes, result is whatever
+        // data that was passed out using this.close({ data })
+        if (result === null) {
+            // do something else
+        } else {
+            // shouldNavigate is boolean, arbitrary
+            // rowId is what's needed for lightning-navigation
+            const { shouldNavigate, rowId } = result;
+            if (shouldNavigate) {
+                this.navigateToObjectHome(rowId);
+            }
+        }
+    });
+}
+
+navigateToObjectHome(rowId) {
+    // construct the page ref
+    const pageRef = {
+        type: 'standard__recordPage',
+        attributes: {
+            recordId: rowId,
+            actionName: 'view'
+        }
+    }
+    // then call the .Navigate method with the pageRef
+    this[NavigationMixin.Navigate](pageRef);
+}
+
+/* ... other modal code */
+```
+
+This `template` is our modal, containing a tree grid with the navigation buttons, named `c-my-lwc-tree-grid-with-navigation`. The `handleNavSelection` function in this component processes the `rowId` data for the modal component to pass to its parent.
+
+```html
+<!-- c/myModalWithTreeGridNavigation.html -->
+<template>
+    <lightning-modal-header label="My Modal Heading">
+        The modal tagline.
+    </lightning-modal-header>
+    <lightning-modal-body>
+        <h2>Choose a record to navigate to:</h2>
+        <!-- custom event listener when button clicked inside tree grid -->
+        <div onnavselection={handleNavSelection}>
+            <c-my-lwc-tree-grid-with-navigation></c-my-lwc-tree-grid-with-navigation>
+        </div>
+    </lightning-modal-body>
+    <!-- no <lightning-modal-footer> in this example -->
+</template>
+```
+
+```js
+/* c/myModalWithTreeGridNavigation.js */
+handleNavSelection(event) {
+    event.stopPropagation();
+    const { detail: { rowId } } = event;
+    if (rowId) {
+        // rowId value is important to lightning-navigation
+        // passing this data out through the LightningModal's
+        // .close() method, then handled in the .then((result) {})
+        // see code above: c/myLwcAppModalLauncher.js
+        this.close({ shouldNavigate: true, rowId });
+    }
+}
+```
+
+```js
+/* c/myLwcTreeGridWithNavigation.js */
+
+dispatchNavSelectionEvent(rowId) {
+    // add rowId to event.detail
+    // this custom event listener exists in
+    // LightningModal body code, see code above:
+    // c/myModalWithTreeGridNavigation.html
+    const eventToFire = new CustomEvent('navselection', {
+        detail: { rowId },
+        bubbles: true,
+        cancelable: false
+    });
+    // dispatch custom event
+    // see event listener added to lightning-modal-body
+    this.dispatchEvent(eventToFire);
+}
+
+handleRowButtonClick(event) {
+    // simplified handler to get row.Id
+    // from the tree grid row button that was clicked
+    const row = event.detail.row;
+    this.dispatchNavSelectionEvent(row.Id);
+}
+```
+
 #### Styling Variants
 
-The `lightning-modal-header` and `lightning-modal-footer` child components are optional, and you can choose to not include one or the other in your modal. 
+The `lightning-modal-header` and `lightning-modal-footer` child components are optional, and you can choose to not include one or the other in your modal.
 
 The headerless variant of `LightningModal` has these additional requirements.
 - Must set a descriptive modal title with the `label` property using `Modal.open({ label })` or you’ll get a console error.
--  The `label` property is required for all variants of `LightningModal`. Assistive devices read the `label` value, even though the headerless modal variant doesn't display the label. 
+-  The `label` property is required for all variants of `LightningModal`. Assistive devices read the `label` value, even though the headerless modal variant doesn't display the label.
 -  Because this variant doesn't use `lightning-modal-header`, you have to manually create an `<h1>` heading in `lightning-modal-body`. Provide accessible structure by starting with heading level `<h1>` and using levels up to `<h6>` appropriately. For more information, see [Semantic Structure, Headings on WebAim.org](https://webaim.org/techniques/semanticstructure/#headings).
 
 The `LightningModal` component also supports the SLDS [Directional variant](https://www.lightningdesignsystem.com/components/modals/#Directional) modal blueprint pattern.
 
-To achieve the directional button layout, place the buttons in a `div` with the `slds-modal__footer_directional` class. 
+To achieve the directional button layout, place the buttons in a `div` with the `slds-modal__footer_directional` class.
 
 ```html
 <!-- c/modalDirectional.html -->
@@ -403,7 +570,7 @@ To achieve the directional button layout, place the buttons in a `div` with the
 
 #### Styling Hooks
 
-The `lightning-modal-*` helper components support [style hooks](https://www.lightningdesignsystem.com/components/modals/#Styling-Hooks-Overview). The styling hooks for the template that invokes the helper components doesn't carry over to them, so you must style each helper component individually. 
+The `lightning-modal-*` helper components support [style hooks](https://www.lightningdesignsystem.com/components/modals/#Styling-Hooks-Overview). The styling hooks for the template that invokes the helper components doesn't carry over to them, so you must style each helper component individually.
 
 Customizing the styling on the white modal frame and background, close button, or gray backdrop isn't supported.
 
@@ -411,4 +578,4 @@ Customizing the styling on the white modal frame and background, close button, o
 
 The `lightning-modal-header` component renders the `label` value in an `<h1>` element. If your modal uses the header, begin any additional heading levels in the modal with `<h2>` for accessibility. Provide accessible structure by using heading levels up to `<h6>` appropriately. For more information, see [Semantic Structure, Headings on WebAim.org](https://webaim.org/techniques/semanticstructure/#headings).
 
-To include tagline text or link content for the header section, add it between the `<lightning-modal-header>` tags. 
+To include tagline text or link content for the header section, add it between the `<lightning-modal-header>` tags.

package/src/lightning/modal/__examples__disabled/allform/allform.html

@@ -3,7 +3,7 @@
         <button
             onclick={handleDemoModal}
             aria-haspopup="modal"
-        >Open the Modal</button> 
+        >Open Modal form, size=medium</button>
         <p>Result: <code>{demoResult}</code></p>
     </div>
 </template>

package/src/lightning/modal/__examples__disabled/allform/allform.js

@@ -7,7 +7,7 @@ export default class ModalAllForm extends LightningElement {
     handleDemoModal() {
         ModalDemoAllForm.open({
             // LightningModal
-            size: 'small',
+            size: 'medium',
             // this becomes 'label'
             heading: 'Edit Contact Information',
             description: 'Edit the contact information for Sales Opportunities',

package/src/lightning/modal/__examples__disabled/allformfull/allformfull.css

@@ -0,0 +1,7 @@
+.example {
+    margin: 0.5rem;
+    border-radius: 0.5rem;
+    background: #FFF;
+    box-shadow: 0 1px 0.25rem rgb(0 0 0 / 20%);
+    padding: 1rem;
+}

package/src/lightning/modal/__examples__disabled/allformfull/allformfull.html

@@ -0,0 +1,9 @@
+<template>
+    <div class="example">
+        <button
+            onclick={handleDemoModal}
+            aria-haspopup="modal"
+        >Open Modal form, size=full</button>
+        <p>Result: <code>{demoResult}</code></p>
+    </div>
+</template>

package/src/lightning/modal/__examples__disabled/allformfull/allformfull.js

@@ -0,0 +1,49 @@
+import { LightningElement } from 'lwc';
+import ModalDemoAllFormFull from 'modal/demoallformfull';
+
+export default class ModalAllForm extends LightningElement {
+    demoResult = 'unset';
+
+    handleDemoModal() {
+        ModalDemoAllFormFull.open({
+            // LightningModal
+            size: 'full',
+            // this becomes 'label'
+            heading: 'Edit Contact Information',
+            description: 'Edit the contact information for Sales Opportunities',
+            // ModalDemo
+            options: [
+                {
+                    id: 1,
+                    variant: 'neutral',
+                    label: 'Close',
+                    triggerCancel: true,
+                },
+                {
+                    id: 2,
+                    variant: 'neutral',
+                    label: 'Disable Close Button',
+                    toggleDisableClose: true,
+                },
+                {
+                    id: 3,
+                    variant: 'neutral',
+                    label: 'Open Next Modal',
+                    triggerSecondModal: true,
+                },
+                {
+                    id: 4,
+                    variant: 'brand',
+                    label: 'Save Data',
+                    triggerSubmit: true,
+                },
+            ],
+        }).then((result) => {
+            if (result === null) {
+                this.demoResult = 'dismiss';
+            } else {
+                this.demoResult = JSON.stringify(result);
+            }
+        });
+    }
+}

package/src/lightning/modal/__examples__disabled/demoallformfull/demoallformfull.css

@@ -0,0 +1,3 @@
+lightning-input .slds-checkbox_toggle .slds-checkbox_faux_container {
+    display: block !important;
+}

package/src/lightning/modal/__examples__disabled/demoallformfull/demoallformfull.html

@@ -0,0 +1,146 @@
+<template>
+    <lightning-modal-header label={heading}>
+        <p>Update your contact information by completing the form below.</p>
+    </lightning-modal-header>
+    <lightning-modal-body><div id="all-body">
+        <div class="slds-form slds-form_stacked" role="list">
+            <div class="slds-form__row">
+              <div class="slds-form__item" role="listitem">
+                <lightning-input onchange={handleTextInput} type="text" name="assignedTo" label="Assigned To" required></lightning-input>
+              </div>
+              <div class="slds-form__item" role="listitem">
+                <lightning-input onchange={handleTextInput} type="text" name="teamName" label="Team Name" required></lightning-input>
+              </div>
+            </div>
+            <div class="slds-form__row">
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input type="toggle" label="Security Assessment Required?" name="input3" checked disabled></lightning-input>
+                </div>
+                <div class="slds-form__item" role="listitem">
+                    <lightning-combobox
+                        name="progress"
+                        label="Status"
+                        value={statusValue}
+                        placeholder="Select Progress"
+                        options={statusOptions}
+                        onchange={handleChangeStatus}
+                    ></lightning-combobox>
+                </div>
+            </div>
+            <div class="slds-form__row">
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleTextInput} type="text" name="personalSettings" label="Personalization Settings"></lightning-input>
+                </div>
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleTextInput} type="number" name="slaSerialNum" label="SLA Serial Number"></lightning-input>
+                </div>
+            </div>
+            <div class="slds-form__row">
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleDateInput} type="date" name="slaExpireDate" label="SLA Expiration Date" ></lightning-input>
+                </div>
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleTimeInput} type="time" name="slaExpireTime" label="SLA Expiration Time" ></lightning-input>
+                </div>
+            </div>
+            <div class="slds-form__row">
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleTextInput} type="text" name="location" label="Location"></lightning-input>
+                </div>
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input onchange={handleTextInput} type="text" name="selectedLangs" label="Selected Languages"></lightning-input>
+                </div>
+            </div>
+            <div class="slds-form__row">
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input-address
+                        address-label="Billing Address"
+                        street-label="Street"
+                        city-label="City"
+                        country-label="Country"
+                        province-label="Province"
+                        postal-code-label="PostalCode"
+                        street={addressBilling.street}
+                        city={addressBilling.city}
+                        country={addressBilling.country}
+                        province={addressBilling.province}
+                        postal-code={addressBilling.postalCode}
+                        country-options={getCountryOptsBilling}
+                        province-options={getProvinceOptsBilling}
+                        onchange={handleChangeBilling}
+                        field-level-help="Enter your billing address.  Where your credit card statements are sent."
+                    ></lightning-input-address>
+                </div>
+                <div class="slds-form__item" role="listitem">
+                    <lightning-input-address
+                        address-label="Shipping Address"
+                        street-label="Street"
+                        city-label="City"
+                        country-label="Country"
+                        province-label="Province"
+                        postal-code-label="PostalCode"
+                        street={addressShipping.street}
+                        city={addressShipping.city}
+                        country={addressShipping.country}
+                        province={addressShipping.province}
+                        postal-code={addressShipping.postalCode}
+                        field-level-help="Enter your shipping address. Where you receive packages."
+                        country-options={getCountryOptsShipping}
+                        province-options={getProvinceOptsShipping}
+                        onchange={handleChangeShipping}
+                    ></lightning-input-address>
+                </div>
+            </div>
+        </div>
+    </div></lightning-modal-body>
+    <lightning-modal-footer><div id="all-footer">
+        <template for:each={options} for:item="option">
+            <template if:true={option.triggerCancel}>
+                <lightning-button
+                    key={option.id}
+                    label={option.label}
+                    class="slds-button"
+                    data-focus={option.focusName}
+                    variant={option.variant}
+                    onclick={handleButtonCancel}
+                    data-id={option.id}
+                    disabled={disableClose}
+                ></lightning-button>
+            </template>
+            <template if:true={option.triggerSecondModal}>
+                <lightning-button
+                    key={option.id}
+                    label={option.label}
+                    class="slds-button"
+                    data-focus={option.focusName}
+                    variant={option.variant}
+                    onclick={handleButtonOpenSecondModal}
+                    data-id={option.id}
+                ></lightning-button>    
+            </template>
+            <template if:true={option.toggleDisableClose}>
+                <lightning-button
+                    key={option.id}
+                    label={computedDisableCloseLabel}
+                    class="slds-button"
+                    data-focus={option.focusName}
+                    variant={option.variant}
+                    onclick={handleButtonToggleDisableButton}
+                    data-id={option.id}
+                ></lightning-button>
+            </template>
+            <template if:true={option.triggerSubmit}>
+                <lightning-button
+                    key={option.id}
+                    label={option.label}
+                    class="slds-button"
+                    data-focus={option.focusName}
+                    variant={option.variant}
+                    onclick={handleButtonSubmit}
+                    data-id={option.id}
+                    disabled={disableClose}
+                ></lightning-button>
+            </template>
+        </template>
+    </div></lightning-modal-footer>
+</template>