Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(layout): fix layout for non-default html font-size / revision 2 #6073

Merged
merged 3 commits into from
Mar 30, 2024

Conversation

oleasteo
Copy link
Contributor

Second revision of PR #6007 due to issues with first PR. @wmertens

What is it?

  • Feature / enhancement
  • Bug
  • Docs / tests / types / typos
  • Layout Glitch

Description

Make layout work independent of browser font-size setting.

Use cases and why

See #5853

Checklist:

  • My code follows the developer guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • Added new tests to cover the fix / functionality

Copy link

netlify bot commented Mar 30, 2024

👷 Deploy request for qwik-insights pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 4da9d08

@wmertens wmertens merged commit 6ab865c into QwikDev:main Mar 30, 2024
22 checks passed
@shairez
Copy link
Collaborator

shairez commented Apr 6, 2024

@wmertens @oleasteo this PR removed the <OnThisPage /> sidebar

Was that done by mistake? or was it on purpose?

@oleasteo
Copy link
Contributor Author

oleasteo commented Apr 6, 2024

I considered it dead code. Was I wrong?

  const noRightMenu = ['/docs/'].includes(loc.url.pathname);
  // [...]
        class={{
          'no-right-menu': noRightMenu,
        }}

within /routes/docs/layout.tsx file would always be true. Wouldn't it?

In combination with

.docs main.no-right-menu .on-this-page {
  display: none;
}

this did essentially hide it in all cases.

@shairez
Copy link
Collaborator

shairez commented Apr 6, 2024

Well, if you revert these PR changes the side-menu appears

@oleasteo
Copy link
Contributor Author

oleasteo commented Apr 6, 2024

Ah, my bad: I did not read ['/docs/'].includes(loc.url.pathname) properly; it only matches the exact /docs/ url, not sub-pages. Sorry for this.

So yes, it's been a mistake. Should I create a fix or are you on it anyway?

@shairez
Copy link
Collaborator

shairez commented Apr 6, 2024

Yeah if you can it would be great!
Thanks!

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.

None yet

3 participants