@atlassian/atlassian-connect-js 5.3.203 → 5.3.205

package/.bitbucket/CODEOWNERS.md

@@ -0,0 +1,3 @@
+# The team is defined in https://ssam.us-east-1.prod.apd-paas.net/containers/ecosystem-onecloud-team/
+
+- @workspace-group/ecosystem-onecloud-team-dl-onecloud-team:all

package/CONTRIBUTING.md

@@ -0,0 +1,23 @@
+Contributing
+------------
+Contributions are welcome! However, the versions and branches of this project are in a state of flux. Before starting work,
+please contact the Atlassian Connect team to ensure you understand the process you'll need to follow.
+
+1. Create an issue in the [Atlassian Connect JavaScript API project](https://ecosystem.atlassian.net/browse/ACJS).
+2. Create your feature branch off `master`.
+    * Include your issue key and a short description.
+3. Push your changes.
+4. Create a pull request against this repository.
+5. If your changes will affect the functionality of the Connect plugin, create a feature branch in the product and make sure the build is green against your ACJS branch by updating the version consumed by the product.
+
+
+Releasing a new version
+------------------------
+This is now done via BitBucket Pipelines on the master branch.
+
+The `onecloud-build-bot` account executes this step as via the OAuth method described by [these Bitbucket instructions](
+https://support.atlassian.com/bitbucket-cloud/docs/push-back-to-your-repository/)
+
+
+If you're an Atlassian developer and you wish to release a new version of Atlassian Connect JS for Atlassian products to use,
+follow [this HOWTO](https://hello.atlassian.net/wiki/spaces/ECO/pages/1473343850/HOW-TO+Release+ACJS+for+products).

package/DEVELOPING.md

@@ -0,0 +1,88 @@
+Requirements
+------------
+
+- Node LTS (refer to `.nvmrc`)
+- NPM
+
+Installation
+------------
+
+NPM install takes care of everything for you.
+
+    npm install
+
+Building
+--------
+
+To build the distribution:
+
+    npm run build
+
+Running tests
+-------------
+
+We use [Karma](https://karma-runner.github.io/latest/index.html) for running our [Jasmine](https://jasmine.github.io/) tests.
+
+To run tests in watch mode:
+
+    npm run karma
+
+Running tests with saucelabs
+----------------------------
+
+Tests are automatically run in Sauce Labs from Bitbucket Pipelines. They run using all supported browsers. You can run these yourself as follows:
+
+Set your Sauce Labs credentials using the SAUCE_USERNAME and SAUCE_ACCESS_KEY environment variables.
+
+Then run the tests using:
+
+    SAUCE_LABS=true npm test
+
+Alternatively you can enter Sauce Labs credentials at run time with:
+
+    SAUCE_LABS=true SAUCE_USERNAME=XXXXX SAUCE_ACCESS_KEY=XXXXX npm test
+
+Linting && Coding Style Checks
+------------------------------
+
+ACJS follows the Atlassian Front-End Code Quality guidelines.
+
+    npm run lint
+
+Point IntelliJ / Sublime / your editor of choice at the .eslintrc for linting as you edit.
+
+Code Coverage
+-------------
+
+We use [Istanbul](https://istanbul.js.org/) for code coverage statistics.
+
+To run tests and generate coverage results:
+
+    COVERAGE=true npm run karma-ci
+
+Then point your browser at:
+
+    file:///<path to atlassian-connect-js>/coverage/index.html
+
+Commands
+--------
+
+To see a wider range of gulp commands run:
+
+    gulp --tasks
+
+Dev loop
+--------
+
+To automatically re-create the dist directory on code change, run:
+
+    gulp watch
+
+To have your changes automatically loaded onto a locally running JIRA or Confluence instance, first make sure that you
+include `-Dconnect-js-v5=true` in your command to start the product. Then you can deploy the contents of your dist directory:
+
+    gulp deploy
+
+By default, this will deploy to the v5 resources directory inside your local `atlassian-connect` project, i.e.
+`/<path/to/my/projects>/atlassian-connect/jsapi-v5/src/main/resources/v5`. Changes will be automatically picked up by the
+running product.

package/dist/connect-host.js

@@ -11287,10 +11287,30 @@
       return $dialog;
     };
     _proto.renderErrorState = function renderErrorState(extension) {
-      var $dialog = this.getByExtension({
-        addon_key: extension.addon_key,
-        key: extension.key
-      })[0].$el;
+      var $dialog;
+      if (HostApi$1.getBooleanFeatureFlag('acjs-iframe-allowlist-dialog-flexibility')) {
+        var ext = this.getByExtension({
+          addon_key: extension.addon_key,
+          key: extension.key
+        });
+        if (ext.length === 0) {
+          var dialogs = $('.' + DIALOG_CLASS).toArray();
+          if (dialogs.length === 0) {
+            return;
+          }
+          $dialog = AJS.dialog2(dialogs[0]).$el;
+        } else {
+          $dialog = ext[0].$el;
+        }
+        if (!$dialog) {
+          return;
+        }
+      } else {
+        $dialog = this.getByExtension({
+          addon_key: extension.addon_key,
+          key: extension.key
+        })[0].$el;
+      }
 
       // Fullscreen dialogs already render a close button in the header
       if ($dialog.hasClass('aui-dialog2-fullscreen')) {
@@ -13861,7 +13881,7 @@
    * Add version
    */
   if (!window._AP.version) {
-    window._AP.version = '5.3.203';
+    window._AP.version = '5.3.205';
   }
   simpleXDM.defineModule('messages', messages);
   simpleXDM.defineModule('flag', flag);

package/dist/iframe-fedramp.js

@@ -1373,7 +1373,7 @@ var AP = (function () {
       _this._eventHandlers = {};
       _this._pendingCallbacks = {};
       _this._keyListeners = [];
-      _this._version = '5.3.203';
+      _this._version = '5.3.205';
       _this._apiTampered = undefined;
       _this._isSubIframe = _this._topHost !== window.parent;
       _this._onConfirmedFns = [];

package/dist/iframe.js

@@ -1373,7 +1373,7 @@ var AP = (function () {
       _this._eventHandlers = {};
       _this._pendingCallbacks = {};
       _this._keyListeners = [];
-      _this._version = '5.3.203';
+      _this._version = '5.3.205';
       _this._apiTampered = undefined;
       _this._isSubIframe = _this._topHost !== window.parent;
       _this._onConfirmedFns = [];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlassian/atlassian-connect-js",
-  "version": "5.3.203",
+  "version": "5.3.205",
   "license": "Apache-2.0",
   "description": "Atlassian Connect JavaScript bridge",
   "main": "dist/connect-host.js",

package/src/host/components/dialog.js

@@ -278,10 +278,35 @@ class Dialog {
   }
 
   renderErrorState(extension) {
-    const $dialog = this.getByExtension({
-      addon_key: extension.addon_key,
-      key: extension.key,
-    })[0].$el;
+    let $dialog;
+
+    if (
+      HostApi.getBooleanFeatureFlag('acjs-iframe-allowlist-dialog-flexibility')
+    ) {
+      const ext = this.getByExtension({
+        addon_key: extension.addon_key,
+        key: extension.key,
+      });
+      if (ext.length === 0) {
+        const dialogs = $('.' + DIALOG_CLASS).toArray();
+        if (dialogs.length === 0) {
+          return;
+        }
+
+        $dialog = AJS.dialog2(dialogs[0]).$el;
+      } else {
+        $dialog = ext[0].$el;
+      }
+
+      if (!$dialog) {
+        return;
+      }
+    } else {
+      $dialog = this.getByExtension({
+        addon_key: extension.addon_key,
+        key: extension.key,
+      })[0].$el;
+    }
 
     // Fullscreen dialogs already render a close button in the header
     if ($dialog.hasClass('aui-dialog2-fullscreen')) {