Skip to content

fix: get rid of legacy prop - #18687

Open
Antreesy wants to merge 1 commit into
mainfrom
fix/noid/settings-dialog-legacy
Open

fix: get rid of legacy prop#18687
Antreesy wants to merge 1 commit into
mainfrom
fix/noid/settings-dialog-legacy

Conversation

@Antreesy

@Antreesy Antreesy commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

☑️ Resolves

  • content non-wrapped with class 'app-settings-subsection' showed huge gaps, that are not expected with 'legacy-style' components
  • temporarily wrap in div until migrated
  • remove deprecated 'legacy' prop

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

See section names drifted off to the right, slight change in vertical gaps (in some places)

🏚️ Before 🏡 After
image image
image image
image image
image image

🏁 Checklist

  • 🌏 Tested with different browsers / clients:
    • Chromium (Chrome / Edge / Opera / Brave)
    • Firefox
    • Safari
    • Talk Desktop
    • Integrations with Files sidebar and other apps
    • Not risky to browser differences / client
  • 🖌️ Design was reviewed, approved or inspired by the design team
  • ⛑️ Tests are included or not possible
  • 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

@ShGKme

ShGKme commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Before/After screenshots are mixed?
On the After headings are not aligned anymore.

@Antreesy

Copy link
Copy Markdown
Contributor Author

Before/After screenshots are mixed?

No

On the After headings are not aligned anymore.

That's from non-legacy --... offset variable

@ShGKme

ShGKme commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Then I didn't get the change. Do you want to remove legacy prop, but keeping the legacy design?

@Antreesy

Copy link
Copy Markdown
Contributor Author

Do you want to remove legacy prop,

Yes, as it's a deprecated prop that barely changing styles for us. All major changes introduce with v34 are wired with server check isLegacy34 anyway and prop doesn't play a role here

but keeping the legacy design?

For now, so we can update section by section

@Antreesy

Copy link
Copy Markdown
Contributor Author

Added a similar offset to 'legacy' sections, here's how it looks next to modern settings:
image

- content non-wrapped with class 'app-settings-subsection' showed huge gaps, that are not expected with 'legacy-style' components
- temporarily wrap in div until migrated

Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
@Antreesy
Antreesy force-pushed the fix/noid/settings-dialog-legacy branch from ccf2d6b to ba9db80 Compare July 17, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants