Skip to content

Merge dev into master: af-core 1.0.10 and authoring test fixes - #2010

Merged
rismehta merged 7 commits into
masterfrom
merge-dev-to-master-20261023
Oct 23, 2026
Merged

rismehta merged 7 commits into
masterfrom
merge-dev-to-master-20261023

Conversation

@rismehta

Copy link
Copy Markdown
Collaborator

Description

Merge the latest Adobe dev into a new branch created from Adobe master, preserving both branch histories with a merge commit.

Source revisions:

  • dev: f7de780dfa573592b38a7c2189f08abe7dae81d1
  • master: fc839c72ef1bdbbd9dcb6e1d099196d5a625de5f

This promotes the complete pending dev changes, not only the runtime dependency update:

The merge changes nine files and required no conflict resolution or additional source changes.

Related Issue

FORMS-28607

Merged source PRs: #2009 and #2006.

Motivation and Context

Promote the validated dev fixes to master. Runtime 1.0.10 restores temporary backward compatibility for legacy private access on the field model exposed in custom functions, with deprecation warnings. The existing custom-function fixture and runtime regression cover the customer-style _options.parent._setProperty('visible', false) access.

The additional authoring-test changes are already merged into dev and are included intentionally in this full branch promotion.

How Has This Been Tested?

On the promotion merge head, in an isolated worktree with its own dependencies:

  • npm --prefix ui.frontend test -- --runInBand — passed: 7 suites, 45 tests.
  • npm --prefix ui.frontend run build:prod — passed: standard and XFA production builds and clientlib generation.
  • git diff --check adobe/master HEAD — passed.
  • Changed-file JavaScript module syntax checks and XML parsing — passed: 5 JavaScript files and 1 XML file.

Both merged source PRs had successful CI when checked, including Java 11/21 builds and Cypress Chrome latest-addon jobs with and without feature toggles.

Maven suites and Cypress suites were not rerun locally on this promotion head. Promotion-PR CI is separate from the successful source-PR checks and must complete before merge.

Screenshots (if appropriate):

Not applicable: branch promotion with no additional UI changes.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes and the overall coverage did not decrease.
  • All unit tests pass on CircleCi.
  • I ran all tests locally and they pass.

rismehta and others added 7 commits October 2, 2026 12:29
Reuse the existing telephone field with the same default policy, wait for policy save and verify persisted custom patterns before editor navigation, and clean up prepared policy attempts. Keep shared insertion commands unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Preserve insertion of a new telephone field into the blank form. Await policy persistence, actual layer transitions and insertion events; query only the visible insertion dialog and re-query its search input after clearing. Preserve original assertions and wait for the edit dialog to close before cleanup.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retry opening the Insert dialog after lost actions, target only visible dialog controls, and wait for layer, insertion and replacement refreshes. Restore the original replace-group policy state using existing editor helpers and named actions.

Add a deterministic lost-Insert-click regression with delayed persistence responses. Validation: five Chrome repeats (25 passing), Electron Sites/Forms replacement tests (11 passing), and PR-branch Chrome replacement/telephone-input tests (11 passing), all with test retries disabled.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…endly

Replace duplicated telephone policy layer/insertion sequencing with existing helpers. Scope insertion to guideSelectors.insertComponentDialog.dialog and replacement to the Forms content hook; policy controls use cq-dialog and value hooks rather than Coral element tags.

Document shared helper reuse. Validate 10 authoring specs: 67 passing and 2 pre-existing skipped tests. One Button cancel-dialog assertion used its existing retry; a standalone rerun passed all 6 active Button tests on their first attempt. Insertion and layer synchronization checks passed across Forms, Sites, fields, layouts, nested wizard panels and Footer.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…2009)

Add runtime-only coverage for the legacy _options.parent._setProperty chain. Use the maintained IT page so repeated previews retain working custom-function registration.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Promote Adobe dev f7de780 onto master fc839c7.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@adobe-bot

Copy link
Copy Markdown

Accessibility Violations Found

Id Impact
aria-required-attr critical
empty-heading minor
label-title-only serious
target-size serious

1 similar comment
@adobe-bot

Copy link
Copy Markdown

Accessibility Violations Found

Id Impact
aria-required-attr critical
empty-heading minor
label-title-only serious
target-size serious

@codecov

codecov Bot commented Oct 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@rismehta
rismehta merged commit 38688fa into master Oct 23, 2026
10 checks passed
@rismehta
rismehta deleted the merge-dev-to-master-20261023 branch October 23, 2026 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants