Skip to content

fix(core): scope public share theme filter to the download icon#61648

Merged
pringelmann merged 1 commit into
masterfrom
fix/public-page-menu-global-filter-scope
Jul 3, 2026
Merged

fix(core): scope public share theme filter to the download icon#61648
pringelmann merged 1 commit into
masterfrom
fix/public-page-menu-global-filter-scope

Conversation

@pringelmann

@pringelmann pringelmann commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Summary

#59175 added a global + class selector to scope the download-icon color filter to the explicit light/dark theme. Vue's scoped-style compiler drops everything after :global(...). Since data-themes is set on <body>, the filter inverted the entire public share page whenever a theme was enforced. Moving the descendant inside the parens keeps the full selector and limits the filter to the icon.

Before:

before-public-share-inverted

After:

after-public-share-fixed

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Tests (unit, integration, api and/or acceptance) are included
  • Screenshots before/after for front-end changes
  • Documentation (manuals or wiki) has been updated or is not required
  • Backports requested where applicable (ex: critical bugfixes)
  • Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
  • Milestone added for target branch/version (ex: 32.x for stable32)

@pringelmann pringelmann added this to the Nextcloud 35 milestone Jun 29, 2026
@pringelmann pringelmann self-assigned this Jun 29, 2026
@pringelmann pringelmann requested a review from a team as a code owner June 29, 2026 10:56
@pringelmann pringelmann added bug design Design, UI, UX, etc. labels Jun 29, 2026
@pringelmann pringelmann requested review from nfebe and susnux and removed request for a team June 29, 2026 10:56
@pringelmann pringelmann added the 3. to review Waiting for reviews label Jun 29, 2026
@pringelmann pringelmann requested a review from sorbaugh June 29, 2026 10:56
@pringelmann pringelmann force-pushed the fix/public-page-menu-global-filter-scope branch from 8f7cfb6 to c7e6895 Compare June 29, 2026 10:56
@pringelmann

Copy link
Copy Markdown
Contributor Author

/backport to stable34

@pringelmann

Copy link
Copy Markdown
Contributor Author

/backport to stable33

@pringelmann

Copy link
Copy Markdown
Contributor Author

/backport to stable32

@max-nextcloud

Copy link
Copy Markdown
Contributor

I stopped the backports of the first PR to prevent a regression. So the backports here will not be so clean. Not sure how best to proceed. I'm happy to unblock the other backports if that helps.

Comment thread core/src/views/PublicPageMenu.vue
@pringelmann pringelmann force-pushed the fix/public-page-menu-global-filter-scope branch from c7e6895 to b68dd67 Compare June 29, 2026 14:27
Signed-off-by: Peter Ringelmann <peter.ringelmann@nextcloud.com>
@susnux susnux force-pushed the fix/public-page-menu-global-filter-scope branch from b68dd67 to c9aa644 Compare July 3, 2026 10:20
@pringelmann pringelmann merged commit 5db01f0 into master Jul 3, 2026
154 of 161 checks passed
@pringelmann pringelmann deleted the fix/public-page-menu-global-filter-scope branch July 3, 2026 11:49
@backportbot

backportbot Bot commented Jul 3, 2026

Copy link
Copy Markdown

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/61648/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c9aa644b

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61648/stable32

Error: Failed to check for changes with origin/stable32: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Jul 3, 2026

Copy link
Copy Markdown

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/61648/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c9aa644b

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61648/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Jul 3, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/61648/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c9aa644b

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61648/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@pringelmann

Copy link
Copy Markdown
Contributor Author

@max-nextcloud thanks for flagging. I'm not sure its worth it to backport this all the way to stable32. It's a tiny cosmetic fix. Wdyt?

If we do want to backport the fix I can squash both changes into one commit and apply those to each stable.

@susnux

susnux commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

I agree with you, IMHO we do not need this on 32 - lets close the original backport there.

But it was requested to be fixed at least for 34, maybe code did not change that much for 33?
So could you ( @pringelmann ) apply your patch in the backports?

@pringelmann

Copy link
Copy Markdown
Contributor Author

Sure will do :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Public share download button icon color

3 participants