Skip to content

modernize CSS with flexbox and smooth transitions#420

Open
sanjana2505006 wants to merge 1 commit intoapache:masterfrom
sanjana2505006:feature/modernize-css
Open

modernize CSS with flexbox and smooth transitions#420
sanjana2505006 wants to merge 1 commit intoapache:masterfrom
sanjana2505006:feature/modernize-css

Conversation

@sanjana2505006
Copy link
Copy Markdown
Contributor

Updated the CSS to be more modern. Switched the layout from using floats to Flexbox so it's less brittle. Also added smooth transitions to buttons/links and cleaned up a bunch of old browser prefixes we don't need anymore.

@sanjana2505006
Copy link
Copy Markdown
Contributor Author

Please let me know if any adjustments are needed

@jdaugherty
Copy link
Copy Markdown
Contributor

@jamesfredley assume you intend to look at this one?

url('../fonts/roboto-regular.woff') format('woff'), /* Pretty Modern Browsers */
url('../fonts/roboto-regular.ttf') format('truetype'), /* Safari, Android, iOS */
url('../fonts/roboto-regular.svg#svgFontName') format('svg'); /* Legacy iOS */
src: url('../fonts/roboto-regular.eot');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Comments that were previously related to the line, is now looking like they are related to the line below. Generally there are too many unneeded white-space changes

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thank you for catching that! It looks like my code editor automatically reformatted the entire file and shifted all those comments out of place. I just force-pushed an update that undoes all those accidental whitespace changes and only keeps the functional flexbox/transition updates. It should be perfectly clean for review now!

@bito-code-review
Copy link
Copy Markdown

The PR makes extensive whitespace changes in screen.css, such as moving inline comments to separate lines, adjusting tab/space indentation, and adding blank lines between @font-face blocks. These modifications can shift line numbers, causing existing review comments to appear misaligned with their original lines. To minimize disruption, consider limiting changes to functional code and avoiding purely cosmetic whitespace edits.

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

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

4 participants