TopLogic - the automated application engine
  • Releases
  • Dokumentation
  • Github
  • Discord
  1. Home
  2. Releases
  3. TL_8.0.0-alpha9
  4. #29596

8.0.0-alpha9
TopLogic Release

2026-10-01

enhancement

major
#27490
Limit/Trim/Clean Up History
#29004
Allow to use a virus scanner for uploads
#29006
Uniqueness-Constraint
#29421
Add a React calendar view control and declarative <calendar> UIElement.
#29429
Complete the view designer so a view can be built with it end to end
#29462
React: Generic form element for editing configurations
#29487
React view: <form> exposes neither column count nor label position, and there is no <group> element
#29499
Note about maintenance mode in the React interface
#29507
Notification of an impending session timeout in the React interface
#29523
<sidebar> exposes two of the five sidebar item kinds ReactSidebarControl renders, and none of the badge
#29525
Offer the app-bar user menu in the core view layer
#29528
Let the UI theme follow the system's dark/light preference
#29529
Specify a deputy as an explicit security measure in the TL Views settings dialog (with password confirmation, including for password changes)
#29530
URL routing in TL Views: model objects in route parameters, drill-down path in the URL, query bindings
#29531
Filter bar for tables: presets, free-text search across visible columns, and user-defined saved filters
#29532
Object navigation in TL Views: display targets, a reveal protocol for containers, and a show-object action
#29540
Usability feedback on the user menu and the personal settings dialog
#29542
TL Views: channel-bound value inputs for every primitive and reference type, with a submit hook
#29543
TL Views: conditional branches in a generic-command action chain
#29544
TL Views table: row activation by double-click or Enter, and a grouping UI over the existing table model
#29545
TL Views table: drag and drop of rows between tables and onto rows
#29546
TL Views: colors for enumeration literals and classifier objects rendered as pills, and a progress control
#29547
Stop checking in generated React bundles
#29548
React view UI: URL, e-mail and phone attributes are edited as typed inputs and displayed as links
#29551
TL Views: only registered entry points may be loaded top-level via URL
#29557
React view commands: the ExecutableState reason of a disabled command never reaches the client, and there is no disabled-if rule beside visible-if
#29567
TL Views: Multiple Selection for Tables and Trees (selection-mode="multi")
#29575
TL Views: UI Inspector – View the state of a React UI element (e.g., table rows hidden due to access permissions) and record it as a script assertion
#29596
TL Views: Design Options for App-Specific Interfaces (CSS classes, text variations, layout options, input display variations, theme tokens)
#29597
TL Views: object-list as a generic repeater (elements without containers, grid layout, index for staggered animation)
#29598
TL Views: image with URL/resource source, aspect ratio, fill mode, and overlaid content; avatar with photo
#29599
TL Views: Wizard/Stepper Element for Multi-Step Dialog Flows (static and dynamic steps, progress, transitions, auto-advance)
#29600
TL Views: Display of long-running server jobs (phases, progress, undetermined progress, elapsed time)
#29601
TL Views: Display of HTML content and HTML documents (agent responses, property listings) with preview and print/PDF options
#29603
Physically Deleting Deleted Objects from Versioned Tables (Purge): The final set is determined based on required references and content; optional references are cleared
#29605
TL Views table filter bar: an initially active preset, and the active preset and search term as channels for query bindings
#29607
TL Views: a display target reveals a tab inside a pushed frame (a <show> is located within the view shown before it)
#29608
TL Views: value-input with a placeholder, accessible name when the label is hidden, conditional display of elements using visible-if
#29615
TL Views: a <form> spanning a page does not take part in the fill contract, so a split panel or filling panel inside it is sized by its content
#29617
Design System: Tokens and base classes as own package (wave 0)
#29625
TL Views: a page layout of weighted columns (main 2/3, side 1/3) that reflows to one column on a narrow viewport; the split-panel keeps its sashes and clips the side pane at 400 px
#29629
TL Views: `<show-view>` / `<show-views>` actions reveal a mounted view by name and write its channels from a command chain without a model object
#29630
TL Views: a chunked, transactional job body for <start-job> - scripted init / elements / steps / finish, one transaction per chunk, per-item retry and skip, phases and progress derived from the steps
#29637
Model-Based Authorization Definition: Access Parent Object (delegation of access decisions to containers or references, default for composition parts, decision cache per interaction), Role Parent Object instead of Security Parent, completeness check, and wizard
#29640
TL Views: Groups in a grouped table are sorted according to the comparator of the grouping column, not in random order
#29641
TL Views: The React TL Script Editor displays help text for functions and model elements (contextual help for autocomplete, hover tooltips) and no longer jumps to the beginning of the text when you start typing
#29643
TL Views: Adapting the React interface to a client's corporate design using a custom React component library (guidelines and missing extension points)
#29671
TL Views: Restrict drag-and-drop in tables based on rules, with feedback for each destination while dragging
#29681
The TL-Script modifiedRevision() function takes into account changes to references and translations; attribute storages no longer "affect" the owner object
#29690
Option to disable the browser from launching at startup
#29706
Speed up slow unit tests in tl-core and tl-element
minor
#28324
Create documentation for layout overlays
#29500
No way to show a master-detail as an overlay: the detail always costs the list half its width
#29506
A dashboard tile cannot be the entry point it looks like: neither <tile> nor <card> carries an action
#29550
React controls do not consume the theme's radius and surface tokens consistently; a flat theme needs per-component CSS overrides
#29553
React view <table>: <column> has no width, every column defaults to 150 px, so a table with more than six columns overflows a 940 px pane
#29611
TL Views: `<notify>` action shows a translated notice in a generic-command chain (snackbar or OK dialog, optionally stopping the chain); `<throw-error>` removed
#29624
SSO login without a registered user account: configurable information page (ApplicationPages.unknownAccountPage) instead of the login screen, with default pages for the classic and React interfaces
#29670
TL Script: The `trim`, `trimStart`, and `trimEnd` functions remove whitespace at the beginning and end of a string
#29675
TL Views: Creating and deleting are governed by the model's access permissions, rather than being rejected with a "Copying not allowed" message after the form is filled out
#29683
TL-Script: htmlText(html) cannot carry images, so an HTML text with <img> referencing files cannot become a structured text

defect

critical
#29665
TL Views: a click into a rich-text field with a hidden label focuses the editor's Bold button, so the typed text is lost
#29682
TL Views: ConcurrentModificationException in ReactToolbarControl.replaceGroups on a page reload shows the "Internal error" page
major
#25723
Missing check against attribute name clashes during inheritance
#29438
React view layer displays date attributes in a hard-wired format instead of the annotated one
#29474
Neither React drag handle shields the page (or locks the cursor) while dragging
#29502
<tree> does not follow model changes: a delete never arrives, a create collapses the whole tree
#29504
Forced logout does not reach the React interface
#29509
The cookie check rejects a subsequent request to its own URL and logs the session out in the process
#29512
Declare attributes in tl.model that are de facto mandatory as mandatory
#29533
TL Views: executability rules and derived channels must follow changes of the object on a channel, not only of the channel value
#29534
TL Views tile-stack: frames get no definite height, and a frame that is uncovered again is rebuilt from scratch
#29535
TL Views table: a selection channel value that is not among the rows must not be cleared by the table
#29541
Single-valued drop-down select shows two clear buttons
#29554
React view <table>: Columns for any row objects—calculated columns, embedded columns of referenced objects, dynamic columns; transient rows
#29556
react-api/tooltip runs without a TLSubSessionContext: a cell tooltip over a derived attribute using label() answers HTTP 500 (NullPointerException in Label.eval)
#29560
React view <upload-command>: Upload errors (exception in the action chain, size limit exceeded) are not displayed to the user; upload size limit is configurable
#29562
security.xml grants for a SecurityScopeService scope are lost on the start that introduces the scope: AccessConfigurationSetupService imports before the scope exists and stores the file hash anyway
#29564
SecurityConfigurationService: an application cannot add a role to a framework type's grant — a <class> grant is keyed by operation and replaces the earlier entry, silently revoking the framework's roles
#29568
TL Views: A route viewed without logging in is lost when you log in
#29573
TestReactStylesheetTokens fails on master: the pill and progress rules of tlReactControls.css do not keep the theme-token contract
#29574
TL Views: Vetoing a nested channel write access cancels the notification from the outer channel (the table and detail pane remain on the old object after "Discard")
#29576
The React-Controls-Bundle contains a second React instance (createPortal import in TLDropdownSelect)
#29586
tl-layout-react test compilation fails on master: TestSelectValueObservation and TestResourceCellObservation use the DefaultReactContext constructor that #29552 removed
#29590
React view: Multi-value strings are concatenated without separators in table cells and display fields
#29602
TL Views: a URL adopted into an existing session keeps the slot content of the sidebar item that was active before
#29604
ElementSecurityUpdateManager: quadratic collection diff on commit (AbstractSet.removeAll over a List) makes appending to a large reference take seconds
#29609
TL Views: a `<progress>` (ChannelObjectObserver) evaluates its expression on a deleted object and logs an ERROR when an observed object is deleted
#29610
TL Views: a table on an inactive tab shows stale cell values after the displayed objects changed, until its rows are refreshed
#29613
TL Views: a `<dashboard>` tile gets no definite height, so a table in a tile grows with its rows instead of scrolling
#29618
TL Views: a URL switches the sidebar away from an item with unsaved changes without asking
#29619
TL Views: a warning-level configuration constraint is dropped, so the model editor shows nothing
#29620
TL Views: a tree node is never a link to where its object is displayed, although the display targets declare one
#29622
TL Views: a `<flow-diagram selection="ch">` writes its channel but does not follow it, so a node selected elsewhere is not marked in the diagram
#29623
Build: the translate goal re-translates committed German messages after a pull or branch switch when the doclet did not run in the same build
#29626
TL Views: a panel toolbar has no overflow mode; at 400 px width the ticket page's six commands run 908 px wide, three of them unreachable, and the panel title is pushed out
#29627
TL Views table: an I18NString cell wraps its text and is clipped mid-glyph by the 36 px row instead of ending in an ellipsis; header labels are cut without an ellipsis
#29631
TL Views: Escape closes a <window> dialog while a <start-job> it started is still running; the job runs on with nothing left to show or cancel it
#29634
TL Views: the configuration editor builds a text field for a property whose format is parse-only, so selecting a derived attribute in the model editor fails with "There is no normative way to serialize a locator configuration"
#29635
TL Views: a <tree> renders every node as a link, so a click on the label navigates away instead of just selecting the node
#29639
TL-Script objectResolve(id, typeOrTable): resolution via a type including its subtypes or via a table name, objectTable delivers the table of an object, and an object the current user may not read is not resolved
#29644
Incremental security is incomplete when using scripted steps
#29645
TL-Script: The @SideEffectFree annotation on functions from TLScriptFunctions is ignored because the annotation lacks runtime retention.
#29648
TL Views: The scripts and stylesheets delivered via ClientResources do not include a version number in the URL; after an update, the browser uses outdated client files
#29649
TL Views: a job's final state is overwritten by a stale "running" snapshot, so <job-status> shows a completed job as running
#29666
TL Views: leaving a frame by breadcrumb, Back, navigate-pop, show-object or logout discards a form's unsaved changes without asking
#29667
TL Views: a form in edit mode keeps showing stale values after a command committed a change to the same object
#29672
TL Views: initial-edit-mode, an object switch and the edit-mode channel enter edit mode without asking <edit-executability>
#29674
TL Views: after a page load, app-bar command labels appear in the browser's language instead of the user's ("Record" in a German session)
#29677
TL Views: a card in a content-sized column stack shrinks below its content; a table beside it takes more height than it reports
#29678
BoundHelper: Remove the "use-default-security-parent" setting – without a configured security parent rule, an object has no security parent
#29680
Classic UI: the anonymous session is offered the developer options and can run "Ressourcen neu laden"
#29698
CollectionUtil.removeDuplicates() loses the order of the elements
#29705
Workspace/PathInfo: A module's `web-fragment.war` cannot be found if the JAR and fragment are resolved from different local Maven repositories (`maven.repo.local.tail`)
minor
#27889
Switch to SNAPSHOT version does not work
#28474
The background colors of the buttons are inconsistent
#29496
React table: a column resize is rejected with "Integer value expected" and the new width is lost when the client sends a fractional width
#29497
React UI tooltips: clipped table cells and column headers, compact toolbar buttons and attribute descriptions get tooltips; native title attributes replaced by bridge tooltips
#29503
TLResourceCell ships no CSS: icon and label touch wherever a resource cell shows both
#29505
Panel header changes height when its toolbar has no commands, so master-detail headers do not line up
#29508
Additional QueryExecutors do not require security
#29552
TLPhotoViewer fetches its image after the control was disposed when a <switch> replaces it (404 on react-api/data, "Command target NOT FOUND" WARN)
#29555
TL-Script label(<constant>) is folded at compile time: the result is fixed to the compiling thread's locale instead of the reading user's
#29558
XMLInstanceImporter silently imports an internationalized attribute given as value="…" as empty, even when the attribute is mandatory
#29561
TL Views: display of a referenced object does not follow a change of its label (table cell, form field)
#29563
Default group: The persistent group flag "defaultGroup" is derived from the configuration rather than stored in the database; semantics of the default group are documented
#29591
ResKey.decode accepts only double-quoted translations in #(…) literals — #('Travel'@en) fails, even though TL-Script allows both types of quotes
#29606
TL Views: a `<color token>` naming a token the React theme does not emit renders the pill untinted, silently
#29628
TL Views: "Reset personal settings" clears the stored configuration, but the running session keeps its table state and writes it back; the declared column widths return only after a new login
#29636
TL Views: a click on a <tree> node clears the selection channel before setting it, so every dependent display and command flips to empty and back
#29663
TL Views: a <form> no longer insets itself; a <fields> grid inside a form got the page inset twice
#29664
TL Views: the form's Edit, Save, Cancel and Apply commands are labelled with a trailing period ("Bearbeiten.", "Speichern.")
#29668
TL Views: the rich-text editor's toolbar overflows a narrow field; table and undo/redo buttons are cut off
#29669
A request with a malformed query string ("?q=50%") is answered with an "Internal error" page (HTTP 500) instead of 400
#29673
TL Views: personalization commands ("Layout bearbeiten", "Diesen Filter speichern") are offered to the anonymous session
#29676
TL Views admin: deleting an account logs "Target object is deleted" from the still-open account form; delete asks for no confirmation
#29679
TL Views: a command refused by its executability rule is reported with the title "Interner Fehler"

task

minor
#29612
FAQ: Migration guide for upgrading an application from TL 7.11 to 8.0
#29702
Increase the minimum Maven version in the build to 3.8.9
enhancement

major

#29596

TL Views: Design Options for App-Specific Interfaces (CSS classes, text variations, layout options, input display variations, theme tokens)

ReactUI

Context

A gap analysis of the real estate application (estate-agent, hand-coded React front end with a dark “glass” design, serif headings, photo tile grids, a filter sidebar with chips, segment switches, and sliders) against the React interface (.view.xml level) has revealed: The structure (app shell, navigation, routing, tables, forms, dialogs, charts, theme system with dark mode) is in place, but an app-specific appearance cannot be implemented because the elements lack style anchors and have only a basic layout vocabulary.

The theme itself (colors, fonts, icon sets) remains app-specific and is configured within the application. The engine ticket only provides the options and tokens that are missing for this purpose. Principle: Options on existing elements instead of new elements.

Extension

The ticket will be implemented in phases on a branch (multiple pushes/CI runs).

Phase 1: `css-class` for all elements

UIElement.Config gains the `css-class` property, which each control writes to its root element. The existing property of the same name on `<text> ` is moved to the base configuration; `<chart cssClass> ` is updated accordingly. This allows an app stylesheet rule (registered via ClientResources) to style individual panels, cards, stacks, images, or buttons (“this particular card is a glass card”).

Phase 2: Text Variations, Sound, and Pill

<text> receives

  • variant (type role): display, headline, title, body (default), label, caption;
  • tone (color role): primary (default), secondary, helper, accent, success, warning, error, on-color;
  • appearance: text (default) or pill (existing TLPill representation; color from tone).

Each variant is rendered as a stable CSS class (tlText--display, tlText--tone-accent, …) and populated from theme tokens.

New theme tokens with neutral default values that the controls consume, so that an app theme can override them:

  • font-family-display (font for display/`headline`/`title`; default = font-family),
  • border-radius-03 (third radius level for large areas),
  • surface-blur (backdrop blur for areas; default 0),
  • shadow-glow (glow shadow for focus/highlighting; default = no shadow),
  • background-image (app shell background; default = none).

Transparent areas, grain, secondary accents, and similar elements remain in the app stylesheet.

Phase 3: Layout Options

  • <stack>: wrap, justify, and max-width (centered content column).
  • <grid>: max-width. (max-columns as the upper limit for auto-fit, e.g., 3 cards per row, provided by #29597 via the shared grid options of <grid> and <object-list layout="grid">.)

Hero sections with background images and overlays are implemented via app CSS on a CSS class stack; no engine element is required for this.

Phase 4: Display Variants for Input Fields

The field control providers receive a ` display` option, which is set via an `<input-control>` annotation on the attribute or on the `<field> ` element:

  • SelectControlProvider: dropdown (default), chips (multiple selection as a tag cloud with toggleable chips), segmented (single selection as segmented radio buttons with a sliding marker);
  • NumberInputControlProvider: input (default), slider (with min, max, step, and displayed value);
  • BooleanControlProvider: checkbox (default), switch.

<value-input> accepts the same options.

Phase 5: `<value-input>` as a search field

<value-input> now supports `icon`, `placeholder`, `clearable `, and `debounce ` (delay before the value is written to the channel), allowing a standalone search field with a magnifying glass to be configured without its own element (along with the existing `on-submit ` and `<query-bindings>`). (placeholder is already included in #29608.)

Phase 6: Transition anchors

Opening/closing dialogs and frame changes in the tile-stack will receive CSS-transition-enabled state classes, allowing app CSS to define fade-in/fade-out effects. `prefers-reduced-motion` will continue to be honored. The animations themselves remain the responsibility of app CSS.

Solution

Implemented in two pushes on the same branch: Phases 1, 2, 3, and 5, followed by Phases 4 and 6.

Phase 1

`UIElement.Config#getCssClass() ` (css-class) is the single configuration property for all elements. On the control side, there is exactly one state key, ` cssClass `, in the base class `ReactControl ` (`setCssClass`, included in `scriptingPresentationKeys()`; subclasses supplement their keys via presentationKeys(super.scriptingPresentationKeys(), …)); the previous individual keys of the same name from ReactTextControl, ReactHtmlControl, ReactImageControl, ReactStackControl, ReactOverlayControl, and ReactResourceCellControl are no longer used. Each of the 66 elements passes its configured class to the returned Control (there is no central creation point; child Controls are mounted on the client side without a wrapper element). An element that passes on another element’s control (such as `view` or `tile`) only sets the class if it has configured one itself. On the client side, the bridge function `rootClassName(state, …)` constructs the `className` of the root element for each of the 78 registered components. <text> sends its overflow modifier as its own state key `overflow` instead of in the class string; the `TextOverflow ` enum is associated with the control. The differently named `cssClass ` property of `<chart> ` is omitted; the inherited ` css-class` applies. FAQ: docs/faq/react-view-layer.md (section “Styling a single element”), docs/faq/new-ui-element.md.

Phase 2

variant, tone, and appearance are three ExternallyNamed enums(TextVariant, TextTone, TextAppearance in com.top_logic.layout.react.control.common) on TextElement.These are passed as separate state keys to TLText (default values are included) and become tlText--<variant>, tlText--tone-<tone>, and tlText--pill there. Each tone is a rule that populates the custom property --tlText-tone; they read the text color and pill color. appearance="text" retains the current behavior (a value with a model color is displayed as a pill); appearance="pill" always renders a pill whose color comes from tone, provided the value does not have a model color; text without content does not draw a pill. The recoloring of text in the primary app bar now only uses ` tlText--tone-primary`, so an explicitly set tone takes precedence there.

Typography: `display ` and `headline` receive their own tokens (`display-01-font-size/`-line-height`, ` heading-04-font-size/`-line-height`) and `font-family-display`; title = heading-03 (+ new heading-03-line-height), body = body-compact-01, label = heading-compact-02, caption = label-01 (+ new label-01-line-height). Sounds: primary/`secondary`/`helper`/`on-color`/`error` use the existing text-* tokens; new as ref tokens : text-accent → interactive, text-success → support-success, text-warning → support-warning.

Additional tokens in the default theme(inherited by Dark): font-family-display (refers to font-family), border-radius-03 (1rem, third radius level “large area”; docs/faq/react-theme-tokens.md describes three levels), surface-blur (length, 0`; consumed by the dialog backdrop), `shadow-glow` (text, none), background-image (text, none; consumed by ` body ` in `tlReactBase.css `).

Phase 3

<stack>: wrap (boolean), justify (enum ReactStackControl.StackJustify: start, center, end, space-between, space-around, space-evenly, rules .tlStack--justify-*) and max-width. `max-width` is derived from the common base class `ReactLayoutControl ` (state key `maxWidth`, class `tlBounded`: `width: 100%`, `margin-inline: auto`) and, for grids, from the common `GridOptions`; it therefore applies to `<grid> ` and `<object-list> ` (grid and list layouts). As with `<panel width>`, the type is a CSS length value as a string. The stack’s layout keys are declared as pure presentation in the headless projection. See the FAQ section “Layout: stack and grid.”

Phase 4

The display variants are options of the existing field control providers (com.top_logic.layout.view.form), set via the existing <input-control> mechanism: as a TLInputControl annotation on the attribute or type, as the input-control of a <field>, and—new—as the input-control of a <value-input> (ValueInputElement.Config; the type-based path of FieldControlService.createFieldControl takes a provider configuration as a priority parameter for this). Each variant is a pure display state key (display, declared in scriptingPresentationKeys() ), so that the headless projection reads the same options and the same value in every form.

  • Switch: BooleanPresentation (model annotation <boolean-display presentation="switch"/>) takes the value "switch"; the classic UI treats it as a checkbox (CheckboxInputTag, PrimitiveColumn, AttributeOperations). BooleanControlProvider.Config#display (@NullDefault) overrides the annotation for a field. ReactCheckboxControl sends display=switch; TLCheckbox renders <input type=checkbox role=switch class="tlReactCheckbox--switch"> with a track and button from theme tokens. A tristate value remains a checkbox (a switch has no third state).
  • Chips / Segments: SelectControlProvider.Config#display with Enum SelectDisplay (dropdown, chips, segmented; com.top_logic.layout.react.control.select). A server-side control, ReactDropdownSelectControl, maintains the option index and value history for all forms and selects the appropriate React module (TLDropdownSelect, TLOptionChips, TLSegmentedChoice); a form that displays all options receives the option list immediately and upon every value change (invalidateOptions()), while the dropdown continues to load only when opened. Client: selectOptions.tsx (shared option descriptor, pill, image, read-only value), TLOptionChips (toggle buttons with ` aria-pressed`; single selection toggles, multiple selection switches), TLSegmentedChoice (radiogroup/`radio` with arrow keys, sliding marker via ResizeObserver; for multiple selection, filled segments without a marker).
  • Sliders: ` NumberInputControlProvider.Config ` with `display ` (enum `NumberDisplay`: `input`, `slider`), `min`, `max`, `step`. Validation is enforced by configuration constraints, ensuring that a configuration form does not allow invalid configurations: min/`max` are required as soon as display="slider" (new general annotation @MandatoryIf(other=@Ref(DISPLAY), value="slider") in com.top_logic.basic.config.constraint.annotation, which compares the configuration notation of the other value), min < max (@ComparisonDependency), step > 0 (@Bound). Custom ReactSliderControl ( TLSlider module): the value is exchanged as a number (not as text in locale format) and converted to the field’s number type via ` NumberFormats.normalize `; the server renders the label next to the slider handle (valueLabel) in the field’s format. Client : `<input type=range> ` + `<output>`, debounced submission and submission on release.

Tests: TestBooleanControlProvider, TestSelectControlProvider, TestNumberInputControlProvider (including constraint cases), TestMandatoryIf, TestValueInputElement. FAQ: docs/faq/react-view-layer.md, section “Display variants of input fields.”

Phase 5

icon (encoded ThemeImage, e.g., css:fa-solid fa-magnifying-glass), clearable, and debounce are applied to each field control in ReactFieldControlProvider.createField, similar to placeholder (#29608) FieldSpec properties applied to each field control in ` ReactFieldControlProvider.createField `; sent to the client as state keys `icon`, `clearable`, and `debounceMs ` from `ReactFormFieldControl ` (pure presentation; placeholder remains in the projection) and implemented in TLTextInput: leading icon, clear button (appears only when content is present, immediately sets the empty value, returns focus to the field), configurable delay. The constant VALUE_DEBOUNCE_MS (300 ms) is defined once in the bridge; text, number, and password fields read debounceMs. A field that submits only when exited (URL field, number) ignores the delay. <value-input> declares icon, clearable, debounce (@Format(MillisFormat.class), e.g., debounce="300ms").

Phase 6

A Bridge hook `useKeyedTransition({keys, node, container, enterClass, exitClass}) ` (react-src/bridge/transition.ts, exported from tl-react-bridge) marks the change in what a control displays: a newly appearing key is assigned the `enter` class on its element; a disappearing key is replaced in the container by an inert copy of its last-displayed element (aria-hidden, inert, no IDs, pointer-events: none) with the `exit` class. Both end with an animation/`transition` on the element itself, upon the key’s reappearance, or after TRANSITION_FALLBACK_MS (1000 ms, once defined). The initial display—and, regardless of the app’s CSS, a viewer with `prefers-reduced-motion: reduce `—receives neither a class nor a copy.

Consumers and classes:

  • Wizard: tlWizard__step--entering / tlWizard__step--exiting, tlWizard--forward|backward; retains its default animation. The previous inline code copied the step after the DOM swap and thus captured the incoming step instead of the exited one (confirmed in the browser); the hook remembers the element of each key after every commit and copies the one that was actually exited.
  • Dialog: tlDialog__backdrop--entering on the backdrop of the open dialog, tlDialog__backdrop--exiting on the copy of the closed dialog (the TLDialogManager is the container and therefore remains rendered even without dialogs). The copy covers the page and allows all input to pass through.
  • Tile Stack: tlTileStack__frame--entering / tlTileStack__frame--exiting and tlTileStack--forward|backward (derived from the change in activeIndex ).

For dialogs and tile stacks, the engine provides only the structural rules for the copy (position: absolute; inset: 0; pointer-events: none or pointer-events: none), not any animation. FAQ: “Transitions” section in docs/faq/react-view-layer.md.

Demo

com.top_logic.demo.react: “Design” page (demo/styling-demo.view.xml) with all text variations and colors, pills made of clay and model paint, hero banner and glass card via CSS class from tl-demo-react.css, stack/grid options, search field, and the “Input Display Variations” section (form via a transient demo.react:demo with chips, segments, sliders, and toggles, plus `<value-input>`s with `input-control`). tl-demo-react.css animates the transition classes (dialog fades in/out, tile stack frames slide depending on direction). Additional demo theme “glass” (extends “default”), which sets ` surface-blur`, ` shadow-glow `, and ` font-family-display `.

Not included in this ticket: generic repeater (object-list), image extension, wizard/stepper, display of long-running jobs, and display of HTML documents/printing. There are separate tickets for these.

  • Get Started
  • Github
  • Discord
  • Das Unternehmen hinter TopLogic
  • Softwareentwicklung heute
  • Kontakt

© Copyright – Business Operation Systems GmbH

  • top-logic.com
  • Nutzungsbedingungen
  • Impressum
  • Rechtlicher Hinweis
  • Datenschutz
  • DE
  • Login