Skip to content

Optimize header layout performance with flexbox mixins#5

Open
ShashankFC wants to merge 1 commit into
header-layout-optimization-prefrom
header-layout-optimization-post
Open

Optimize header layout performance with flexbox mixins#5
ShashankFC wants to merge 1 commit into
header-layout-optimization-prefrom
header-layout-optimization-post

Conversation

@ShashankFC

Copy link
Copy Markdown
Collaborator

@GitHoobar

Copy link
Copy Markdown

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b229316ee

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 35 to +39
.panel {
float: right;
position: relative;
margin-left: auto;

@include order(3);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Preserve right alignment in noscript header

In the noscript header (app/views/application/_header.html.erb lines 3–18), .panel sits inside a .row, and .row is still the Bootstrap float-based grid (app/assets/stylesheets/vendor/bootstrap.scss lines 25–38), not a flex container. After removing float: right here, the login panel will no longer align to the right and will stack below the title when JavaScript is disabled (the <noscript> path). Keeping the float for that markup or making .row a flex container would avoid the regression in no-JS environments.

Useful? React with 👍 / 👎.

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.

2 participants