Repository navigation
Conversation
…colour and image EXO-91474 (#674) **Symptom**: with a background set for applications in Branding, the rows of the Tasks list, and of a project's List view, stayed light grey instead of showing it, and a background image set for applications showed nowhere in the Tasks app. **Cause**: the rows were painted with `@tableBackgroundAccent` (`tasks.less`), a fixed grey that no Branding key drives. The `TasksManagement` portlet opts out of the frame's background colour (`no-layout-background-color`), and its two cards, the tab bar and the tab content (`TasksManagement.vue`), paint `application-background-color`, opaque by default, over the image that the portlet frame (`PORTLET-FRAGMENT`) still painted. **Fix**: - the rows are transparent and keep their border, so they show the application background; - both cards carry `application-background-image` beside `application-background-color`, and the portlet's `layout-css-class` gains `no-layout-background-image`, so the frame paints neither and the gap between the cards shows the page for the image as for the colour. The image is painted per card, fitted to each card's box. No automated test: CSS and template classes only (`frontend-vue.md`, no JS unit test). Checked on a running 7.3.x `feature/ai-contribution` server: the rows show the Branding application colour; the Branding application image shows on the tab bar and on the content card, and through the rows, on the Tasks tab and on a project's List view. Knowledge: pending — EXO-91474 This change is classified N3 at `b47b02feb`: no REST/DAO/schema/ACL surface touched (`classification.md` §3). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 70c60cf)
…round set in Branding EXO-91383 (#672) Symptom: with a Drawers & Popup background set in Branding and Theme, the suggestions list of the project picker of a task event, in the engagement center's rule form, stays white, with dark grey suggestions. Cause: the suggestions menu is detached to the page's root application container and keeps Vuetify's white surface. The picker's content-class attribute lands on its input, not on the menu: Vuetify 2 takes the menu content class only from menu-props, and the string form of menu-props carries flags only. Fix: menu-props takes its object form, keeping the closeOnClick and closeOnContentClick flags, and adds the content classes layout-drawer, which paints the Drawers & Popup colour on the menu, and application-menu, which lets the suggestions take the drawer text colour, size, weight and style instead of the fixed dark grey, the page text size and the normal weight and style the platform gives menu items, as Meeds-io/social#6233 does for exo-identity-suggester. The string's "maxHeight = 100" entry was read as an unknown flag and set no height, so the menu keeps its default height. Not covered: a Drawers & Popup background image is hidden by the list's solid drawer colour. Knowledge: Meeds-io/eng-standards#440 This change is classified N2 (at 97bf5ab: a shared component of the addon's common module, rendering only, no REST/DAO/schema/ACL surface) — its approver must be an Archi/Dev who knows it is N2, not an approval on AI review alone. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 2a9ff0e)
Jihed525
force-pushed
the
backport/theming-exip-to-mips
branch
from
October 24, 2026 17:19
f4d4148 to
8630577
Compare
Contributor
Author
Re-picked from the current
|
Jihed525
marked this pull request as ready for review
October 24, 2026 17:20
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
the Theming eXIP's
taskwork onfeature/mips, from the Tribe board Validation – Theming (project 8412): every task its stories cover that has a commit in this repository, picked fromfeature/ai-contributionin its order. Tasks: EXO-91408, EXO-91474, EXO-91383.Picks
3 commits,
git cherry-pick -x, in the order offeature/ai-contribution, picked from the commits on its current history, none of them already onfeature/mips(checked bygit cherry). The third column compares the pick's patch-id with its source's:=equal,resolveda conflict resolved inside the pick (listed below).e07cffcad220c2790670c60cfeb4ca6e1dd12a9ff0e5d863057771Testing
Built before a clean rebase onto the current
feature/mips(every pick=ingit range-diff), head863057771:mvn -B clean install: 260 tests, 0 failures,BUILD SUCCESS.Classification: N3: theme rules only (LESS and Vue templates, one portlet CSS class list), following the backgrounds an administrator sets in Branding; no REST, DAO, schema or ACL surface touched.
Knowledge: pending — EXO-91408
🤖 Generated with Claude Code